Aditya

Incredible work making this possible @GjermundGaraba @srdtrk!! And of course thanks to all the engineers who worked on IBC these past years to make it the most secure interoperability protocol, we're carrying the torch forward to Ethereum and new ecosystems beyond 🫡

@GjermundGaraba @arlai_mk @IBCProtocol This is a good overview!

@arlai_mk @IBCProtocol Any other changes people should be aware of @turingtestrun?

Which indexers would be affected by @IBCProtocol Eureka changes? I'm trying to map out all the tools and software that need updating. #IBCEureka

🚀🚀🚀

Massive!

Verifying IBC light client proofs on Ethereum is expensive. Thankfully, ZK proofs offer a scalable solution that reduces the cost. The IBC team at @interchain_io built a proof-of-concept for an EVM Tendermint Light Client using @succinctlabs SP1.

Come see my talk on Pessimistic Validation and enabling IBC for rollups and beyond (hint: Ethereum) 15:40 at the Pencil stage. @modular_summit

We wanted to use Instagram ads to highlight how ad tech invades your privacy. Instead, Facebook shut our account down: signal.org/blog/the-insta…

I've released go-codegen v0.2 this week, which can now generate an interchaintest-based test suite, along with message definitions and a gRPC query client for @CosmWasm contracts. Join me at the @AwesomWasm in Berlin, where I'll demonstrate how to leverage @strangelovelabs' interchaintest with go-codegen to efficiently test IBC-enabled @CosmWasm applications. Don't miss out! 🚀 Check out the repo here: github.com/srdtrk/go-code… #IBC #CosmWasm

Explore the growing spectrum of ways to build with IBC, & how the protocol is set up to stay relevant in an ever-changing landscape. Join the panel featuring industry leaders: @adrianbrink from @anoma, Callum Waters from @CelestiaOrg, @turingtestrun from @interchain_io, & moderated by @tmsdkeys from @Polymer_Labs. 🎟️Don't miss out! lu.ma/IBCBerlin

@Ethereal0ne Hope to see you in Berlin very soon!! Take care until then

as someone building a cross-chain app, the highest priority for me is:

👀👀👀

Incredible work by the IBC team. This approach could be generalized to any architecture that allows parallel statemachines to run on the same consensus model. Thinking here of rollups, restaking AVS, etc. More ecosystem expansion from us incoming...

Generally agreed on everything here! Though I doubt it is ever possible to get things right on the first try. My work in IBC is complete when the protocol is adaptable enough for future devs to undo all the mistakes we made

@0xshake @IBCProtocol @cosmos Congrats and godspeed!! 🚀

While we started off building in the Ethereum ecosystem, we've also had deep conviction in both @IBCProtocol and @cosmos technology since the very beginning. We're deeply passionate about merging both Ethereum and Cosmos tech together to form the Cosmothereum ecosystem. Ethereum and Cosmos teams have spent the past few years solving a different but complementary set of problems. Ethereum L2 teams have been solving the settlement problem while the Cosmos core teams have been solving the interoperability and app chain developer UX problem. Now, both Ecosystems share a similar vision for the future. Interoperable networks of app rollups on Ethereum and an interoperable network of app chains/rollups in the Cosmos. Our mission @Polymer_Labs is to ensure that these two ecosystems that share the same vision for the future do not walk along diverging technical paths. By building Polymer as an L2 on Ethereum, we aim to unify both ecosystems using a common language in IBC. Our novel approach allows Ethereum to directly communicate with the Cosmos without a middle man or chain. While Polymer is the first Cosmothereum L2, we also aim to build a network of Cosmothereum L2s allowing @cosmos_sdk builders to deploy directly onto Ethereum. We're excited and humbled to bring on board an incredible roster of investors who share our vision of the future - @blockchaincap, @Maven11Capital, @placeholdervc, @NorthIslandVC, @FigmentCapital, @informalinc, @DCGco and many more! Personal thanks to these amazing investors and partners who have supported us and given us the freedom to build conviction in our unique path forward - @TravisScher, @yuan_han_li, @sproule_, @cburniske, @rainandcoffee, @MathijsvEsch, @0xJim, @DougieDeLuca, @jacobkxyz, @sreeramkannan, @musalbas and more! Also, we're building on the shoulders of giants and the many teams who have been contributing to the Interchain stack as well as the OP stack - @turingtestrun, @susevans, @chrlylrhc, @adi_r_r, @plafer2718, @cwgoes, @fekunze, @mark0baricevic, @AdiSeredinschi, @buchmanster, @sunnya97, @jackzampolin, @protolambda, @maurelian_ , @tyneslol, @kelvinfichter and many many more!

Serdar is such a beast 💪!!

@seunlanlege agreed that handshakes should be compressed for resource-constrained envs. client <-> app as cheaply as possible soon ack/timeout are great and should stay an interop protocol that requires shared security is just a scaling solution

Finally understanding that shared security fixes IBC asset fungibility? Or that 4-way messaging for sending a single cross-chain message doesn't scale? Let's check back on our IBC friends in the future.

Ideas that ISMP has already implemented

In 2024, IBC will expand to new ecosystems. One of the targets is the OP Stack, a framework built by @optimism, Ethereum's second-largest rollup. But how do you port a well-defined interoperability protocol to the OP Stack framework? A preview into architecture 🧵 1/

Pretty nice that cosmos tx is plainly readable on ledgers 😎

2024 is rollup szn for IBC