Documentation
Everything Atrium does is documented on this site: the architecture, the API, the operational runbooks, the security posture, and an honest account of what is real on testnet versus what is still relayed or mocked. Start anywhere below.
Product & architecture
What Atrium is, how the system fits together, and the decisions behind it. One margin account across venues, with the contracts and the math laid out.
Architecture
One margin account, many venues. Twenty-four contracts on Arbitrum Sepolia with an interactive system map and a position traced end to end.
system map · verified addresses
Architecture decision records
ADR-001 through ADR-012: Stylus over Solidity, Kani over Halmos, the dual-oracle median, UUPS upgradeability, the open IPorticoAdapter, and more, with the alternatives rejected.
12 decisions
Glossary
Every subsystem name (Plinth, Sigil, Lantern…) in plain English: what it is and what it does for you.
18 subsystems · plain language
API
The Codex HTTP API: pay-per-call margin and risk reads, with quickstart and SDK snippets.
Operations
How Atrium runs day to day, and exactly what is deployed on-chain. Read the playbooks and the live registry yourself.
Honesty & what is real
Where the testnet falls short of production, named line by line. No mock shown as real, no number without a source.
Security
Threat model, key handling, and how to report a vulnerability.
Getting started
For a first read: walk the product, then verify it yourself against the chain.
Getting started
From zero to your first cross-margin trade. Eight short steps in plain language on a free testnet. No prior crypto experience needed.
8 steps · testnet
Verify
Seven steps, each backed by a real contract call on Arbitrum Sepolia: deposit, open, margin, chaos, liquidation, proof-of-reserves, kill switch.
7 steps · on-chain
Adapter spec
IPorticoAdapter v1.0 + v1.1 with explicit originator. MIT-licensed. Curator grants will pay $5K ARB per accepted adapter, after testnet launch.
Sigil schema
EIP-712 IntentSigil + ActionSigil envelopes. 256-byte fixed body, count-prefixed venues/instruments (max 8 each), 65-byte trailing sig.
ReadSPAN scenarios
7 shock scenarios (±10%, ±5%, ±2%, 0) per instrument, sourced tospan.rs SCENARIOS_BPS, with cross-correlation netting across instruments in the same correlation class.
The full product spec, technical design, and reference docs are open source in the repository. github.com/Pratiikpy/atrium