ProposalsProposal 361
Withdraw from the TokenBuyer/Payer contracts
Executed
For
202
Against
91
Abstain
1
Quorum: 123
Proposed by
0x8404...F128
ProposalsProposal 361
The treasury assets are currently held by the TokenBuyer/Payer contracts are not included in the forking calculation and in the upcoming Proposal 360 there is a ∼105 ETH refill for the TokenBuyer/Payer which might cause some disagreement just before a possible fork so I propose to withdraw from the 2 contracts.
The contracts will refill with the first USDC proposal after this one so it wont cause any issues.
Would like to see proposals include information that helps voters understand context, reasons, impact.
(noun40 voting via agora)
voting in favor for the same reason as the last TokenBuyer withdrawal prop (prop 347):
no need to frame this as petty imo. if an honest minority was forking they too would be engaging in similar behavior trying to divvy up every last dao controlled asset possible. I'm voting in favor b/c I don't think this hinders the dao's activity meaningfully (it might delay a prop builder from receiving USDC immediately if they ask for more than $200k; they will be registered a debt while the tokenbuyer contract executes the trade, but nothing more than that) and I don't think this is against the spirit of what the fork is meant to accomplish.
Against for the same reason as the last TokenBuyer withdrawal prop
sent from voter.wtf
https://tenor.com/bXDiV.gif
vote cast on safari mobile using Dawn Wallet
The treasury assets are currently held by the TokenBuyer/Payer contracts are not included in the forking calculation and in the upcoming Proposal 360 there is a ∼105 ETH refill for the TokenBuyer/Payer which might cause some disagreement just before a possible fork so I propose to withdraw from the 2 contracts.
The contracts will refill with the first USDC proposal after this one so it wont cause any issues.