Hub Wallet Abstraction (Wallet Factory)
Hub Wallet Abstraction is the deterministic smart wallet system on the SODAX Hub that gives each user a stable execution identity for cross-network actions.
What it is
Hub Wallet Abstraction is the system that generates a deterministic smart wallet for each user on the Hub.
When a user acts from a supported network, their source address maps to a predictable proxy wallet on the Hub. This wallet is created through the protocol's factory contract and serves as the execution identity for cross-network actions.
It is not a consumer wallet and it is not a custody replacement. It is an execution surface inside the Hub.
What it does inside SODAX
Within SODAX, the Hub Wallet is the on-chain identity through which cross-network actions are carried out on the Hub. When a user signs an intent, that authorization allows the corresponding Hub Wallet to:
- Receive assets carried to the Hub from the user's source network.
- Interact with the Asset manager.
- Carry out trades or deposits on the Hub.
- Coordinate multi-step actions tied to that identity.
Because the wallet address is deterministic, assets can be sent to it from another network even before the wallet is deployed, so an incoming transfer is not held up by missing contract state.
The Hub Wallet does not calculate routes, move assets on its own, or decide how the liquidity inventory is used. It carries out steps the user has authorized and that a permissioned solver within the SODAX system has planned.
Why it exists
Cross-network execution needs a stable on-chain identity at the coordination layer.
Without a deterministic Hub wallet:
- Assets carried to the Hub could arrive without a defined execution surface.
- Multi-step actions would need additional message handling.
- Recovery logic would be more complex.
Hub Wallet Abstraction gives every user a predictable execution anchor on the Hub. Assets land in a known location, and actions can be coordinated without relying on external wallet state. This reduces failure modes in cross-network actions.
What this means for users and partners
For users, Hub Wallet Abstraction is invisible. A single signed intent can start a multi-step action because the system has a stable execution identity on the Hub.
For builders, it shows that user identity at the coordination layer is contract-based and deterministic, not dependent on manual wallet deployment.
Component boundaries remain clear:
- The Hub Wallet provides execution identity.
- The permissioned solver determines how an intent is filled.
- The Coordinator structures the execution steps.
- The Asset Manager moves assets into and out of the system.
- The Hub records final settlement state.
- GMP and the Relayer deliver cross-network instructions.
The Hub Wallet does not manage liquidity and does not take custody. It provides the stable identity that cross-network execution needs.
Related terms
- Deterministic execution wallets: the concept behind the Hub Wallet
- Hub: where the wallet lives and settlement is recorded
- Asset manager: moves assets in and out
- Intents: the signed request the wallet acts on
- Solver: plans and performs the fill
- Generalized Messaging Protocol (GMP): carries instructions between networks