The current workflow for executable proposals is Draft → Snapshot Vote → Onchain Vote. This means that it takes 14 days (5 day snapshot vote + 7 day onchain vote + 2 day timelock) for an executable proposal to pass, and requires two votes from delegates.
The nominal reason for this is that we don’t want delegates to have to waste ETH on gas fees for proposals that are sure to fail; preflighting via snapshot ensures this doesn’t happen. Doing it this way extends the whole process, however, and instead requires more work from delegates by making them vote twice.
I’d like to propose a change: Executable votes can go straight from Draft to an onchain vote, but the proposer must put up a deposit in ENS - say 100 ENS for the sake of argument - that is forfeit if the proposal fails. The deposit could be sent to the DAO wallet or burned.
This should strongly discourage submission of votes that are not likely to pass, while making the whole process faster and easier for everyone. Posting a deposit could even take the place of the current 100k vote requirement to be able to propose a vote.
If this was approved, we’d need to deploy a new governor contract to encode these rules, but the changes should be relatively straightforward.