blog.celestia.org/lazybridging/
In order for modular to succeed long-term, applications cannot be forced to trade off access to users and liquidity, due to cross-chain fragmentation.
Lazybridging is Celestia’s “endgame” plan to allow Celestia’s blockspace to be saturated by a multi-rollup ecosystem that feels like a seamless, single experience to the end user.
Lazybridging will be enabled by adding a ZK-based IBC client to the base layer, which will enable rollups to natively bridge to Celestia, without the need to add smart contracts to the base layer, which introduces performance overheads such as state bloat.
I believe that Celestia might be the only rollup ecosystem that is capable of achieving a frictionless modular experience user in the long-term, for two reasons. Firstly, Celestia has single-slot finality, which means that interoperability can be instant, especially as we take advantage of decreasing ZK proving times.
Secondly, Celestia supports IBC, which means that applications will have a native way to access assets and liquidity outside of just the Celestia ecosystem, but across the wider blockchain ecosystem, without third-party multisigs. For example, rollups would be able to access native USDC via Noble, or access BTC via a Babylon IBC connection. This can also be used to bridge to non-IBC chains like Ethereum without third-party multisigs, as upcoming improvements to IBC will make it easy to deploy an IBC client as an Ethereum smart contract.
The main reason why some developers choose to deploy smart contracts on monolithic chains instead of rollups right now is better access to users and liquidity. But if we eliminate that reason with an interop experience identical (or even better) than using a monolithic L1, then developers choosing rollups will be a no brainer, as it gives them more flexibility over capturing revenue rather than leaking it all to the base layer, let alone allowing them to create products that simply aren't possible on existing shared VMs. That's what the big opportunity is.
Celestia’s ZK-based IBC client, which is the first step to Lazybridging, is undergoing implementation work, with deployment on the base layer targeted for the first half of 2025. A proof-of-concept is also being developed that bridges a Rollkit-based reth chain to Celestia, using the SP1 prover.
In order for modular to succeed long-term, applications cannot be forced to trade off access to users and liquidity, due to cross-chain fragmentation.
Lazybridging is Celestia’s “endgame” plan to allow Celestia’s blockspace to be saturated by a multi-rollup ecosystem that feels like a seamless, single experience to the end user.
Lazybridging will be enabled by adding a ZK-based IBC client to the base layer, which will enable rollups to natively bridge to Celestia, without the need to add smart contracts to the base layer, which introduces performance overheads such as state bloat.
I believe that Celestia might be the only rollup ecosystem that is capable of achieving a frictionless modular experience user in the long-term, for two reasons. Firstly, Celestia has single-slot finality, which means that interoperability can be instant, especially as we take advantage of decreasing ZK proving times.
Secondly, Celestia supports IBC, which means that applications will have a native way to access assets and liquidity outside of just the Celestia ecosystem, but across the wider blockchain ecosystem, without third-party multisigs. For example, rollups would be able to access native USDC via Noble, or access BTC via a Babylon IBC connection. This can also be used to bridge to non-IBC chains like Ethereum without third-party multisigs, as upcoming improvements to IBC will make it easy to deploy an IBC client as an Ethereum smart contract.
The main reason why some developers choose to deploy smart contracts on monolithic chains instead of rollups right now is better access to users and liquidity. But if we eliminate that reason with an interop experience identical (or even better) than using a monolithic L1, then developers choosing rollups will be a no brainer, as it gives them more flexibility over capturing revenue rather than leaking it all to the base layer, let alone allowing them to create products that simply aren't possible on existing shared VMs. That's what the big opportunity is.
Celestia’s ZK-based IBC client, which is the first step to Lazybridging, is undergoing implementation work, with deployment on the base layer targeted for the first half of 2025. A proof-of-concept is also being developed that bridges a Rollkit-based reth chain to Celestia, using the SP1 prover.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
