Content pfp
Content
@
0 reply
0 recast
0 reaction

datadanne ↑ pfp
datadanne ↑
@datadanne.eth
I don't think this is a good solution since it makes delegation slow, but couldn't you work around the flaw by not allowing an NDT to vote until proposalUpdatablePeriodInBlocks + votingDelay + votingPeriod blocks has passed since it was minted? That way you can't swap -> mint -> vote for any prop that is created
3 replies
0 recast
3 reactions

Michael Gingras (lilfrog) pfp
Michael Gingras (lilfrog)
@frog
Couldn’t you still mint yourself x NDTs from the pool and let them mature and if nobody back runs you then you have x voting power for the price of 1? Feels like improvement but not 100% there. I think nulling NDTs on noun transfer would help but needs hooks on transfer right? Which isn’t possible?
1 reply
0 recast
1 reaction

datadanne ↑ pfp
datadanne ↑
@datadanne.eth
Yeah if you allow stale NDT-tokens to vote you could! But a key difference imo is that you can’t do that to impact an existing prop that is onchain. Burning NDR on noun transfers can’t be done w/o hooks, but you can invalidate them & not allow them to vote unless the noun has the same owner as when it was minted
1 reply
0 recast
2 reactions