Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Promotions
AI
Gate AI
Your all-in-one conversational AI partner
Gate AI Bot
Use Gate AI directly in your social App
GateClaw
Gate Blue Lobster, ready to go
Gate for AI Agent
AI infrastructure, Gate MCP, Skills, and CLI
Gate Skills Hub
10K+ Skills
From office tasks to trading, the all-in-one skill hub makes AI even more useful.
GateRouter
Smartly choose from 30+ AI models, with 0% extra fees
I noticed that Vitalik recently shared very important details about the future of the execution layer in Ethereum, and the topic is worth taking a moment to discuss.
The first development relates to the state tree. The idea here is to transition from the current Merkle Patricia structure to a more efficient binary tree structure, with the main improvement relying on the use of stronger hash functions like Blake3 or Poseidon series. This significantly reduces the length of Merkle branches, thereby lowering the bandwidth costs for verification. What I like about this approach is that they are studying its application through EIP-7864, not just a theoretical idea. Additionally, the plan includes unifying storage cells into pages, which reduces access costs for adjacent storage, while maintaining metadata bits to enable future state expiration features.
The second development is more bold: replacing the entire EVM. Vitalik points to the possibility of using a RISC-V architecture for the new virtual machine. The idea is that the new VM should improve execution efficiency and proof generation simultaneously, support creating ZK proofs on the client side, and simplify overall code execution. The application path is clear: first replace pre-defined contracts, then allow deploying the new virtual machine contracts, and finally achieve backward compatibility and a gradual transition from EVM.
What’s interesting is that these improvements are not random—each change is designed to solve a specific problem. Using an optimized hash function means better performance, restructuring the tree means resource savings, and moving to RISC-V opens the door for more efficient proofs. This reflects a long-term vision for the evolution of Ethereum’s core.