Generalized Messaging Protocol (GMP)
GMP is the authenticated messaging layer that transmits and verifies cross-network instructions within the SODAX system.
What it is
The Generalized Messaging Protocol (GMP) is SODAX's own contract-level messaging protocol, used to send verified instructions between networks.
It does not move assets. It transmits payloads that instruct contracts on other networks to perform specific actions.
GMP provides the authenticated channel through which cross-network actions are coordinated across the Hub and supported networks.
What it does inside SODAX
Within SODAX, GMP carries the instruction layer of cross-network execution.
When a contract on one network needs to trigger logic on another network, GMP transmits a payload containing the necessary data. That payload is verified through a distributed signer set in the Relayer before it is executed on the destination contract. GMP ensures:
- Messages are uniquely identified.
- Messages cannot be replayed.
- Only authorized relayers can validate delivery.
- A message is processed at most once.
It does not calculate routes. It does not determine pricing. It does not hold liquidity. It does not decide whether or how an Intent is filled. It verifies and delivers instructions. Asset movement is handled separately by the Asset Manager.
Why it exists
Cross-network execution requires more than moving assets. Contracts must be able to trigger logic on other networks in a verifiable way. Without an authenticated messaging layer:
- Settlement state could diverge.
- Execution steps could not be coordinated.
- Recovery paths would be harder to implement.
- Contracts would lack a secure way to confirm cross-network intent.
GMP exists to provide a minimal, secure pipe for transmitting instructions between networks. It separates instruction delivery from asset custody and from execution reasoning.
GMP is SODAX's own infrastructure rather than a third-party routing primitive, and SODAX works alongside existing messaging layers rather than replacing them.
What this means for users and partners
For users, GMP is invisible. It ensures that once a cross-network action is initiated, the required contract calls are delivered and verified across networks.
For builders, GMP is part of what the SODAX API takes off their hands (often searched as cross chain messaging protocol): apps call the SODAX API, and GMP carries the resulting instructions between networks, so builders do not design their own cross-network communication layer.
Component boundaries remain clear:
- A permissioned solver within the SODAX system determines how to fill an Intent.
- The Coordinator structures execution steps.
- The Asset Manager moves assets.
- The Hub records settlement.
- GMP transmits and verifies instructions between networks.
GMP is the messaging pipe of SODAX. It carries instructions, not value.
Related terms
- Relayer: signs and submits verified messages
- Hub: where settlement is recorded
- Spoke: the endpoint on each network
- Asset manager: moves the assets
- Hub-and-spoke architecture: the design GMP connects
- Cross-network execution: what GMP makes possible