System Architecture
13 contracts across four layers. Each layer has a single responsibility. Value flows inward, governance ratchets upward, nothing flows back.
Contract Layers
Core
Bridge, UCU token, supply control, and compute distribution
Identity
Citizenship, sovereignty scoring, and support classes
Governance
Quadratic voting, conviction weighting, and constitutional limits
Oracle
Compute basket pricing and creator grant verification
Token Flow
UCU lifecycle from L1 deposit to burn. Every token enters through the bridge and either circulates or gets burned. None leave.
Contract Dependencies
Which contracts reference which. The dependency tree flows from Governor at the top down to the leaf contracts with no dependencies.
One-Way Design
Why no withdraw()?
The bridge has no withdraw() function. Not disabled, not paused, not behind a flag. It was never written. This is a deliberate architectural decision, not a missing feature.
Economic Irreversibility
UCU is a compute unit, not a speculative asset. Once USDC enters the SVRN economy, it becomes compute capacity. Reversing that would undermine the entire pricing model tied to the compute basket.
L2ToL1MessagePasser
The standard OP Stack L2ToL1MessagePasser at 0x4200...0016 is replaced with a contract that reverts unconditionally on initiateWithdrawal().
Deflationary Pressure
With no exit, value that enters must circulate or burn. The Bonfire mechanism permanently destroys surplus UCU each epoch, creating natural deflation as the economy grows.