Reference
Further reading
This site covers the protocol. The material below lives next to the code it describes and is not searchable from here. Each link opens the current version on GitHub.
Run something
| Document | Who it is for | What it covers |
|---|---|---|
| Statoblast liquidator | Vault operators and keepers | Monitoring pool health, staging and executing liquidations, and the bot's dashboard. |
| OpenOracle arbitrager | Price correctors | Finding mispriced REP/ETH reports, funding disputes against Uniswap quotes, executor deployment, and settlement tracking. |
| Chaos bot and its operator reference | Testnet operators | Exercising every permissionless protocol path with real transactions, safety limits, and runtime controls. |
| augurScan, its operations guide, API reference, and state model | Indexer operators and integrators | The read-only protocol explorer: deployment, backup and upgrade, the HTTP API, and how retained evidence differs from the current view. |
| Local test network and Sepolia Reth node | Developers and node operators | Docker Compose setups for the repository-pinned Anvil chain and a pruned Sepolia execution and consensus pair. |
Read the code
| Document | Who it is for | What it covers |
|---|---|---|
| Repository README | Contributors | Setup, local development, simulation mode, common commands, and validation. |
| Contract layout and the Statoblast contract directory | Auditors and contract developers | Why source paths are stable, which directory owns which contracts, and the OpenOracle vendoring boundary. |
| Security regression suite | Auditors | The focused tests that reproduce past security findings and how to add one. |
| Shared TypeScript packages and core UI ownership | Front-end and tooling contributors | Package boundaries, build dependencies, and which layer may import which. |
| Statoblast test slices | Contract developers | How the split Statoblast suites are run individually and together. |
| Security pool workflow test slices | Front-end contributors | How the split security-pool workflow suites of the Statoblast UI are run individually and together. |
| Token authorization provenance | Auditors | Where the EIP-712 and ECDSA signature helpers come from and what was changed. |
| augurScan backend boundaries | Indexer contributors | Which backend directory owns HTTP, scanning, storage, and evidence types. |
| UI features, UI protocol client, and UI copy modules | UI contributors | Where feature components, typed contract reads and writes, and user-facing text live, and which may import which. |
| Visual foundation | UI contributors | The shared design tokens, product accents, and status treatments used by every interface. |
Understand the design history
The oracle-research repository holds the proposals, rejected alternatives, and open questions behind the protocol. It explains why the design looks the way it does; the deployed contracts and this site's reference pages describe what it actually does today.