Messaging and transfer mechanisms (formerly Multi-Bridge Architecture)

Messaging and transfer mechanisms are how SODAX carries cross-network actions between its Hub and Spokes: over its own messaging protocol and relay, working alongside existing messaging layers rather than replacing them. SODAX is not a bridge.

cross-networkgmpmessagingverificationrelayersystem

What it is

This page covers how SODAX carries messages and assets between networks. It was earlier called the Multi-Bridge Architecture, a name from an older framing. SODAX is not a bridge.

SODAX carries each cross-network action over its own messaging protocol, the Generalized Messaging Protocol (GMP), and its own Relayer. The Hub, the messaging protocol and the relay are SODAX's own infrastructure, not third-party routing primitives. SODAX works alongside existing messaging layers rather than replacing them.

What it does inside SODAX

When a cross-network action needs to travel between a Spoke and the Hub, the Spoke creates a message, GMP authenticates and verifies it, and the Relayer submits it on the destination network.

Assets move as part of the same action. The Asset manager authorizes tokens into and out of the SODAX system, and the Rate Limiter caps how much value can move between networks in a given time window.

How a message travels is decided at the system level. It is not exposed to the app that requested the action.

Why it exists

Depending on a single outside transport is a known risk in cross-network infrastructure (often searched as cross chain messaging). An exploit, downtime or congestion on one protocol can halt every action that relies on it.

Owning the core messaging path, and working alongside existing messaging layers instead of depending on any one of them, reduces that single point of failure. It also lets SODAX settle each action on its own Hub, rather than handing a user's transaction to an outside rail.

What this means for users and partners

For users, how a message travels is invisible. They request an action, and it completes as requested or reverts and returns the original assets.

For partners, there are no bridges to run and no individual messaging protocols to evaluate. They call the SODAX API, and SODAX carries the action between networks. A team already running a messaging standard can use SODAX alongside it.

Related terms

Last updated: 11/11/2026