Fallback mechanism

The fallback mechanism enables Conla Layer to “fall back” to using Ethereum calldata for data availability in the event of downtime on Celestia.

In the case of Celestia downtime or temporary unavailability, Conla will fallback to posting transactions as calldata on Rootstock instead of posting to Celestia. This mechanism ensures users can continue to transact securely and seamlessly, preventing disruptions and helping to ensure user funds do not get stuck in the Conla's bridge on Rootstock.

Fallback is triggered whenever the sequencer has an error sending the PayForBlobs transaction on Celestia. Fallback can be triggered due to a congested mempool or nonce error and can be simulated with an error such as low balance or incorrect sequence. Fallback can also be triggered in the event Blobstream stops relaying attestations.

Last updated