Appearance

Standards & Security ​

Unified Token Standard Support ​

Lucid Bridge is built on an extended xERC20 framework supporting multiple interoperability and mint/burn standards.

Supported standards include:

  • xERC20
  • NTT
  • CCT
  • ITS
  • ERC-7802
  • custom mint/burn implementations

This allows assets to move across supported chains and interoperability providers without requiring bridge-specific wrappers or isolated token implementations.

xERC20 Infrastructure ​

Lucid extends the xERC20 model to support bridge-agnostic mint and burn infrastructure across multiple interoperability providers.

This enables:

  • unified asset movement across chains
  • bridge-independent token execution
  • configurable mint and burn permissions
  • interoperability across supported bridge systems

Assets can move across integrated infrastructure providers while maintaining a consistent token model across supported ecosystems.

Mint & Burn Architecture ​

Mint and burn operations are executed exclusively through Lucid Asset Controller contracts.

These controllers:

  • manage mint and burn permissions
  • coordinate token supply changes
  • operate independently from routing infrastructure
  • remain isolated from relay coordination systems

Routing systems and bridge infrastructure do not hold mint or burn authority.

Controller Separation ​

Lucid separates:

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

This separation prevents routing infrastructure or temporary relay systems from controlling token supply management.

Even during multi-hop execution, mint and burn permissions remain isolated within the controller infrastructure.

Relay Security Model ​

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

The relay infrastructure:

  • validates routing parameters
  • coordinates transaction forwarding
  • introduces operational redundancy
  • does not control token supply
  • does not hold mint or burn permissions

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

Distributed Signer Infrastructure ​

The relay multisignature system uses independent signing environments to reduce correlated operational risk.

Each signer operates within isolated infrastructure environments with separate operational coordination.

This reduces dependency on:

  • single relayer infrastructure
  • single execution environments
  • centralized bridge coordination systems

Emergency Access ​

Emergency access is reserved exclusively for recovery procedures and operational protection.

Any emergency action requires:

  • multisignature approval
  • internal governance coordination
  • explicit authorization procedures

Emergency infrastructure does not modify Lucid’s separation between:

  • relay coordination
  • routing infrastructure
  • mint and burn authority

Asset Compatibility ​

Lucid Bridge supports interoperability across multiple token infrastructure models through unified mint and burn coordination.

Supported compatibility models include:

  • canonical token infrastructure
  • bridge-native mint/burn systems
  • wrapped interoperability models
  • custom token controller architectures

This enables ecosystems to integrate existing token infrastructure into Lucid Bridge without rebuilding asset architecture for individual bridge providers.