# RFC: Raise OPEN’s proposal threshold and quorum **URL:** \ **Category:** OPEN Stablecoin DTF\ **Created:** [October 18, 2026, 11:16pm UTC](https://forum.reserve.org/t/rfc-raise-open-s-proposal-threshold-and-quorum/1668 "2026-10-18T23:16:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![0xJMG](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.reserve.org/0xjmg/32/1104_2.png) [@0xJMG](https://forum.reserve.org/u/0xJMG)\ **Post date:** [October 18, 2026, 11:16pm UTC](https://forum.reserve.org/t/rfc-raise-open-s-proposal-threshold-and-quorum/1668/1 "2026-10-18T23:16:04Z")
Recent malicious OPEN proposals sought administrative and rebalance permissions, forcing holders to organize repeated defensive votes. I propose raising the voting power needed to submit proposals and the participation required to meet quorum. Across **Basket governance, DTF governance, and DAO governance** , this proposal would change: - **Proposal Threshold from 1% to 5%.** A proposer would need 5% of the total staked voting power, held directly or delegated to them. - **Quorum from 10% to 15%.** For and Abstain votes would need to represent 15% of total staked voting power. Against votes do not count toward quorum. The [current OPEN settings](https://app.reserve.org/ethereum/index-dtf/0x323c03c48660fe31186fa82c289b0766d331ce21/settings) show 1% and 10% across all three governance areas. Our [review of nine proposals](https://docs.google.com/spreadsheets/d/1jiTTQCofO8_moxI2P0cMDl6CrRb_wGg_O3o6TNMny9k/edit?gid=0#gid=0) found that all six proposals meeting today’s quorum would also have met 15%. However, the Jan 20, 2026 voting-period proposal reached only 15.9%, so lower turnout could stall future decisions. The higher proposal threshold would require smaller holders to gather delegations or find a proposer with enough voting power. These changes raise the requirements for an attack, but someone meeting the new threshold could still submit repeated proposals. Taylor’s [separate spam-protection upgrade](https://forum.reserve.org/t/rfc-proposal-spam-protection-upgrade-for-open/1666) addresses that problem. Please share suggestions, objections, and alternative thresholds during the five-day discussion ending **Oct 23, 2026**. We plan to incorporate that feedback and submit the onchain implementation proposal that day. ---
**Author:** ![0xJMG](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.reserve.org/0xjmg/32/1104_2.png) [@0xJMG](https://forum.reserve.org/u/0xJMG)\ **Post date:** [October 21, 2026, 6:55pm UTC](https://forum.reserve.org/t/rfc-raise-open-s-proposal-threshold-and-quorum/1668/2 "2026-10-21T18:55:16Z")
An update changing the recommendation to 4% proposal threshold: > [@\[RFC\] Proposal-spam protection upgrade for OPEN](https://forum.reserve.org/t/rfc-proposal-spam-protection-upgrade-for-open/1666/4): > > 1. I suggest Basket, DTF and DAO governance to share a **2-day voting delay, 5-day voting period and 3-day execution delay** , with a **4% proposal threshold and 15% quorum**. The 2/5/3 schedule is easy to explain. I previously suggested 5%, but our [Oct 21 snapshot tab #4](https://docs.google.com/spreadsheets/d/1jiTTQCofO8_moxI2P0cMDl6CrRb_wGg_O3o6TNMny9k/edit?gid=1847291032#gid=1847291032) shows nine wallets currently control at least 4% of votes, versus five at 5%. The new 12-hour averaging rule would still apply. Can the final contracts use these settings? ---
**Author:** ![0xJMG](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.reserve.org/0xjmg/32/1104_2.png) [@0xJMG](https://forum.reserve.org/u/0xJMG)\ **Post date:** [October 24, 2026, 8:40pm UTC](https://forum.reserve.org/t/rfc-raise-open-s-proposal-threshold-and-quorum/1668/3 "2026-10-24T20:40:48Z")
This proposal in three parts has moved onchain. 1. Basket Settings → Raise proposal threshold from 1% to 4% and quorum from 10% to 15%. Governs assets, weights, and rebalancing. 2. DTF Settings → Raise proposal threshold from 1% to 4% and quorum from 10% to 15%. Governs fees, distributions, auctions, roles, and technical configuration. 3. DAO Settings → Raise proposal threshold from 1% to 4% and quorum from 10% to 15%. Governs voting, revenue tokens, and DAO roles. Voting starts in 48hrs on Monday at 1:30pm PT. These proposals cover only the proposal and quorum thresholds meant to disincentivize recent uptick in malicious proposals. Separately there is an exploratory conversation on spam protection along with a new rewards vaults in this RFC: [[RFC] Proposal-spam protection upgrade for OPEN - #2 by 0xJMG](https://forum.reserve.org/t/rfc-proposal-spam-protection-upgrade-for-open/1666/2) This will be brought onchain separately as soon as a few more questions get clarified. Thx to all vlSQUILL that are contributing ideas, concerns and votes.