EVM and non-EVM
EVM networks run the Ethereum Virtual Machine and share its smart contract environment, while non-EVM networks such as Bitcoin, Solana, Sui and Stellar run their own execution environments. SODAX operates across 20+ networks of both kinds, including native Bitcoin, and takes the differences between them off the hands of apps that call the SODAX API.
What it refers to
EVM stands for Ethereum Virtual Machine, the environment that runs smart contracts on Ethereum. EVM networks, such as Ethereum, Arbitrum, Base and Avalanche, run the same kind of virtual machine, so they share smart contract languages, an account and address format, and most developer tooling (often searched as EVM vs non-EVM chains).
Non-EVM networks run their own execution environments. Bitcoin records balances as unspent transaction outputs and has a deliberately limited scripting language. Solana, Sui and Stellar each have their own contract model, transaction format and address format.
Why this concept exists
The split decides how much work it takes to support a network. Contracts, wallets and tooling written for one EVM network carry over to another with few changes. Each non-EVM network needs its own contracts, transaction handling and integration work, so many apps and services support only EVM networks, or only a few networks of either kind.
What this changes for system design
A system that works across both kinds of network has to handle different account models, transaction formats, fee mechanics and confirmation timing, and still treat a financial action as one request.
SODAX operates across 20+ networks, EVM and non-EVM, including native Bitcoin. It follows a hub-and-spoke architecture: a spoke on each network accepts the action, and the Hub keeps the accounting and settles. Apps that call the SODAX API do not have to handle EVM and non-EVM differences themselves: SODAX takes transaction construction, routing and multi-step coordination across both kinds of network off their hands.
Related terms
- Native Bitcoin: Bitcoin as a non-EVM network
- Hub-and-spoke architecture: one design across both kinds of network
- Spoke: the local endpoint on each network
- Cross-network execution: actions that span EVM and non-EVM networks
- Chain abstraction: removing network-specific steps
- SODAX System: the 20+ networks it spans