Onyxdao governance

Onyx Chain assigns one unit of voting weight for each stXCN held by an address at the proposal's snapshot block. The recorded balance includes staking rewards accrued by that block. Native XCN held unstaked, WXCN, and liquidity-provider tokens contribute zero voting weight in this system.

Staking after the snapshot adds no weight to that proposal. Transferring or unstaking stXCN afterward leaves the already-recorded weight unchanged; future snapshots reflect the later balances. The documented native system has no separate delegation registry, so voting weight belongs to the address holding stXCN at the snapshot.

Eligibility Snapshot

A rolling record used for proposal creation. A proposer must prove enough voting weight against the latest finalized eligibility snapshot to meet the proposal threshold.

Proposal Snapshot

A record fixed for one OIP and permanently bound to it at creation. It determines the electorate, each address's voting weight, and the eligible supply used for that proposal's quorum.

The Snapshot Registry stores a Merkle root, a cryptographic commitment to the address-and-weight records, together with the snapshot block, eligible supply, and policy version. Both snapshot types pass through publication, a one-day challenge window, and finalization. An independent challenger recomputes the records; a disputed incorrect root must be replaced, and a guardian can veto a bad root.

The Governor accepts only finalized snapshots. When a vote is submitted through the Onyx App, the app attaches a Merkle proof linking the address and its weight to the proposal's snapshot root. A missing, invalid, or mismatched proof cannot establish voting power.

View full-size image

The native proposal threshold applies to creating an OIP with a human-readable description and exact on-chain actions specified for execution. An address with any positive stXCN weight in a proposal's finalized snapshot can vote during its active voting period, provided its vote includes a valid proof.

Proposal Threshold

The greater of 100,000,000 XCN of staked voting weight or 0.10% of eligible staked supply, capped at 1,000,000,000 XCN of weight. The proposer must satisfy this threshold using the latest finalized eligibility snapshot.

Quorum

The greater of 200,000,000 XCN of staked voting weight or 2.00% of eligible staked supply, capped at 1,000,000,000 XCN of weight. The proposal snapshot fixes the relevant supply. Only For votes count toward quorum.

Approval

For votes must reach quorum and strictly exceed Against votes. Against votes affect the majority comparison but do not help reach quorum. Abstain votes count toward neither quorum nor the majority.

Participation Above Quorum, Support Below It

In this hypothetical Onyx Chain proposal, assume eligible staked supply leaves quorum at the documented floor of 200,000,000 units of voting weight. Every vote total below is hypothetical and represents stXCN snapshot weight at the close of voting.

For

196,482,718 units of voting weight.

Against

18,743,506 units of voting weight.

Abstain

7,291,604 units of voting weight.

Total participation is 222,517,828 units, but only the 196,482,718 For units count toward quorum. For exceeds Against, yet affirmative support is 3,517,282 units short of quorum, so the proposal fails. With the same quorum and Against tally, For would have needed another 3,517,282 units to satisfy both approval conditions; additional Against or Abstain weight would not close that shortfall.

View full-size image

Voting Delay

Onyx Chain proposals have a one-day delay after creation before voting opens. Voting weight is already fixed by the proposal snapshot.

Voting Period

The native voting window lasts two days, with For, Against, and Abstain options. The Ethereum governance overview describes a separate three-day voting period for its own Governor; that timing does not apply to the native Onyx Chain system.

Timelock

An approved proposal must be queued into the Timelock, which imposes a mandatory two-day delay before execution can occur. The guardian can cancel a malicious or defective proposal before execution.

Execution

After the delay, anyone can trigger execution if the queued proposal has not been canceled. The Timelock performs the proposal's approved on-chain actions. A successful vote or a queued proposal is an earlier state than completed execution.

The documented minimum from Onyx Chain proposal creation to execution is about five days: a one-day voting delay, two days of voting, and a two-day Timelock. Snapshot preparation and its one-day challenge window precede creation. Queuing and triggering execution remain necessary actions, so the minimum timeline does not promise completion at a fixed time.

View full-size image