GOVERNANCE BUILT FOR CREDIBILITY, NOT VIBES

GOVERNANCE BUILT FOR CREDIBILITY, NOT VIBES

GOVERNANCE BUILT FOR CREDIBILITY, NOT VIBES

Authra runs on transparent, parameterized rules with checks & balances—force-inclusion for censorship resistance, an auditable AnyTrust DAC, a Security Council for emergencies, and usage-linked buy-&-burn.

RReeaadd  GGoovveerrnnaannccee  FFrraammeewwoorrkk
RReeaadd  GGoovveerrnnaannccee  FFrraammeewwoorrkk

Why Governance matters here

Authra’s Three-Trust Fabric turns everyday devices into signed, privacy-preserving sensors and anchors those proofs to an Arbitrum Orbit L3. Governance defines how parameters change, who can act in emergencies, and the transparency users can rely on. 

Governance bodies

Community governance

Sets protocol thresholds (e.g., force-inclusion window, sequencer failover), via public RFCs and on-chain votes. 

Community governance

Sets protocol thresholds (e.g., force-inclusion window, sequencer failover), via public RFCs and on-chain votes. 

Security Council

May enact temporary overrides behind a timelock; mandatory public post-mortems. Also owns select security-critical parameters (e.g., PQC migration, certain privacy thresholds).

Security Council

May enact temporary overrides behind a timelock; mandatory public post-mortems. Also owns select security-critical parameters (e.g., PQC migration, certain privacy thresholds).

Foundation / Treasury stewardship

Holds & disburses funds for development, grants, and ecosystem growth under community oversight.

Foundation / Treasury stewardship

Holds & disburses funds for development, grants, and ecosystem growth under community oversight.

Community governance

Sets protocol thresholds (e.g., force-inclusion window, sequencer failover), via public RFCs and on-chain votes. 

Security Council

May enact temporary overrides behind a timelock; mandatory public post-mortems. Also owns select security-critical parameters (e.g., PQC migration, certain privacy thresholds).

Foundation / Treasury stewardship

Holds & disburses funds for development, grants, and ecosystem growth under community oversight.

Parameterized protocol (defaults at genesis)

Censorship resistance:

Delayed Inbox force-inclusion 24h (range 12–48h). 

Sequencer liveness:

Auto-rotate after N=3 missed intervals (range 1–6).

Data availability:

AnyTrust DAC (publish member list, M-of-N quorum, rotation cadence). Rollup fallback is Plan-B. 

Timeboost auctions:

Off at genesis; governance-toggleable. 

Emissions split:

0/40/20 (Mobile/Challengers/Treasury); epoch length 30 days, decaying schedule within bounds.

Supply:

Hard-cap 1,000,000,000 ATRX; rewards are time-release from a pre-minted community pool (no net new supply). 

Buy-&-burn:

30% of net enterprise fees used to purchase and burn ATRX; quarterly reporting. 

All defaults are subject to governance and
Security Council safeguards where noted. 

Transparency & auditability

Public logs:

Weekly attestation reports; Merkle-rooted inclusion/latency logs and DAC signature sets committed on-chain. 

Chain-Health Oracle (0–100):

REST + WS endpoints publish sequencer uptime, inclusion latency, delayed-inbox depth, DAC quorum freshness, anchor lag, and dispute metrics; weights and alert thresholds are governed on-chain. 

Liveness & censorship resistance

User path if censored

Anyone can force-include via the Delayed Inbox after the window elapses; CLIs/UI documented. 

Failover

On missed intervals the sequencer auto-rotates to hot standby; rotation events and last inbox hash are posted on-chain. 

Compliance & privacy (governed controls)

Data minimization & pseudonymization

Delayed Inbox force-inclusion 24h (range 12–48h). 

Modular compliance modes:

(Global, Enterprise/KYB, Regulated) enforced on-chain. 

Retention:

Raw telemetry 90 days by default; region overrides allowed, with hashed commitments persisting on-chain. 

Economic alignment

Hard cap & allocations

published; emissions are time-release (not inflation), with public unlock charts. 

Buy-&-burn target

links utility to scarcity; governance discloses quarterly burn vs. releases. 

Guardrails

Emission ratchets and “usage-to-burn” targets align supply with real utility. 

How a change happens (typical flow)

Public RFC → 2) On-chain vote → 3) Timelocked execution;

emergency overrides only by the Security Council with mandatory post-mortem. 

Roadmap items governed over time

Timeboost

(priority auctions) → chain-opt-in controlled by governance. 

Broaden DAC membership

and evaluate alternative DA providers as they mature. 

FAQ

FAQ

FAQ

Who can run a challenger?

Anyone; hardware specs and Docker references will be documented. Rewards for valid disputes; spam penalized per governance.

How do I monitor chain health?

Use the Chain-Health Oracle: GET /api/v1/oracle/chain_health and WS /stream/chain_events.

What if the DAC fails or regulators require stricter DA?

We flip to Rollup mode via a planned regenesis with dual-run and state snapshot.

What’s the anti-censorship path for users?

Submit via the Delayed Inbox; transactions must be processed after the window closes.

Who can run a challenger?

Anyone; hardware specs and Docker references will be documented. Rewards for valid disputes; spam penalized per governance.

How do I monitor chain health?

Use the Chain-Health Oracle: GET /api/v1/oracle/chain_health and WS /stream/chain_events.

What if the DAC fails or regulators require stricter DA?

We flip to Rollup mode via a planned regenesis with dual-run and state snapshot.

What’s the anti-censorship path for users?

Submit via the Delayed Inbox; transactions must be processed after the window closes.

Who can run a challenger?

Anyone; hardware specs and Docker references will be documented. Rewards for valid disputes; spam penalized per governance.

How do I monitor chain health?

Use the Chain-Health Oracle: GET /api/v1/oracle/chain_health and WS /stream/chain_events.

What if the DAC fails or regulators require stricter DA?

We flip to Rollup mode via a planned regenesis with dual-run and state snapshot.

What’s the anti-censorship path for users?

Submit via the Delayed Inbox; transactions must be processed after the window closes.

Sign in to newsletter and never miss any update.

Navigation

Home

Home

Protocol

Protocol

Ecosystem

Ecosystem

Blog

Blog

About

About

Legal

Privacy Policy

Privacy Policy

Terms of Service

Terms of Service

Disclosures

Disclosures

Security

Security

Whitepaper

Whitepaper

Support Wallet

Support Wallet

Grants & Parterships

Grants & Parterships

© 2025 Authra. All rights reserved.

Sign in to newsletter and never miss any update.

Navigation

Home

Home

Protocol

Protocol

Ecosystem

Ecosystem

Blog

Blog

About

About

Legal

Privacy Policy

Privacy Policy

Terms of Service

Terms of Service

© 2025 Authra. All rights reserved.

Sign in to newsletter and never miss any update.

Navigation

Home

Home

Protocol

Protocol

Ecosystem

Ecosystem

Blog

Blog

About

About

Legal

Privacy Policy

Privacy Policy

Terms of Service

Terms of Service

© 2025 Authra. All rights reserved.