memoscan

0x5efd…a1ce

All memos sent from and to 0x5efd…a1ce.
0x66666665…d513sent to0x5efda50f…a1ce·#25,796,615·0xc1027c0b…19fbc1
{"title":"Proposal #68: Migrated proposal data fetching from RPC to The Graph.","description":"Expenditure: 200 TORN\n\nReason: Currently, Most RPC retrieval methods have a block count limit, typically a maximum of 10,000 blocks. However, the block number from our first proposal to the latest block number has exceeded 10 million blocks. Therefore, switching to a Graph-based retrieval method solves the RPC problem once and for all.\n\nUpdate Details:\n\n1. Deployed Proposal Subgraph: https://thegraph.com/explorer/subgraphs/2Z6mFMqDdwHSvbMLS3Zy3egmrEwHXLxHaDgeAHt9NrnG\nSubgraph Source Code: https://github.com/tornado-dao/tornado-governance-subgraph\n\n2. Add a tornado[.]cash phishing website notice board.\n\n3. Migrated code from Codeberg to GitHub (Codeberg announced that it no longer permits hosting cryptocurrency projects).\n\n4. Updated the UI to fetch proposals via The Graph instead of RPC; voting comments are now also fetched via The Graph.\n\nTarget: Update the IPFS hash for the Tornado Cash classic UI associated with the ENS domain tornadocash.eth.\n \nUI Code Repository: https://github.com/tornado-dao/classic-ui/commits/development/\n \nUI Code commit: https://github.com/tornado-dao/classic-ui/commit/17c54dae9ad91bb3c6d62a7860df6cd365ab76d4\n \nIPFS Hash: bafybeigduniojgqrz7e4vntsgmovdli3oi7a2pnzzvz2gfxlvj3yqwk75a\n\nIPFS Hash Verification Tool: https://github.com/tornado-dao/tornado-ipfs-ui\n \nContent Hash: e30101701220c3a350e49a11cfc9cab672331d51ad1b723e0d3db9cd73a316ebaa7788595fe8 (calculated using the tool at https://github.com/tornado-dao/tornado-ipfs-ui/blob/main/ContentHash.html )\n \nAffected DomainsThe updated IPFS hash will affect the following domains:\n\ntornadocash.eth.limo\ntornadocash.eth.link\nipfs.io/ipns/tornadocash.eth\ntornadocash-eth.ipns.dweb.link"}
0xd4eca8c9…a925sent to0x5efda50f…a1ce·#25,392,193·0x350da85a…e42d40
{"title":"Tornado Cash Governance Proposal: Establishing 0.5% Fee Standard and 90% Dynamic Deflationary Burn Plan","description":"Summary\nThis proposal aims to transition the Relayer Registry to the V5 Strategy A architecture, officially abolishing the legacy fee structures to establish a brand-new dynamic deflationary economic model.\n\nThe core parameters of the upgrade are: unifying and adjusting the Relayer service fee rate to 0.5%. Within the withheld tokens from this fee base, a structured reallocation mechanism is introduced—90% of the tokens will be direct-routed to the burn pool for permanent destruction (Burn), while the remaining 10% will continue to be distributed as staking rewards to governance stakers (achieving a 90/10 wealth redistribution under the 0.5% fee standard). Concurrently, this proposal requests 50 TORN from the treasury to reimburse the proposer’s upfront gas expenses paid during mainnet contract deployment.\n\nWithout introducing any risk to existing staked assets, this upgrade reshapes TORN’s deflationary tokenomics, enhances market scarcity, and fosters a long-term positive feedback loop for all ecosystem participants (stakers, relayers, and token holders).\n\n🔍 Core Arguments\n1️⃣ Zero-Loss & Win-Win: Revamping Fee Rules to 0.5% and Spurring Token Price Appreciation via the Precise \"90/10\" Deflationary Model\nNewly Established 0.5% Fee Standard: This upgrade completely re-engineers the relayer ecosystem by standardizing the service fee to exactly 0.5%. This parameter regulates market order while securing sustainable, predictable volume streams for both the treasury and the burn pool.\n\nPrecise Deflationary Vector (90% Burn)：By permanently destroying 90% of the accumulated fees, a high-intensity, rigid on-chain deflationary narrative is embedded into TORN. The continuous contraction of circulating market supply directly drives the fundamental valuation of the remaining asset base.\n\nPreserving 10% Staking Incentive: We have meticulously retained a 10% allocation of the collected fees as staking incentives. Powered by the multiplier effect of token price appreciation, the "}
0x914d73e3…b20esent to0x5efda50f…a1ce·#24,955,293·0x1ea572d9…0cdf3d
{"title":"Proposal #66: Update the ETH RPC List and ENS - 50 TORN","description":"Expenditure: 50 TORN\n\nReason: The current default Blockscout RPC is unusable because it enforces a strict JSON-RPC mode.\n\nThe feeOracleV4 and feeOracleV5 calls in tornado-oracles do not include the latest block parameters, causing compatibility issues with strictly compatible RPC endpoints.\n\nThe most practical and straightforward solution is to update the ETH RPC list to resolve this incompatibility issue.\n\nUI Update Details:\n\nETH RPCs: pocket, Mevblocker, mevblockerFullprivacy, torndaoRPC, sentioRPC, lavaRPC, blastRPC, xrpc\n\nGoal: Update the IPFS hash of the Tornado Cash Classic UI associated with the ENS domain tornadocash.eth.\n\nUI Codebase: https://codeberg.org/torndao/classic-ui/commits/branch/development\n\nUI Code Commit: https://codeberg.org/torndao/classic-ui/commit/d52c01688f5697e60a1d3c598a4c30989403fb0f\n\nIPFS Hash: bafybeibr7xeb2sg6uiaeueh5lrw6vsoopkyti67wamiyimpo5gvrpua5by (Accessible via https://ipfs.io/ipfs/bafybeibr7xeb2sg6uiaeueh5lrw6vsoopkyti67wamiyimpo5gvrpua5by)\n\nIPFS Hash Verification Tool: https://codeberg.org/torndao/tornado-ipfs-ui\n\nContent Hash: e3010170122031fdc81d48dea2004a10fd5c6deac9ce7ab1347bf603118431eee9ab17d01d0e (Calculated using tools at https://codeberg.org/torndao/tornado-ipfs-ui/src/branch/main/ContentHash.html)\n\nAffected Domains: The updated IPFS hash will affect the following domains:\n\ntornadocash.eth.limo\n\ntornadocash.eth.link\n\nipfs.io/ipns/tornadocash.eth\n\ntornadocash-eth.ipns.dweb.link"}
0x05642422…6a6asent to0x5efda50f…a1ce·#24,404,731·0x843630a5…c31336
{"title":"Proposal #65: Update ETH RPC List and ENS","description":"Reason: The current ETH RPC List on the UI no longer support historical queries, necessitating an update to the default ETH RPC list.\n\nUI Update Details:\n\nETH RPCs: blockscoutRPC,blastRPC,xrpc, gasHawkRPC, lavaRPC,torndaoRPC,sentioRPC,tornadoRPC\n\nTarget: Update the IPFS hash for the Tornado Cash classic UI associated with the ENS domain tornadocash.eth.\n \nUI Code Repository: https://codeberg.org/torndao/classic-ui/commits/branch/development\n \nUI Code commit: https://codeberg.org/torndao/classic-ui/commit/d52c01688f5697e60a1d3c598a4c30989403fb0f\n \nIPFS Hash: bafybeie5hxovqc4ifcnrnhvmjbefxgeix6oqvzaspyytdxiyscji22v5pu (accessible via https://ipfs.io/ipfs/bafybeie5hxovqc4ifcnrnhvmjbefxgeix6oqvzaspyytdxiyscji22v5pu)\n \nIPFS Hash Verification Tool: https://codeberg.org/torndao/tornado-ipfs-ui\n \nContent Hash: e301017012209d3ddd580b88289b169eac48485b9888bf9d0ae4127e3131dd1890928d6abd7d (calculated using the tool at https://codeberg.org/torndao/tornado-ipfs-ui/src/branch/main/ContentHash.html)\n \nAffected DomainsThe updated IPFS hash will affect the following domains:\ntornadocash.eth.limo\ntornadocash.eth.link\nipfs.io/ipns/tornadocash.eth\ntornadocash-eth.ipns.dweb.link"}
0xae437331…6327sent to0x5efda50f…a1ce·#23,547,783·0xd93ee0bc…7d6fda
{"title":"Deploy Tornado Cash on the Solana blockchain(without any code modifications, only to gauge the community’s attitude toward the extension)","description":"https://t.me/TornadoCashOfficialDAO/14367\nhttps://etherscan.io/address/0xc36ef9b313a50e6f56e571ab9f902643efadc119#code\n\nProposal 64 (without any code modifications, only to gauge the community’s attitude toward the extension)\n - Partnership Details \n\n - Partner: voidify (has been successfully operating since January without any rug-pull incidents or issues) \n\n - Objective: Deploy Tornado Cash on the Solana blockchain \n\n - Contributions \n * V1 Version (If Proposal 64 passes, the scope of code modifications in Proposal 65)\n * Modify Tornado Cash Solidity code and re-implement contracts in Rust for Solana \n * Add a “SOL” option on the Tornado Cash UI page, and ensure the interface is compatible with Solana contracts (the current frontend is not compatible with Solana wallet plugins, therefore an additional subpage will be used) \n * Use a self-developed Node.js Indexer as the subgraph equivalent \n * Do not modify any EVM-related code, only add SVM-related code \n\n * Since August, @tornadosto(https://t.me/tornadosto) and the void team have been working for two months to modify and redesign the original void frontend code for integration into the Tornado Cash UI \n\n * Increase the visibility and relevance of TORN during the current wave of privacy interest, showcasing that Tornado Cash remains active. Voidify also has a large promotional team\n\n * To gain experience in Tornado Cash’s non-EVM chain expansion and in reclaiming fees on the BSC chain\n\n- Specific Details \nDue to the character limit, please refer to the DAO group information and the Etherscan code comments mentioned at the beginning for more details\n"}
0x05642422…6a6asent to0x5efda50f…a1ce·#23,011,580·0x7cf64043…169fe1
{"title":"Proposal #63: Update ETH RPC List and ENS","description":"Reason: The current ETH RPC List on the UI no longer support historical queries, necessitating an update to the default ETH RPC list.\n\nUI Update Details:\n\nETH RPCs: flashbotRPC, tornadoRPC, blockscoutRPC, kyberRPC, gasHawkRPC, lavaRPC.\n\nTarget: Update the IPFS hash for the Tornado Cash classic UI associated with the ENS domain tornadocash.eth.\n\nUI Code Repository: https://codeberg.org/torndao/classic-ui/commits/branch/development\n\nUI Code commit: https://codeberg.org/torndao/classic-ui/commit/30c4b44a5cd96811e17ef46d921ea8e1841a05d0\n\nIPFS Hash: bafybeiadcezfjx4ewel2xbdic66a4oj5ei6wtrvcbnirao5543cqtckukm (accessible via https://ipfs.io/ipfs/bafybeiadcezfjx4ewel2xbdic66a4oj5ei6wtrvcbnirao5543cqtckukm)\n\nIPFS Hash Verification Tool: https://codeberg.org/torndao/tornado-ipfs-ui\n\nContent Hash: e3010170122003113254df84b117ab846817bc0e393d223d69c6a20b51103bbde6c509895453 (calculated using the tool at https://codeberg.org/torndao/tornado-ipfs-ui/src/branch/main/ContentHash.html)\n\nAffected DomainsThe updated IPFS hash will affect the following domains:\ntornadocash.eth.limo\ntornadocash.eth.link\nipfs.io/ipns/tornadocash.eth\ntornadocash-eth.ipns.dweb.link\n"}
1-50 of 287