Skip to main content

Crosschain Treasury Introduction

The Crosschain Treasury enables secure asset transfers between EVVM and external blockchains. This multi-chain solution uses interoperability protocols to coordinate asset management across different blockchain networks.

Architecture

The system uses two coordinated stations:

Host Chain Station

  • Operates on the same blockchain as EVVM
  • Handles withdrawals from EVVM to external chains
  • Receives deposits from external chains
  • Manages EVVM balance updates

External Chain Station

  • Deployed on external blockchains where user assets exist
  • Handles deposits from users to EVVM
  • Receives withdrawals from EVVM
  • Manages real assets (tokens and native coins)

Supported Protocols

ProtocolIDDescription
Hyperlane0x01Modular interoperability framework
LayerZero0x02Omnichain protocol
Axelar0x03Decentralized cross-chain network

Fisher Bridge System

Advanced feature enabling gasless transactions:

  • Gasless Operations: Users don't need native tokens for gas
  • Signature Authorization: Users sign messages to authorize transfers (see Fisher Bridge Signature Structure)
  • Priority Fees: Incentives for fisher executors
  • Authorized Executors: Permissioned addresses that facilitate transfers

When to Use Crosschain Treasury

Ideal for:

  • EVVM on different blockchain than user assets
  • Multi-chain support requirements
  • Advanced features like gasless transactions
  • Interoperability protocol integration

Available Functions

Host Chain Station

External Chain Station

Cross-Chain Flow

External Chain          Host Chain
│ │
User Assets ──────→ EVVM Balances
│ │
External Station ←──→ Host Station

The stations coordinate through cross-chain messaging to maintain synchronized asset management.

Available Functions

Host Chain Station Functions

External Chain Station Functions

Supporting Libraries

For Fisher Bridge signature requirements and verification, see the Fisher Bridge Signature Structure documentation.

The Treasury Crosschain system implements standardized error handling and data structures for cross-chain operations.

Security Features

Security Considerations
  • Principal token withdrawals are blocked to protect ecosystem integrity
  • All cross-chain messages require proper authorization verification
  • Fisher bridge operations use cryptographic signatures for user consent (see Fisher Bridge Signature Structure)
  • Time-delayed governance for administrative changes (1-day delay)
  • Protocol-specific validation for each supported interoperability solution

Gas Management

Each protocol requires different gas payment mechanisms:

  • Hyperlane: Native tokens paid to mailbox contract
  • LayerZero: Estimated fees through LayerZero endpoint
  • Axelar: Gas service payments for cross-chain execution

Users must provide sufficient native tokens to cover cross-chain transaction costs when initiating transfers.