Skip to content

Point the legacy pool at dao-docs, add the proposal format and execution checks #330

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Siegrift wants to merge 2 commits into
base: dao-section
Choose a base branch
from
Open

Point the legacy pool at dao-docs, add the proposal format and execution checks #330

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fdc27ef
Point the legacy pool at the Etherscan page in dao-docs, add the prop…
Siegrift Oct 29, 2026
99fa335
Name the dashboard's retirement date once, in the legacy DAO section
Siegrift Oct 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/dao/api3-token.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,9 @@ Posting a proposal takes 500,000 API3 of voting power (see [Posting a proposal](

The DAO pool of the legacy DAO holds staked API3.
Staking rewards ended with the migration and the pool mints nothing further.
Rewards minted before it still unlock a year after each was minted.
Staking is no longer needed to vote, staked API3 keeps voting as described under [Voting power](/dao/voting-power#what-counts), and unstaking and withdrawing work as before.
The [legacy documentation](https://dao-docs.api3.org/members/staking.html) describes the pool.
The [legacy documentation](https://dao-docs.api3.org/members/staking.html) describes the pool and how to [unstake and withdraw on Etherscan](https://dao-docs.api3.org/members/etherscan.html#unstaking-and-withdrawing).

## Collateral on Morpho

Expand Down
5 changes: 3 additions & 2 deletions docs/dao/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,5 +47,6 @@ Changes to the Snapshot settings and other rules of governance follow the [rule-
## Legacy DAO

Governance used to run on Aragon contracts, with a staking pool and a dashboard for it.
The pool is still in use: stake in it counts as voting power and pool delegations still apply to the stake, but staking is no longer needed to vote.
The [legacy documentation](https://dao-docs.api3.org/) covers the pool, the dashboard and the contracts.
The pool is still in use: stake in it counts as voting power and pool delegations still apply to the stake, but staking is no longer needed to vote and the pool pays no rewards.
The dashboard stays online until the end of March 2028 for unstaking, withdrawing and undelegating.
The [legacy documentation](https://dao-docs.api3.org/) covers the pool, the dashboard and the contracts, and how to [use the pool on Etherscan](https://dao-docs.api3.org/members/etherscan.html) without the dashboard.
11 changes: 2 additions & 9 deletions docs/dao/voting-power.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,15 +78,8 @@ Your wallet balance, deposits, unstaking amount and collateral still vote with y
The pool refuses a delegation change within a week of the last one.
After delegating, you wait a week before you can undelegate or change the delegate, and after undelegating, a week before you can delegate again.

The legacy dashboard is retained for unstaking and withdrawing, and [its documentation](https://dao-docs.api3.org/members/voting.html) describes how pool delegation worked there.
To inspect or change a pool delegation now, open the [pool contract on Etherscan](https://etherscan.io/address/0x6dd655f10d4b9E242aE186D9050B68F725c76d76#code):

1. Under **Read Contract**, call `userDelegate` with your wallet address to see its current delegate.
The zero address means no pool delegation.
2. Under **Write Contract**, connect that wallet and call `undelegateVotingPower` to clear the delegation, or `delegateVotingPower` with the new delegate's address to change it.
These are transactions and cost gas.

The one-week cooldown applies to either change.
The Undelegate button on the [legacy dashboard](/dao/#legacy-dao) clears a pool delegation.
To inspect or change a pool delegation without the dashboard, follow [Using the pool on Etherscan](https://dao-docs.api3.org/members/etherscan.html#changing-a-pool-delegation) in the legacy documentation.
The pool refuses a new delegate who is already delegating inside the pool.

### Snapshot delegation
Expand Down
14 changes: 11 additions & 3 deletions docs/dao/voting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,15 @@ Votes are public while the proposal is open.
Posting a proposal takes 500,000 API3 of voting power, held or delegated to you.
Snapshot checks it at the latest block when it receives the proposal, and the [independent verification](/dao/verification) checks it again at the proposal's snapshot block.

Proposals are discussed on the [API3 Discord](https://discord.gg/api3dao).
A proposal says exactly what it asks for: the action, the amount, the recipient, the timing and what counts as done, as far as each applies.
A rule change says which text or setting changes and to what.
The API3 multisigs do not execute a proposal that leaves any of these open.
Snapshot limits the length of a proposal, so the full text goes on IPFS and the Snapshot post carries a summary and the link.

Proposals are discussed on the [API3 Discord](https://discord.gg/api3dao), before or during the vote, and discussion is optional.

1. Open [New proposal](https://snapshot.box/#/s:api3.eth/create) in the space and connect the wallet that holds the voting power.
2. Write the title and the body.
2. Write the title, and a summary with the link to the full text as the body.
The voting system is basic voting with the choices For and Against.
3. Leave the snapshot block at its default, the latest block (see [Snapshot block](#snapshot-block)).
4. Publish by signing.
Expand Down Expand Up @@ -73,9 +78,12 @@ The [independent verification](/dao/verification) applies the rule.
## Execution

Within seven days of passing, the [API3 multisigs](/dao/#treasuries) verify the result and execute the proposal.
They also check that the proposal is fully specified and that the [charter](/dao/#governing-proposal) does not rule it out.
If they cannot execute in time, they say so publicly before the seven days are up, with the reason and a new date at most seven days later, once per proposal.

A proposal that changes the rules of governance executes 30 days after passing, and a proposal that cancels such a change executes within seven days.
The rules of governance are the voting rules, the DAO's [mandate and charter](/dao/#governing-proposal), the voting power strategy, the space settings, the verification tool, the `api3.eth` name and which multisig holds the treasury.
The rules of governance are the voting rules, the DAO's [mandate and charter](/dao/#governing-proposal), the voting power strategy, the space settings, the verification tool, the ownership of `api3.eth` and which multisig holds the treasury or executes.
An emergency move to a new Safe under the charter is confirmed by a proposal afterwards.
Whether a proposal is a rule change follows from its content, not from anything the author declares.

## Space settings
Expand Down
Loading