• © Goverland Inc. 2026
  • Privacy Policy
  • Terms of Use
Aave DAOAave DAOby0xF1dF824419879Bb8a7E758173523F88EfB7Af193XG177

[ARFC ADDENDUM] Updating rules for ARFC and TEMP CHECK Proposals

Voting ended 23 days agoSucceeded

Summary

Before a proposal is brought to a vote by a 3rd party, the proposer must indicate they wish to submit that proposal a vote.

Motivation

Recent events have highlighted this gap in the proposal rules. Submitters should have time to revise proposals and should not have their name attached to a proposal they have not chosen to submit.

I am open to consider other proposal related rules that the community thinks should be included.

Details

The proposer must indicate they wish to have a proposal submitted before a 3rd party can submit it for a vote, such as by replying “formally submitting” on the proposal’s forum thread.

Specification

As this proposal pertains to governance guidelines, it does not require any on-chain action or protocol change.

Disclaimer

Codeknight is not presenting this ARFC on behalf of any third party and is not compensated for creating this ARFC.

Next Steps

  1. If consensus is reached on this ARFC, escalate this proposal to the Snapshot stage.

  2. If the Snapshot outcome is YAE, this proposal will be considered canon, and the guidelines will be adopted.

Copyright

Copyright and related rights waived via CC0.

Off-Chain Vote

YAE
648.42K AAVE100%
NAY
0.01 AAVE0%
Abstain
0.1 AAVE0%
Download mobile app to vote

Discussion

Aave DAO[ARFC ADDENDUM] Updating rules for ARFC and TEMP CHECK Proposals

Timeline

Jan 08, 2026Proposal created
Jan 09, 2026Proposal vote started
Jan 12, 2026Proposal vote ended
Feb 03, 2026Proposal updated