One chain, shared state, external reach

One chain, shared state, external reach An architecture diagram generated by Archify. CLI + SDK clients · signed transactions · Architecture component CLI + SDK clients signed transactions RPC + mempool · decode and verify · Architecture component RPC + mempool decode and verify Simplex consensus · decide block order · Architecture component Simplex consensus decide block order Ordered execution · deterministic results · Architecture component Ordered execution deterministic results Execution environments · SVM · EVM · WASM · Move · ZK · Bombil · Runtime-specific effects share the local state boundary · Bombil resident CUDA: gated Execution environments SVM · EVM · WASM · Move · ZK · Bombil Bombil resident CUDA: gated Transaction journal · authority + staged effects · Runtime-specific effects share the local state boundary Transaction journal authority + staged effects Shared accounts · one local state transition · Runtime-specific effects share the local state boundary Shared accounts one local state transition State persistence · WAL, height and QMDB · Architecture component State persistence WAL, height and QMDB External chains · source evidence · Architecture component External chains source evidence HILSA · verified foreign context · Architecture component · committed snapshots HILSA verified foreign context committed snapshots submit transactions ordered payload dispatch staged effects common commit durable writes verify evidence verified foreign context Runtime-specific effects share the local state boundary

The environments have different interface boundaries

  • • Bombil’s resident CUDA runtime remains gated. Each environment has its own entrypoints and compatibility boundaries.

Local atomicity has a precise scope

  • • A local journal can commit or roll back its effects. External settlement remains asynchronous and has separate completion rules.