I am a bit worried about spam prevention for proposals in this DAO.
From the approved AGP text:
configured so that only ANT holders can vote and create votes,
The part about ‘only ANT holders can create votes’ seems scary IMO as you could purchase 10^-18 ANT (which technically makes an account an ANT holder) and spam the DAO with an infinite amount proposals to withdraw all the funding from the DAO. There are very high chances that one of such proposals would pass because no one would be motivated to vote no, specially since there is a tragedy of the commons scenario to vote no (no direct upside), and the attacker potentially can get all the funds in the DAO if one of the proposals isn’t rejected.
I propose adding a spam prevention mechanism by requiring to burn
x ANT in order to create a proposal in the Bounty DAO. This amount of ANT could be small, just to justify the cost to all ANT holders for their attention to vote no on bad proposals.
Wrote the code for it in 10 minutes using ANT’s
approveAndCall, so only 1 transaction is needed. The calldata of the
newVote function would need to be sent in the ANT
approveAndCall transaction. The permissions in the DAO would be set so only the
BurnToPropose contract can create new votes.
If we already had Triggers this could have been done using the UI directly