ARUARU
DashboardMintRedeemActivityDocs
Overview
FOR APS
ARU Overview
How It Works
Becoming an AP
Subscribing (Mint)
Redeeming (Burn)
Safeguards
Contracts & Addresses
ENGINEERING
Architecture Overview
accepted
Per-Request Flows
accepted
Auto-Signer — Bounded Automation in the Multisig
proposed
Threat Model
accepted
Deployment Ceremony & Multisig Hygiene
accepted
CI Hardening
proposed
Invariant Test Suite
proposed
Oracle Design
accepted
Audit History
shipped
ARU ENGINEERING

Docs

Design decisions, contract changes, runbooks, and threat model for the ARU protocol. Each document is versioned next to the code it governs.
3 proposed
5 accepted
1 shipped
For APsWhat APs and integrators need — overview, onboarding, mint/redeem flows, safeguards, integration reference.
ARU Overview
What ARU is, how it stays 100% backed, and what APs can do with it. Read this first.
How It Works
Visual walkthrough of the ARU mint and redeem flows — who does what, when, and what protects you at each step.
Becoming an AP
Onboarding process for Authorized Participants — KYC, AP agreement, on-chain registration.
Subscribing (Mint)
How to mint ARU by depositing USDC. Two-step flow: request with price bound, then wait for multisig approval (typically < 4h).
Redeeming (Burn)
How to redeem ARU for USDC at NAV. Two-step flow: request with minimum price bound, then wait for multisig approval.
Safeguards
What protects APs, ARU holders, and integrators from contract bugs, admin misbehavior, and operational failure. Read this to understand the trust model.
Contracts & Addresses
Deployed contract addresses, key ABIs, and integration notes for APs and downstream protocols.
EngineeringInternal design, threat model, deployment ceremony, audit history, and proposals for future changes.
Architecture Overview
accepted
High-level view of the ARU protocol contracts, roles, and data flows. Read this first before diving into individual engineering docs.
Per-Request Flows
accepted
Full design spec for ARUSubscriptionManager. Per-request submission bound by AP-specified price range, multisig approval within bounds, permissionless 48h expiry reclaim.
Auto-Signer — Bounded Automation in the Multisig
proposed
Operational pattern for reducing required human signatures on routine per-request settlements. An automated signer participates in the multisig and signs only when the proposed settlement price is within NAV tolerance. Pairs with Per-Request Flows.
Threat Model
accepted
Explicit trust boundaries, admin-key powers, compromise scenarios, and accepted risks for the ARU protocol.
Deployment Ceremony & Multisig Hygiene
accepted
Step-by-step ceremony for deploying ARU contracts, bootstrapping minter timelock, onboarding APs, and operating the multisigs. Written to be followed cold.
CI Hardening
proposed
GitHub Actions pipeline, static analysis, dependency pinning, review policy, and release gates for the aru-evm repo.
Invariant Test Suite
proposed
Foundry invariant test harness covering settlement correctness, accounting totals, and token conservation. Preventive — catches the class of bug in Findings
Oracle Design
accepted
ARUPriceOracle design — Chainlink-compatible AggregatorV3 interface, rate-of-change guard, strict variant for downstream integrators that want hard-fail on stale price.
Audit History
shipped
Record of external and internal security review of the ARU contracts. The active v2 design was audited by Nethermind Security (NM-0902) with zero findings; v1 review findings are retained below for the audit trail.