Economic / Cross-Chain Interoperability
Beatoz-Axelar Integration
Solo-built cross-chain integration between Beatoz EVM and Axelar CGP, including core CGP contracts and a Beatoz relayer for event monitoring/command execution.
- Role
- Solo builder · architecture, implementation, and operational tooling
- Period
- 2025.07 - 2025.08
- Context
- Beatoz Labs
Solo-built cross-chain integration between Beatoz EVM and Axelar CGP, including core CGP contracts and a Beatoz relayer for event monitoring/command execution.
What made the system difficult.
Required a verifiable command execution path for cross-chain flows, plus supporting modules (auth, gas, deposits) as part of the end-to-end system.
How boundaries and flows answered it.
Integrated the CGP contract suite (Gateway/AuthWeighted/GasService/DepositService) with weighted multisig auth, gas payment/refund, and CREATE2-based deposits. Implemented a Beatoz relayer that monitors on-chain events and executes verified commands, supported by deploy scripts and tests.
Overview
- Solo-built cross-chain integration between Beatoz EVM and Axelar CGP.
- Includes CGP contracts (Gateway/Auth/Gas/Deposit) and an event-driven relayer.
Key Components
CGP Contract Layer
- Gateway (execute command batches) + AuthWeighted (weighted multisig, epoch/validator set) + GasService + DepositService (CREATE2 deposits).
Relayer (Event Monitoring → Command Execution)
- Monitors source-chain events and executes destination-chain commands.
- Built with batching/direct-RPC style optimizations to reduce overhead while preserving reliability.
Operational Focus
- Cross-chain systems are failure-first: idempotency, retries, and observability are first-class concerns.