Skip to main content
Enso supports three bridge protocols for crosschain operations, each with different characteristics. Use the Bundle API to explicitly select a bridge protocol and 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.

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 TokenFinalization
CCIPLarge callback payloads, high security~30KBNoWaits for source chain finality
RelayDynamic amounts, flexible routingUnlimitedYesFast
StargateLayerZero ecosystem, native bridging~9.5KBYesFast
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.

​
Discovery APIs

  • CCIP: Use GET /ccip/router to get the CCIP Router address
  • Stargate: Use GET /layerzero/pool to get the OFT pool address
  • Relay: Use the token address directly as primaryAddress

Updated