DAOUSDT
DAO Maker / Tether USD
crypto Composite

I wanted to share something interesting that happened recently. Etherscan added an info note to the [Unicorn Meat token page](https://etherscan.io/token/0xed6ac8de7c7ca7e3a22952e09c2a2a1232ddef9a) that reads:
>"This token was created by Avsa of the Ethereum Foundation. Read more about it in this post."
The link goes to a [tweet from the official @ethereum account](https://x.com/ethereum/status/715821110722433024) from April 1, 2016 announcing "the Unicorn Meat Grinder Smart Contract and Bribable DAO" by @avsa.
For those who don't know the backstory: Alex Van de Sande (avsa) was one of Ethereum's earliest core team members. He built the Mist Browser, the Ethereum Wallet, and co-created ENS. In early 2016 he deployed a set of contracts as part of the ethereum.org tutorials, including the Unicorns token and the Unicorn Meat Grinder, a DAO that let you convert Unicorns into Unicorn Meat through on-chain governance.
The contracts were deployed from his same wallet that deployed the Foundation Tip Jar, which Alex made on behalf of the Foundation to raise money and donors received Unicorn tokens. So the provenance chain is: same deployer address, multiple Etherscan-labeled EF contracts, and now an official Etherscan note confirming the connection.
What makes this historically interesting:
* **The Meat Grinder was one of the first DAOs on Ethereum**, predating The DAO by months. It used a proposal and voting system where token holders could vote on actions like grinding Unicorns into Meat.
* **It introduced one of the first token upgrade patterns.** The Unicorn-to-Meat conversion was essentially a token migration mechanism, something that became standard practice years later.
* **The contracts were based on the ethereum.org tutorials** that avsa wrote to teach developers how to build on Ethereum. These tutorials were how an entire generation of Solidity developers learned the language.
We've been working on documenting and verifying the source code of these contracts on [EthereumHistory](https://ethereumhistory.com), including cracking the bytecode of contracts that were never verified on Etherscan. We recently launched a [Collections feature](https://ethereumhistory.com/collections) that groups all contracts by their deployer, starting with avsa's 60 contracts and Vitalik's 66 contracts.
**We also recently cracked and verified the Meat Grinder's source code on Etherscan.** The source had been sitting in [avsa's public GitHub gist](https://gist.github.com/alexvandesande/3abc9f741471e08a6356) for 10 years but was never formally verified on-chain. The challenge was figuring out the exact compiler settings: these contracts predate Solidity 0.4, so there's no metadata hash in the bytecode to help identify the version. We had to work through early solc releases until we found that solc 0.2.1 with default optimization produced an exact byte-for-byte match against the on-chain runtime bytecode. Once confirmed, we submitted it to both [Sourcify](https://sourcify.dev) and [Etherscan](https://etherscan.io/address/0xc7e9dDd5358e08417b1C88ed6f1a73149BEeaa32#code), so anyone can now read the original Solidity source directly on Etherscan and verify it themselves.
It's a small thing, but these early contracts are historical artifacts. Having their source verified on-chain means the code is permanently readable and auditable, not just sitting in a gist that could disappear.
If anyone is interested in Ethereum's early contract history, the [provenance page](https://unicornmeateth.com/provenance) has the full chain of evidence laid out, and [EthereumHistory](https://ethereumhistory.com) is an open platform where anyone can help document contracts.

It’s hack szn and Litecoin is the latest to be targeted after Aave and a number of DeFi protocols got hit
\> Zero-day discovered in the MWEB privacy layer
\> Coordinated DoS on major mining pools
\> Attacker used the window to push invalid peg-outs from MWEB
MWEB = MimbleWimble Extension Blocks. It’s Litecoin’s optional privacy layer, activated via soft fork in May 2022, that lets users do confidential transactions
DoS = Denial of Service (common brute force hack)
Bridges / swap protocols that optimized for speed over block finality may have had double spends while bridges/protocols that waited for more confs are unaffected
Near Intents may have about $600k in exposure and THORChain may have had 1-2 swaps effected
Overall, this is the only known publicly reported $ exposure thusfar. There could be more after audits are conducted on potential trouble spends
DeFi protocols have lost over $750 million to exploits in 2026 through mid-April, including the $292 million Kelp DAO bridge drain on April 19 and a $285 million attack on Solana-based perpetuals platform Drift on April 1
This is all a reminder to stay SAFU in a time of unprecedented software attacks

The main things I can think of that would hinder Solana's market share growth are:
A killer app from a competitor, especially in gaming, that would drain usage elsewhere.
A failure to adapt to governments compliance rules for RWA trading.
ETH chain abstraction landscape quickly becoming unified and performant, making the usage of ETH ecosystem feel like a unified fast-enough network, competing with SOL's high-speed atomic transactions.
For safety, I am quite confident that the core team and security auditors are keeping the core protocol safe, but it would be very bad to have more security breaches affecting major actors/elements on Solana's network, like Jupiter, Ondo, Jito, Realms... What happened to Aave (and Kelp DAO) was bad enough.
For Q-Day, the computational cost of generating the ZK-proof of a quantum resistant signature on a cell phone could be a problem for mobile usage. You don't want your phone to become a toaster while gaming or whatever needs a lot of transactions. But the devs will probably find a solution. Probably not a deal breaker anyway. But who know?

The paranoia is justified. Three LST platforms controlling most of staked ETH is a systemic risk that nobody wants to talk about because everyone's earning yield from it. If one of those platforms gets exploited (Kelp DAO just showed how this goes), the contagion hits every protocol that accepts that LST as collateral. It's concentration risk dressed up as decentralization.

I wanted to share something interesting that happened recently. Etherscan added an info note to the [Unicorn Meat token page](https://etherscan.io/token/0xed6ac8de7c7ca7e3a22952e09c2a2a1232ddef9a) that reads:
>"This token was created by Avsa of the Ethereum Foundation. Read more about it in this post."
The link goes to a [tweet from the official @ethereum account](https://x.com/ethereum/status/715821110722433024) from April 1, 2016 announcing "the Unicorn Meat Grinder Smart Contract and Bribable DAO" by @avsa.
For those who don't know the backstory: Alex Van de Sande (avsa) was one of Ethereum's earliest core team members. He built the Mist Browser, the Ethereum Wallet, and co-created ENS. In early 2016 he deployed a set of contracts as part of the ethereum.org tutorials, including the Unicorns token and the Unicorn Meat Grinder, a DAO that let you convert Unicorns into Unicorn Meat through on-chain governance.
The contracts were deployed from his same wallet that deployed the Foundation Tip Jar, which Alex made on behalf of the Foundation to raise money and donors received Unicorn tokens. So the provenance chain is: same deployer address, multiple Etherscan-labeled EF contracts, and now an official Etherscan note confirming the connection.
What makes this historically interesting:
* **The Meat Grinder was one of the first DAOs on Ethereum**, predating The DAO by months. It used a proposal and voting system where token holders could vote on actions like grinding Unicorns into Meat.
* **It introduced one of the first token upgrade patterns.** The Unicorn-to-Meat conversion was essentially a token migration mechanism, something that became standard practice years later.
* **The contracts were based on the ethereum.org tutorials** that avsa wrote to teach developers how to build on Ethereum. These tutorials were how an entire generation of Solidity developers learned the language.
We've been working on documenting and verifying the source code of these contracts on [EthereumHistory](https://ethereumhistory.com), including cracking the bytecode of contracts that were never verified on Etherscan. We recently launched a [Collections feature](https://ethereumhistory.com/collections) that groups all contracts by their deployer, starting with avsa's 60 contracts and Vitalik's 66 contracts.
**We also recently cracked and verified the Meat Grinder's source code on Etherscan.** The source had been sitting in [avsa's public GitHub gist](https://gist.github.com/alexvandesande/3abc9f741471e08a6356) for 10 years but was never formally verified on-chain. The challenge was figuring out the exact compiler settings: these contracts predate Solidity 0.4, so there's no metadata hash in the bytecode to help identify the version. We had to work through early solc releases until we found that solc 0.2.1 with default optimization produced an exact byte-for-byte match against the on-chain runtime bytecode. Once confirmed, we submitted it to both [Sourcify](https://sourcify.dev) and [Etherscan](https://etherscan.io/address/0xc7e9dDd5358e08417b1C88ed6f1a73149BEeaa32#code), so anyone can now read the original Solidity source directly on Etherscan and verify it themselves.
It's a small thing, but these early contracts are historical artifacts. Having their source verified on-chain means the code is permanently readable and auditable, not just sitting in a gist that could disappear.
If anyone is interested in Ethereum's early contract history, the [provenance page](https://unicornmeateth.com/provenance) has the full chain of evidence laid out, and [EthereumHistory](https://ethereumhistory.com) is an open platform where anyone can help document contracts.

It’s hack szn and Litecoin is the latest to be targeted after Aave and a number of DeFi protocols got hit
\> Zero-day discovered in the MWEB privacy layer
\> Coordinated DoS on major mining pools
\> Attacker used the window to push invalid peg-outs from MWEB
MWEB = MimbleWimble Extension Blocks. It’s Litecoin’s optional privacy layer, activated via soft fork in May 2022, that lets users do confidential transactions
DoS = Denial of Service (common brute force hack)
Bridges / swap protocols that optimized for speed over block finality may have had double spends while bridges/protocols that waited for more confs are unaffected
Near Intents may have about $600k in exposure and THORChain may have had 1-2 swaps effected
Overall, this is the only known publicly reported $ exposure thusfar. There could be more after audits are conducted on potential trouble spends
DeFi protocols have lost over $750 million to exploits in 2026 through mid-April, including the $292 million Kelp DAO bridge drain on April 19 and a $285 million attack on Solana-based perpetuals platform Drift on April 1
This is all a reminder to stay SAFU in a time of unprecedented software attacks

The main things I can think of that would hinder Solana's market share growth are:
A killer app from a competitor, especially in gaming, that would drain usage elsewhere.
A failure to adapt to governments compliance rules for RWA trading.
ETH chain abstraction landscape quickly becoming unified and performant, making the usage of ETH ecosystem feel like a unified fast-enough network, competing with SOL's high-speed atomic transactions.
For safety, I am quite confident that the core team and security auditors are keeping the core protocol safe, but it would be very bad to have more security breaches affecting major actors/elements on Solana's network, like Jupiter, Ondo, Jito, Realms... What happened to Aave (and Kelp DAO) was bad enough.
For Q-Day, the computational cost of generating the ZK-proof of a quantum resistant signature on a cell phone could be a problem for mobile usage. You don't want your phone to become a toaster while gaming or whatever needs a lot of transactions. But the devs will probably find a solution. Probably not a deal breaker anyway. But who know?

The paranoia is justified. Three LST platforms controlling most of staked ETH is a systemic risk that nobody wants to talk about because everyone's earning yield from it. If one of those platforms gets exploited (Kelp DAO just showed how this goes), the contagion hits every protocol that accepts that LST as collateral. It's concentration risk dressed up as decentralization.

I don’t believe DAO was a hack when it happened. It was an exploit of a flaw in how smart contracts work, but it was simply executing the contract as it was written.
I also don’t think rolling it back was the right solution specifically for the reason you said: it proves that the ledger isn’t immutable.
It sucks that all those funds should have been stolen forever, but that’s what an immutable and uncensorable ledger is. The initial problem was in the design of the contract that got exploited.

liquidity lock and renounced ownership stopped being meaningful signals maybe 18 months ago once people figured out how to write withdraw functions into the liquidity contract before locking it. what i actually look at now is whether the deployer wallet has any on-chain history before this project fresh wallets with zero prior activity and a shiny new token are the tell. second thing is token distribution: if 3 wallets hold 40%+ and theyre not labeled team/DAO with a vesting cliff, assume its a coordinated dump waiting to happen. none of this is foolproof but it filters out the lazier rugs

JUST IN: Aave DAO Contributes 25,000 ETH To DeFi United

The sybil problem is unsolvable without identity, and identity is the one thing crypto was designed to avoid. Every DAO governance system either accepts plutocracy (token-weighted) or requires KYC (kills the point). There's no middle ground that actually works at scale.

The Sun vs WLFI case is going to set precedent for every DAO governance dispute going forward. If a protocol can freeze your tokens and strip voting rights without on-chain consensus, the "governance" is just branding over admin keys. This is the Kelp DAO debate all over again but with political actors instead of hackers.

just a few voters can change everything in a DAO

Nouns DAO ends daily auctions after 10 voters force change

It feels like the entire DeFi industry is moving as one coordinated DAO right now. Albeit, not a very good one
IMO, freezing assets is a very slippery slope. My take is that security and asset protection should be at the app level and NOT the protocol level
Once protocols and blockchains start changing block production, the “immutability” of crypto deteriorates. We are only as strong as our weakest link.
Do you agree with tether freezing these assets or do you think this is a huge misstep for crypto ideals?