Deterministic execution wallets
Deterministic execution wallets are system-generated smart wallets that provide each user with a consistent identity and execution account across all supported networks.
What it refers to
Deterministic execution wallets are smart wallets that SODAX automatically generates for each user on the Hub network. They provide a consistent execution identity that persists across all cross-network actions, regardless of which Spoke network the user initiates from.
The wallet is deterministic: given the same user identifier (their source wallet address), the system always derives the same Hub wallet. This means a user interacting from Base, Arbitrum, or Solana is always recognized as the same entity on the Hub.
Why this concept exists
In multi-network environments, users typically have separate wallets and identities on each network. There is no built-in way for a system to recognize that the same person is acting across Arbitrum and Solana.
This creates problems for cross-network execution:
- State (such as lending positions or pending intents) cannot be unified
- Each network interaction appears as an independent event
- Applications must manage identity mapping themselves
Deterministic execution wallets (often searched as smart wallet abstraction or cross chain account abstraction) solve this by creating a unified account on the Hub that maps to the user's wallets on every Spoke. The Hub wallet becomes the single source of truth for that user's state across the entire system.
What this changes for system design
Deterministic wallets enable several system capabilities:
- Unified state: a user's lending positions, pending intents, and balances are managed through one Hub account
- Simplified execution: applications route all cross-network operations through a single wallet context
- Consistent identity: the system can enforce rate limits, permissions, and constraints per user across all networks
- Wallet generation without user action: the system creates Hub wallets as needed, without requiring users to deploy contracts or complete additional transactions
The concept shifts identity management from the application layer to the infrastructure layer, making cross-network coordination a system-level capability rather than an application-level integration challenge.
