Track your crypto coins now - https://t.co/S9Ea9O4Uw2
Analyze your token portfolio across all major blockchains with AI-powered risk analysis.
Discover profit opportunities, paperhanded coins, and get AI trading insights.
Our algorithm scans every token you sold and calculates what it would be worth at its all-time high.
Ethereum is for shipping.
Here are 25 things the Ethereum ecosystem launched, upgraded, and announced over the past month.
0/ @thedaofund Ethereum Security Quadratic Funding Round with @Giveth wrapped. The fund supported 134 security projects and had 3,934 unique donors.
1/ @Ronin_Network, one of the largest gaming blockchains, completed its migration to an Ethereum L2.
2/ Clear Signing went live. It is an open standard designed to help end blind signing and make transaction data human-readable before signing. Contributors include wallets and hardware, infrastructure, tooling, individual builders, and the Ethereum Foundation’s Trillion Dollar Security initiative, with the @ethereumfndn acting as a neutral steward.
3/ @SEAL_911 and @Wonderland_Fi introduced DARC, a Digital Asset Risk & Compliance standard for crypto teams, with continuous monitoring across GitHub, infrastructure, multisigs, DNS, and more.
4/ @arbitrum announced that LG Electronics' blockchain team is piloting an onchain advertising network on Arbitrum.
5/ @base activated Azul, its first standalone network upgrade, introducing multiproofs, new execution and consensus clients, CLZ opcode support, Osaka repricings, and performance upgrades up to 5,000 TPS.
6/ @Mastercard expanded stablecoin settlement support to include USDC, PYUSD, USDG, USDP, and SoFiUSD on Ethereum mainnet, @arbitrum, and @base.
7/ @EFDevcon 8 Mumbai early bird tickets went live. Tickets were available paid in ETH.
8/ Türkiye's Directorate of Communications (@Communications) registered cbiletisim.eth, making its first step in establishing an official onchain identity with @ensdomains.
9/ @CashApp launched stablecoin support, allowing nearly 60 million users to send and receive USDC with no wallet setup required, live on Ethereum mainnet and @Arbitrum.
10/ @torproject and @FundingCommons launched a web3-native crowdfunding initiative supporting 10 internet freedom projects.
11/ @JPMorgan launched a second tokenized money market fund on Ethereum.
11/ @lifiprotocol launched LIFI Intents, a full-stack intent execution engine built on the Open Intents Framework, an initiative for standardizing crosschain intents.
12/ @l2beat launched Token Frameworks, a dedicated place to explore interoperability solutions, token movement, volume, speed, chains, and framework adoption.
13/ @PrivacyEthereum launched a private transfers dashboard comparing 11 protocols across privacy, cost, UX, decentralization, compliance, verifiability, state, and composability.
14/ @Veildotcash launched Veil MCP 0.2.0, enabling agents to make private x402 payments on @base.
15/ @src_co_ introduced SLOW, reversible, self-custodial crypto payments on Ethereum.
16/ @ensdomains ecosystem builders launched ENS8004, a web app that converts an ENS name into an onchain AI agent other applications can find and verify.
17/ @OctantApp introduced properQF in Epoch 12, integrating quadratic funding into the funding round.
18/ @AragonProject launched onchain profiles, making governance participants readable across forums by resolving ENS names, avatars, bios, websites, and social links from Ethereum mainnet.
19/ The Ethereum Community Hub network expanded to Lisbon, hosted at the @gnosisDAO office.
20/ @SuccinctLabs introduced data confidentiality to OP Succinct, enabling institutions to keep transactions confidential while settling to Ethereum.
21/ @HardhatHQ 3 became stable, bringing Solidity tests, multichain support, a Rust-powered runtime, a revamped build system, and Hardhat Ignition for deployments.
22/ The inaugural @ethconf, in NYC, brought together thousands of founders, industry leaders, and builders to discuss building on top of Ethereum.
23/ @EthPrague brought Ethereum builders together in Prague to discuss protocol development, privacy, culture, and long- term societal impact.
24/ @ETHGlobal introduced a new format where, for the first time at an ETHGlobal hackathon, projects do not have to begin from zero.
Now, the quantum resistance roadmap.
Today, four things in Ethereum are quantum-vulnerable:
* consensus-layer BLS signatures
* data availability (KZG commitments+proofs)
* EOA signatures (ECDSA)
* Application-layer ZK proofs (KZG or groth16)
We can tackle these step by step:
## Consensus-layer signatures
Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation.
Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation.
One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are:
* Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in
* Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower)
* BLAKE3 or similar (take the most efficient conventional hash we know)
## Data availability
Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems:
1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world.
2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection.
Summary: it's manageable, but there's a lot of engineering work to do.
## EOA signatures
Here, the answer is clear: we add native AA (see https://t.co/YD9nIpsxcC ), so that we get first-class accounts that can use any signature algorithm.
However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify.
We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify.
We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower.
The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero.
## Proofs
Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs.
The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is.
In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block).
This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct.
Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this:
https://t.co/rAUSJjW7WL
https://t.co/EtXpkaDll5
State-level stablecoin oversight matters more than people realize. If Treasury cuts states out of GENIUS Act supervision, we lose regulatory diversity that could actually protect innovation. Lummis is right to push back. #Stablecoins
Who's watching this closely?
finally made an actual meal tonight instead of staring at charts 😭 pasta from scratch and everything. charts will still be red or green tomorrow, the garlic bread needed me NOW
Announcing AI dreams is easy. Building them with $50B on the line? That's a different beast entirely. Bitcoin miners are learning that execution separates visionaries from storytellers. The market is watching closely now. 👀
#Bitcoin Thoughts?
Every day in crypto feels like watching a new civilization being built in real time. The chaos, the breakthroughs, the drama — it's all part of something bigger than we realize.
#crypto Thoughts?
I’ve been in crypto for 9 years.
I’ve survived multiple bull and bear markets.
When the dust settles, the wealth will flow to those who stayed when it was hard & boring.
We're still early.
Being this early is painful. But it pays.
ETH in 2021: $1,700
ETH in 2022: $1,700
ETH in 2023: $1,700
ETH in 2024: $1,700
ETH in 2025: $1,700
ETH in 2026: $1,700
ETH before BitMine buying: $1,700
ETH after BitMine buying: $1,700
ETH before ETF approval: $1,700
ETH after ETF approval: $1,700
ETH during anti-crypto President: $1,700
ETH during pro-crypto President: $1,700
ETH before US-Iran war: $1,700
ETH after US-Iran war: $1,700
Performance of $ETH is an absolute joke.
Clarity Act is moving but there's a sneaky provision that could kneecap the actual builders. Kinda wild to claim crypto leadership while threatening devs. Fix it or the whole thing falls apart. #CryptoPolicy
Who's actually reading the fine print here?
The best way to build an L2 is to lean into the L1's offerings (security, censorship resistance, proofs, data avail...) more, and reduce your logic to just being a sequencer and a prover (if based, just a prover) over the core execution.
This is the combination of trust minimization and efficiency that the 2010s enterprise blockchain crew wanted, but was never able to achieve. Now, with Ethereum L2s, you can achieve it. And we've already seen successful examples of the L1's features protecting users' rights if something on the L2 goes wrong.
Tom Lee is getting absolutely laughed at for his bet on Ethereum.
Good.
Thinking 10 years ahead isn’t always appreciated.
History is full of business titans who were laughed at for seeing the future too early:
Elon Musk: “Electric cars are weak & lame."
Jeff Bezos: “Selling books… online? Stocks down 99%”
Jensen Huang: “GPUs are just for video games.”
Steve Jobs: “Touchscreen? App marketplace? Smart?”
Jack Dorsey: “A 140-character social network? Who would use it?”
These visionaries weren't crazy.
They were just early.
Ethereum is a nascent industry exploding with growth.
Don’t be so quick to bet against technology.
Don't be so quick to count crypto out.