Content pfp
Content
@
0 reply
0 recast
0 reaction

Elad pfp
Elad
@el4d
Nouns Governor design challenge We found a bad attack vector, and don't love any of the mitigations. Please read and help us be smarter! (rounds.wtf starts tomorrow morning) https://mirror.xyz/verbsteam.eth/gnTdSqqiZC7OmqL8Dix-hEek5Sim1abC1BsZNm9_h-s
4 replies
14 recasts
39 reactions

1𝐴35𝐸1 pfp
1𝐴35𝐸1
@1a35e1
At a glance, creating off-chain proofs seems like the best approach to me. As the protocol grows, calculation voting power will only grow in complexity. Improving the governor to work with various strategies. i.e - 1 NOUN = 1 VOTE - 500,000 $NOUNS = 0.5 VOTE/s - ve/stNOUNS = ?? VOTES/s Would be cool.
0 reply
0 recast
0 reaction

w-g pfp
w-g
@w-g
another q is whether to reframe the problem to include proposal spamming, which currently *is* exacerbated by permissionless swapping. I suppose depends whether part of the intended purpose of constraining a noun’s proposal rate is to constrain the owner’s proposal rate, or just to limit total simultaneous props
1 reply
0 recast
1 reaction

wiz pfp
wiz
@wiz
hard one. how important is preserving stale delegations (after a noun has been transferred)? same attack vector exists with nouns on nft exchanges right?
2 replies
0 recast
0 reaction