Governance sources, verification, and discrepancies¶
Integrated sources¶
- DAO DApp README: wallets, BPs, proposals, and community entry points.
- Governance user help: power, phases, risk, and rewards.
- Operations guide and Keeper README: newer role/operations boundaries.
- Interface phase derivation: explains the interface, not authoritative chain validation.
- DAO implementation and interface/tables.
- Treasury implementation, BP voting, and reward claiming.
- Mainnet read-only responses and code hashes, 2026-11-02, with interpretation.
A local mainnet operations draft dated 2026-11-01 was also reviewed. It was uncommitted in the DApp repository and partly outdated, so it was not directly published as current configuration.
Resolving source differences¶
| Source statement | Verified behavior / treatment |
|---|---|
| Allocation sum must not exceed principal | Listed system source requires equality with target locked principal; the guide states that constraint. |
| reserve reduces liquid / release restores liquid | Source reserve increases reserved only; release decreases reserved only. Available balance is liquid - reserved. |
| closegrant closes completed/released grants | Listed source accepts only open, expired grants; completed/released are other terminal states. |
| Keeper drives external closeepoch | New operations documentation describes onblock closure and reward-claim assistance; verify the deployment version. |
| New guide includes standbyproof | Observed mainnet ABI lacks it; described conditionally, not as a live mainnet command. |
| November 1 mainnet allowlists empty, higher thresholds | November 2 reads show five enabled entries and changed thresholds; publish dated evidence instead of static current-state claims. |
| Endorsement and formal votes use one snapshot | Source accumulates endorsement-time power without per-account activation recomputation; formal votes read activation checkpoints. |
| Proposal stores full per-action authorization | proposal_action stores target/action/bytes; authorization comes from allowlist, is immutable for existing rules in the reviewed version, and is checked again at execution. |
Verification limits¶
Read-only queries verify chain ID, tables, code hashes, and ABI action presence. They are not protocol audits, liveness audits, or reproducible source-to-WASM proofs. Independent reads are not an atomic single-block snapshot. Values change; mainnet and testnet need separate confirmation.