Multi-Bridge Architecture
The Multi-Bridge Architecture is SODAX's layered approach to cross-network message delivery, combining proprietary relays with third-party protocols to maximize reliability and coverage.
What it is
The Multi-Bridge Architecture is the transport layer that SODAX uses to move messages and assets between networks. Rather than depending on a single bridge protocol, SODAX operates multiple bridge paths in parallel: proprietary relays built and operated by the SODAX team, alongside third-party protocols such as LayerZero and CCTP.
This layered design means SODAX is not dependent on any single external bridge for cross-network message delivery (often searched as cross chain bridge or cross chain messaging).
What it does inside SODAX
Within the SODAX system, the Multi-Bridge Architecture sits beneath the Generalized Messaging Protocol (GMP). When a cross-network action requires message delivery between a Spoke and the Hub, the system selects the appropriate bridge path based on the networks involved, asset types, and current conditions.
Proprietary relays handle the majority of traffic on supported routes. Where proprietary coverage does not yet exist or where specific asset standards require it (such as USDC via CCTP), the system routes through third-party protocols.
The architecture is additive. New bridge integrations can be added without replacing existing ones, and routing decisions happen at the system level rather than being exposed to the application.
Why it exists
Single-bridge dependency is a known risk in cross-network infrastructure. Bridge exploits, downtime, or congestion on one protocol can halt execution across the entire system.
The Multi-Bridge Architecture exists to reduce single points of failure in message delivery. It also expands network coverage, since different bridge protocols support different networks.
For the broader DeFi ecosystem, this pattern is sometimes described as bridge aggregation (often searched as cross chain bridge aggregator): using multiple transport layers to improve reliability and reach.
What this means for users and partners
For users, the bridge selection is invisible. They submit an action, and the system determines how messages are delivered.
For partners integrating SODAX, the Multi-Bridge Architecture means broader network support and reduced dependency risk. Partners do not need to evaluate or integrate individual bridge protocols. They interact with SODAX's execution surface, and the system handles transport.
