# \[ARFC ADDENDUM\] Updating rules for ARFC and TEMP CHECK Proposals **URL:** \ **Category:** Governance\ **Created:** [December 31, 2025, 5:43pm UTC](https://governance.aave.com/t/arfc-addendum-updating-rules-for-arfc-and-temp-check-proposals/23786 "2025-12-31T17:43:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Codeknight](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@Codeknight](https://governance.aave.com/u/Codeknight)\ **Post date:** [December 31, 2025, 5:43pm UTC](https://governance.aave.com/t/arfc-addendum-updating-rules-for-arfc-and-temp-check-proposals/23786/1 "2025-12-31T17:43:35Z")
**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](https://creativecommons.org/publicdomain/zero/1.0/). ---
**Author:** ![MarcZeller](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/marczeller/32/7124_2.png) [@MarcZeller](https://governance.aave.com/u/MarcZeller)\ **Post date:** [January 5, 2026, 8:22am UTC](https://governance.aave.com/t/arfc-addendum-updating-rules-for-arfc-and-temp-check-proposals/23786/2 "2026-01-05T08:22:40Z")
Hello, Thanks for submitting this proposal, It’s a welcome addition to fix the previous loophole exploited recently. I think we should do a larger revisit of the framework, but this quick fix is a good idea, thanks for leveraging the ARFC ADDENDUM tool that was meant for these small scope proposals. ---
**Author:** ![Codeknight](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@Codeknight](https://governance.aave.com/u/Codeknight)\ **Post date:** [January 7, 2026, 2:03pm UTC](https://governance.aave.com/t/arfc-addendum-updating-rules-for-arfc-and-temp-check-proposals/23786/4 "2026-01-07T14:03:51Z")
Sounds good. I am ready to escalate to snapshot. ---
**Author:** ![ACI](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/aci/32/4780_2.png) [@ACI](https://governance.aave.com/u/ACI)\ **Post date:** [January 8, 2026, 9:02am UTC](https://governance.aave.com/t/arfc-addendum-updating-rules-for-arfc-and-temp-check-proposals/23786/5 "2026-01-08T09:02:03Z")
The current proposal has been escalated, under Skywards, with explicit consent from the author, @Codeknight, to [ARFC Addendum Snapshot](https://snapshot.org/#/s:aavedao.eth/proposal/0x0845c742ab78f256a7992aa467015a4353e09809fea4381295e0b7d588b411d1). Vote will start tomorrow, we encourage everyone to participate. ---
**Author:** ![ACI](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/aci/32/4780_2.png) [@ACI](https://governance.aave.com/u/ACI)\ **Post date:** [January 12, 2026, 9:42am UTC](https://governance.aave.com/t/arfc-addendum-updating-rules-for-arfc-and-temp-check-proposals/23786/6 "2026-01-12T09:42:30Z")
The current [ARFC Addendum Snapshot](https://snapshot.org/#/s:aavedao.eth/proposal/0x0845c742ab78f256a7992aa467015a4353e09809fea4381295e0b7d588b411d1) has just ended, reaching out both YAE and Quorum with 648K votes. Therefore, [[ARFC ADDENDUM] Updating rules for ARFC and TEMP CHECK Proposals ](https://governance.aave.com/t/arfc-addendum-updating-rules-for-arfc-and-temp-check-proposals/23786) has PASSED. This proposal is Canon now, meaning that from now on, every proposal that needs to be escalated to either TEMP CHECK Snapshot, ARFC Snapshot, ARFC Addendum Snapshot, need explicit consent from the author to be escalated, shared via forum in the same proposal, in those cases where the a third party is the one submitting it for a vote. ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/aave/original/2X/e/e11637c36f45ffa158f2146f5c19438d46e0824d.svg) [@system](https://governance.aave.com/u/system)\ **Post date:** [February 11, 2026, 9:43am UTC](https://governance.aave.com/t/arfc-addendum-updating-rules-for-arfc-and-temp-check-proposals/23786/7 "2026-02-11T09:43:12Z")
Closed on February 11, 2026, 9:43am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.