About

Espresso is the base layer for rollups, delivering fast, secure finality and reliable data availability. Developers building on rollups integrated with Espresso can rely on Espresso’s consensus to achieve instant, trust-minimized finality and build applications that react safely and quickly across chains. Espresso’s fast and secure finality unlocks a new era of cross-chain applications. Imagine using a bridge between two rollups — Rollup A and Rollup B. When sending funds from A (the source) to B (the destination), those funds must first be locked on A before being released on B. To ensure safety, you must be confident that the transaction on the source chain cannot be reverted. Traditionally, you’ve had three options: - Wait for finality on the parent chain — secure but slow (can take hours). - Skip waiting and assume the risk — fast but unsafe. - Use Espresso confirmations — fast and secure, powered by the Espresso Network’s consensus.

Prizes

🏆 Best Cross-Chain App Deployed on ANY Espresso-integrated chain$4,000
🥇
1st place
$2,500
🥈
2nd place
$1,500
Best Cross-Chain Application deployed on ANY Espresso-integrated chain (Celo, ApeChain, Rari, Appchain, Molten, T3rn, NodeOps, Rufus, Huddle01, LogX).

Qualification Requirements

The application must: - Have a cross-chain interaction (from a source chain to a destination chain). You can use message protocols like Hyperlane to perform the cross-chain interaction. - The source chain must be an Espresso-integrated chain (ApeChain, Rari, Appchain, Molten, T3rn, NodeOps, Rufus, Huddle01, LogX, Celo). The application must: - The message protocol (for example, Hyperlane), must read from the Espresso's Caff Node RPC. This is just a normal RPC instrumented to read from the Espresso Network.