Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.enso.build/llms.txt

Use this file to discover all available pages before exploring further.

Enso supports four bridge protocols for crosschain operations, each with different characteristics. Use the Bundle API to explicitly select a bridge protocol and (where supported) define post-bridge callbacks.

CCIP

Chainlink CCIP - Best for ERC20 tokens with larger callback payloads (up to 30KB). Higher security through Chainlink’s oracle network. Note: waits for source chain finalization.

CCTP

Circle CCTP v2 - Native USDC burn/mint across chains. Fast Transfer (sub-15s) or Standard + Forwarding Service. No callbacks.

Relay

Relay - Best for flexible bridging with dynamic amounts. No callback data limit, supports native tokens.

Stargate

LayerZero Stargate - Best for native token bridging and LayerZero ecosystem. Tight callback limit (~9.5KB).

Mixed Protocols

Stargate + CCIP - Combine multiple bridges for complex crosschain workflows with nested callbacks across chains.

When to Use Each Bridge

ProtocolBest ForCallback LimitNative TokenToken CoverageFinalization
CCIPLarge callback payloads, high security~30KBNoERC20 (whitelisted)Waits for source chain finality
RelayDynamic amounts, flexible routingUnlimitedYesERC20 + nativeFast
StargateLayerZero ecosystem, native bridging~9.5KBYesOFT-enabled tokensFast
CCTPNative USDC across chainsNo callback supportNoUSDC onlyFast (where available) or wait for finality
CCIP finalization: CCIP waits for source chain finalization before executing callbacks. Timing varies by chain (sub-second to hours). See Chainlink’s Finality By Blockchain for current times. Consider this for time-sensitive swaps with slippage protection on slower chains.
CCTP transfer modes: Every CCTP transfer is auto-relayed by Circle’s Forwarding Service — receivers never need destination gas. Fast Transfer attests after a few confirmations (sub-15s typical) and pays a small protocol fee on top of the forwarding fee; Standard waits for full source-chain finality and pays the forwarding fee only. The bundle action silently falls back to Standard when Fast is unavailable on the source.

Discovery APIs

Updated