Sudont supports two virtual machines: the Ethereum Virtual Machine (EVM) and the
Solana Virtual Machine (SVM). Both are first-class citizens.
A single CanonicalIntent carries a vm_type field that routes it to the correct Cage
implementation. The architecture is unified at the type level — the Judge and the rest of the
pipeline are completely VM-agnostic.
Defined in sudont-types, SimulationEngine is the contract both Cage implementations fulfill:
SimulationEngine — VM-Agnostic Interface
/// Both EVM and SVM cages implement this trait.pub trait SimulationEngine: Send + Sync { fn simulate(&self, intent: &CanonicalIntent) -> Result<SimOutcome, String>;}
The CanonicalIntent input carries the vm_type discriminant:
VmType Enum
pub enum VmType { Evm, Svm,}
The RPC layer reads vm_type and dispatches to the correct SimulationEngine implementation
at runtime — no conditional logic needed in the Judge or policy layers.
Precise gas computation and revert reason extraction
EIP Support
EIP-3607 and active EIPs via feature flags
State source: Local Base reth node with Flashblocks support. The simulation reflects the
pending world, not a stale cache.Supported protocols: Uniswap V3 (exactInputSingle, exactInput), Aerodrome router swap flows.
The Judge uses asset_changes to compute effective slippage and price impact against the
CanonicalIntent’s amount_out_min and slippage_bps fields.
Rust crate:sudont-cage-svmDependency:litesvmThe SVM Cage implements the same SimulationEngine trait for Solana transactions:
SVM SimulationEngine
pub struct SvmSimulator;impl SimulationEngine for SvmSimulator { fn simulate(&self, intent: &CanonicalIntent) -> Result<SimOutcome, String> { // intent.data holds the serialized Solana transaction bytes // The simulator deserializes into VersionedTransaction, // executes inside LiteSVM, and returns native logs + state diffs. }}
LiteSVM is a fast in-process Solana runtime that executes transactions without a validator:
State Hydration
Account state from RPC snapshots
Full Execution
Instruction-level Solana program execution
Log Capture
Compute unit accounting and log output
Mainnet Compatible
Supports loading real SBF binaries when needed
The TypeScript SDK accepts native Transaction / VersionedTransaction objects, serializes them
to base64, and the RPC sidecar routes the decoded bytes into sudont-cage-svm with
vm_type: Svm.
The TypeScript SDK exposes vmType as a constructor parameter:
import { SudontClient } from '@sudont/sdk';// Routes to sudont-cage (revm)const evmClient = new SudontClient('http://localhost:8545', 'evm');
On the server side, the JSON-RPC layer reads vmType from the incoming request and selects the
appropriate SimulationEngine implementation. The Judge, Constitution, and diagnostic machinery
are shared — only the simulation backend differs.
