Noesea

Governance

Rules that cannot be quietly changed.

What Noesea governance can change, and what no one can.

01

Governance governs the protocol, never the truth of a claim. No governance vote, token holder, team key or operator can declare a claim true or false, override a verdict, choose a panel or change a vote.

02

Adjudication rules — panel selection, commit and reveal windows, quorum, verdict and slashing math — are fixed in each deployment, and every dispute records the rule snapshot it ran under. Token governance cannot change them.

03

Token governance holds a narrow, enumerated surface: bounded fee settings, emission allocation and treasury withdrawals, each behind a public vote and a timelock.

04

Deployment-team roles are handed to on-chain governance before the first claim can be registered, and the resulting authority map can be read back from chain.

Authority surfaces

Fees & emissions — governed

Fee levels and splits within hard on-chain ceilings, emission allocation and the reward-claim fee. Changes need a public token vote and a timelock, and can be vetoed during the security council's limited term.

Treasury — governed

Treasury withdrawals execute only from a passed governance proposal, in public.

Dispute & slashing rules — not governed

Selection, timing, quorum, verdict and slashing rules are constants of the deployment. A change cannot reach an active or finished case.

Upgrades — none

Core contracts are not upgradeable. A new rule set ships as a successor deployment that participants choose to adopt. Earlier verdicts stay on chain, and anyone can re-derive them with noesea verify-verdict.

Deployed authority explorer

Inspect a signed release manifest

The manifest binds each privileged selector to its live authority, control domain, delay, veto or appeal, fixed sunset, pending acceptance, and public recovery path.

No release is assumed. Open a manifest obtained from a channel you explicitly trust; its checkpoint and deployed bytecode can then be verified through the SDK against your own RPC endpoints.

Related