If you are already into Cosmos projects you already know how they are taking governance proposals seriously, there is already a terminology for it: DPS (Drama per second) because we like to discuss everything to its last details in Cosmos Ecosystem.
So Proposal 63 offers usage of Juno Commonwealth ( https://commonwealth.im/juno ) for all Juno proposals for a minimum of 3 days before being submitted for a vote on chain. Of course this doesn't stop people spamming governance with fake airdrops (watch out for airdrop proposals in deposit period, they just want to click the scam links in the description, don't fall for it).
There won't be any code update in this proposal, seem like just a signaling proposal to get on community. Here is the whole proposal
Most proposals go through Commonwealth for review and discussion before arriving on chain. This allows community members to engage with the proposers to understand and provide input and feedback before the proposal is submitted on chain. However, some proposals do not go through Commonwealth, which can lead to proposals arriving on chain that could have been discussed and improved before arriving on chain.
This proposal is to formalise the usage of Juno Commonwealth ( https://commonwealth.im/juno ) for all Juno proposals for a minimum of 3 days before being submitted for a vote on chain.
Software upgrade proposals do not need to follow this process.
This requirement should be enforced through the use of NoWithVeto.
- Vote YES to approve a three-day mandatory discussion period on commonwealth.
- Vote NO to reject a three-day mandatory discussion period on commonwealth.
- Vote ABSTAIN to express no interest in the matter.
Vote NOWITHVETO to cause depositors to lose their deposit.
