Proposal 46 - fix proposals state and update docs

Proposals
1

Why we need it

  1. After proposal 41 (changing quorum threshold) old proposals state started showing incorrect on website. I think that it is website problem but no - it happened bcs old devs implemented governance proposalState function incorrect and it checks quorum before checking proposal execution status
  2. Docs have not updated after proposal 41 and 44 and users see deprecated info about relayer registration threshold and actual ipfs hashes

What i did

I changed state function and updated docs ipfs. Also i implemented very very comprehensive governance tests with auditor - these tests should be added in future to each proposal to be sure that proposal does not break governance

New docs: https://cloudflare-ipfs.com/ipfs/QmYjBe2bNTGQzgdqAi7hkdNJ9BBrAgf4e8teRWLa4oN6Y6

Proposal info
Update state function in governance contract and change ipfs contenthashes on docs.tornadocash.eth and docs.sources.tornadocash.eth

Proposal code: https://git.tornado.ws/ButterflyEffect/proposal-46/src/branch/main/contracts/Proposal.sol
New state function code: https://git.tornado.ws/ButterflyEffect/proposal-46/src/branch/main/contracts/v5-proposal-state-patch/GovernanceProposalStateUpgrade.sol
Proposal tests: https://git.tornado.ws/ButterflyEffect/proposal-46/src/branch/main/test/Proposal.js
Governance comprehesive tests: https://git.tornado.ws/ButterflyEffect/proposal-46/src/branch/main/test/Governance.js
Proposal contract: https://etherscan.io/address/0x142145916e1a5139890b8da275ca9a4443f3a137#code
Updated governance contract: https://etherscan.io/address/0xbf46f2222c0712caf2f13b8590732dbd964ce395#code

For transparency i as in last proposal placed ipfs hashes and conversion hash library right in proposal code and anyone can verify it just need to copy from contract code
Who want to test the site you can use cid which placed raw in proposal code

1 Like
2

who interested about airdrop proposal - i will propose two airdrops proposals in the middle of february
if first proposal will accepted second will be automatically rejected
if second accepted, first rejected

1 Like
3

Thanks for your hard work. Proposal 46 is necessary.
As for Airdrop I think it’s also right during this period.
Since the $TORN price has almost no more buyers and only increases by market.
We don’t need TornadoCash ads but we need more DAO and Staking participants to increase the TORN value.

4

What is the meaning of airdrop? If airdrops are added, the value of existing TORN will fall to the point of no return. I still recommend adding a burning mechanism. Of the tokens deducted from the relayer, 80% will be used for burning and 20% will be used for distribution. At the same time, attempts are made to charge mixers for their deposits, and the fees are distributed to pledgers. This is the way to go in the long run.

5

I think this is wrong. You’re putting in front of the fact that there will be an airdrop. Must first decide by voting whether the airdrop is needed by the community and whether the community is ready to take all the risks?

6

Yes, airdrops are pointless. I think it’s okay and should be considered from the perspective of how to operate in compliance with regulations, how to charge fees and how to empower tokens.