Proposal 302 (Q1911)

From Nouns Dev
A Nouns proposal.
Language Label Description Also known as
English
Proposal 302
A Nouns proposal.

    Statements

    0 references
    Fund a code4rena audit for DAO V3
    0 references
    73
    0 references
    0
    0 references
    302
    0 references
    0 references
    0 references
    0 references
    0 references
    1 June 2023
    0 references
    1 June 2023
    0 references
    200,000
    0 references
    1
    0 references
    200,000
    0 references
    45.16
    0 references
    45.16
    0 references
    324
    0 references
    0 references
    The text is about funding a second audit for the upcoming DAO V3 upgrade proposal. The new features of the upgrade include a new minority protection mechanism, proposal editing, propose by signature, an objection-only period, and votes snapshot after voting delay. The first audit started on June 1st with Spearbit and is expected to end around June 20th.
    0 references
    The text does not provide the name of the team or builder proposing the proposal
    0 references
    1
    0 references
    0 references
    My thesis as a delegate is: “Nouns has a unique role in the ecosystem as a gathering place around public goods.” Securing Nouns while funding independent auditors for a public audit report is clearly a public good. Easy yes!
    0 references
    NounsDAO protocol upgrades should be audited.
    0 references
    no brainer. have used code4rena before and was happy with results. nice getting loads of new technical eyes on the project too. who knows, might even attract some new builders as well as ensuring free of vulns.
    0 references
    0 references
    lets gooooooo! *sent from voter.wtf*
    0 references
    **FOR - 40 VOTES** **DonJon** | *No brainer* **AGAINST - 0 VOTES** **ABSTAINS - 9 VOTES**
    0 references
    Voting For the audit of course but confused about this part: Objection-only Period: a conditional voting period that gets activated upon a last-minute proposal swing from defeated to successful, affording against voters more reaction time. Not sure why more time is being given for no votes but not last minute yes votes. But that doesnt impact the need for the audit.
    0 references
    Clearly we should get our contracts audited. One thing not mentioned in the prop, but I hope to see: sharing of the audit results.
    0 references
    Abstaining from this vote as I dont believe the Nouns Fork should be implemented. I appreciate and respect all of the work the team put into v3, and expect this audit prop to pass, but the fork mechanism is likely dangerous for the DAO.
    0 references
    Ok but it seems highly unfair to those who aren’t given a similar opportunity if they have a last minute defeat. It’s not that easy to just put the prop back up. Why not do it either way if there is a list minute flip? And what would be the parameters? (eg what is considered last minute?) --And I realize this will need to be a separate prop to enact but do think this part should be a completely different prop from the other features since it’s a significant change.
    The current design for last-minute voting changes was chosen because it was found to be the most reasonable after discussions with technical Nouners. Symmetrical time extensions could lead to griefing proposals, causing them to never end or take a very long time. The current design has a higher risk in a proposal that passes when it shouldn't have, but unsuccessful proposals can always be re-proposed. The change will be deployed turned off, and the DAO can turn it on by configuring it with non-zero params. The team is open to better designs if they are proposed.
    0 references
    Question <@378904401290592258> or <@701029092547493888> on this:--Objection-only Period: a conditional voting period that gets activated upon a last-minute proposal swing from defeated to successful, affording against voters more reaction time.--Why only if it goes defeated to successful? Why not the other way too?
    The Objection-only Period is activated only when a proposal swings from defeated to successful because there is a higher risk in a proposal that passes when it shouldn't have, as opposed to the other way around. You can always re-propose, but you cannot undo a successful proposal. A symmetrical design for For/Against was not found to be reasonable, as it could lead to griefing proposals to never end or take a very long time. The current design was chosen after careful consideration of alternatives with technical Nouners. However, they are open to better designs if any are proposed.
    0 references