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 important details about the future roadmap for the execution layer in Ethereum, and the topic is very worth paying attention to.
The first point concerns the state tree – Vitalik supports transitioning from the current hexagonal structure to a more efficient binary structure. The idea here is to use advanced hash functions like Blake3 or Poseidon instead of the current method, which will significantly reduce the length of Merkle branches and verification costs. Additionally, the plan includes consolidating storage cells into pages to reduce access costs, while maintaining certain metadata to enable future state expiration features.
Regarding the virtual machine, the discussion is more bold – it proposes replacing the EVM entirely in the long term, possibly using a RISC-V architecture. The new VM should offer higher execution efficiency, better proof capabilities, support for generating ZK proofs from the client side, and simplify code execution processes.
The implementation won't happen overnight – the plan begins with replacing pre-compiled contracts first, then allowing new contracts to be deployed on the updated virtual machine, and finally achieving backward compatibility and a gradual transition. This approach reflects the team’s careful effort to avoid breaking the current system.
Interestingly, these improvements will directly impact network efficiency and scalability – a topic of great interest to everyone in the community.