Appearance

Multi-Hop & Multi-Consensus ​

Multi-Hop ​

Multi-Hop enables deterministic cross-chain routing between supported ecosystems through a single transaction flow.

Instead of requiring users to manually route assets across multiple chains or bridge systems, Multi-Hop coordinates routing, verification, and settlement through Lucid’s infrastructure layer.

This allows assets to move between supported ecosystems through one coordinated execution process.

Routing Architecture ​

Multi-Hop uses Arbitrum as the base mint chain for Lucid assets.

When a transfer is initiated:

  1. assets are routed through supported routing infrastructure
  2. relay infrastructure coordinates transaction forwarding
  3. assets are forwarded to the destination bridge infrastructure
  4. the transfer finalises on the destination chain

The routing flow is coordinated automatically through Lucid’s infrastructure layer.

Relay Infrastructure ​

Multi-Hop routing uses a transient relay infrastructure coordinated through a 2-of-3 Safe multisignature relay mechanism.

The relay infrastructure:

  • coordinates transaction forwarding
  • validates routing parameters
  • introduces operational redundancy
  • does not hold mint or burn authority

Funds remain within the relay infrastructure only temporarily during transaction forwarding.

Infrastructure Separation ​

Lucid separates:

  • routing infrastructure
  • relay coordination
  • mint and burn authority
  • bridge execution infrastructure

This separation ensures that routing systems and relay coordination layers do not control asset minting permissions or token supply management.

Multi-Consensus Transfers ​

Multi-consensus transfers allow assets and messages to require confirmation from multiple interoperability providers before execution finalises.

Instead of relying on a single bridge provider, Lucid coordinates transfer execution across multiple integrated bridge systems through configurable consensus thresholds.

Transfer execution is determined by:

  • configured bridge limits
  • selected interoperability providers
  • consensus thresholds
  • transfer size

Consensus Thresholds ​

Consensus-based execution requires confirmation from multiple interoperability providers before transfer finalisation.

Supported threshold configurations can include:

  • 2-of-2
  • 2-of-3
  • 3-of-5

This introduces additional redundancy and verification during transfer execution.

Multi-Bridge Asset Transfers ​

Multi-Bridge Asset Transfers enable governance tokens and supported assets to move across supported chains through consensus-based execution.

Transfer configuration includes:

  • source and destination chains
  • participating bridge providers
  • consensus thresholds
  • transfer amount
  • receiver configuration

Transfer execution is coordinated through Lucid’s bridge aggregation infrastructure.

Multi-Consensus Message Transfers ​

Multi-Bridge also supports consensus-based cross-chain message execution.

This infrastructure supports:

  • governance coordination
  • protocol upgrades
  • contract interactions
  • operational messaging

Messages can require confirmation from multiple interoperability providers before execution.

Export & Execution Flow ​

Consensus-based transactions are exported through Lucid and executed through Safe transaction infrastructure.

Exported transaction payloads include:

  • Target Address
  • Value
  • Data

Transaction execution finalises once the required approval threshold is reached.