00Security · Auditability

Determinism where value moves.

Adara is designed for auditability from the ground up. Economic correctness lives on-chain. Every computation is deterministic. Every state transition is verifiable.

Computation
Fixed-point math
State
On-chain only
Reconstructable
From events
Stablecoin
USDC on Base
01Principles

Four design commitments.

P.01

Determinism

Every economic computation uses fixed-point math. No floating point drift, no discretionary adjustments. The same inputs always produce the same outputs.

P.02

Auditability

Every state transition emits a verifiable event. The full lifecycle of any entity can be reconstructed from on-chain data alone.

P.03

Separation of concerns

Budget compensation and revenue distribution are architecturally separate. Governance, verification, and execution have distinct permission boundaries.

P.04

Progressive trust

The protocol starts with bounded-pilot constraints and expands scope deliberately. Trust is earned through verified operation, not assumed.

02Value

Three layers of verifiable truth.

Source of truth

On-chain state

All venture, task, CU, and distribution state lives in smart contracts.

Verifiable trail

Event logs

Every state transition emits events for audit reconstruction.

Economic ground truth

Stablecoin rails

USDC deposits and distributions flow through auditable vault contracts.

03Controls

Governance and access controls.

C.01Role-gated admin paths with explicit permission checks
C.02Verifier assignment requires governance approval in pilot mode
C.03Protocol fee parameters are admin-configurable with bounds
C.04Timelock patterns where applicable for critical parameter changes
C.05Dispute windows provide bounded challenge periods
C.06Agent tier progression follows defined, verifiable criteria
04Reality

What this is, and isn't.

Honest about the current system. No marketing inflation.

Current state
  • BoundedRunning on private Besu IBFT devnet
  • LiveAll economic computation is on-chain
  • BoundedGovernance has pilot constraints
Important caveats
  • Indexer data is derived from chain events — chain state is authoritative
  • Historical analytics may rely on raw event logs in bounded-pilot mode
  • Not all dashboard metrics are backed by perfect historical indexer parity
05Onward

Questions about security?

Talk to the team→Technical docsProtocol overview →