Spoke
A Spoke is the local execution endpoint on a supported network, responsible for receiving user actions, locking assets, and relaying messages to the Hub for cross-network coordination.
What it is
A Spoke is SODAX's local presence on a supported network. Each network that SODAX supports has a Spoke deployment, which acts as the entry and exit point for user actions on that network.
The Spoke is one half of the hub-and-spoke architecture (often searched as hub and spoke blockchain architecture). The Hub coordinates. The Spoke executes locally.
What it does inside SODAX
Within the SODAX system, the Spoke handles several responsibilities on its local network:
- Receives user actions such as swaps, bridge transfers, lending deposits, or borrow requests
- Locks or transfers assets on behalf of the user
- Relays messages to the Hub via the Generalized Messaging Protocol (GMP)
- Fills intents locally when a Solver determines that the destination network is where the Spoke is deployed
- Enforces rate limits on asset transfers to manage risk
Each Spoke deployment includes a Spoke Asset Manager, an Intent Filler contract, and rate limit controls. These components work together to ensure the local network can participate in cross-network execution (often searched as cross chain execution) without requiring the user to interact with the Hub directly.
Why it exists
Cross-network systems need local interfaces on every supported network. Without a Spoke, users would need to interact directly with the Hub, which would limit the system to a single network.
The Spoke exists so that SODAX can extend its execution and liquidity capabilities to any supported network while keeping coordination centralized on the Hub. This separation means new networks can be added by deploying a new Spoke, without modifying the core system.
What this means for users and partners
For users, the Spoke is invisible. They interact with their local network as they normally would. The Spoke handles the cross-network coordination behind the scenes.
For builders integrating SODAX via the SDK, the Spoke is represented as a Spoke Provider. Each wallet connection on a given network maps to a Spoke Provider instance, which the SDK uses to route operations to the correct local deployment.
