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
More
There has been some activity in the WAX ecosystem recently. The project's CTO Lukas Sliwka gave an in-depth interview, discussing many core topics—from the Core underlying upgrade, decentralization direction, to upcoming ecosystem plans.
This conversation covers several questions that builders are most concerned about: how the technology will iterate, how the governance structure will evolve, and what new actions are happening in the ecosystem. For projects and participants developing on WAX, this information is still worth paying attention to. The interview is not long, straight to the point, and the most core update highlights have been summarized.
Honestly, no matter how eloquently you talk about decentralization, it’s all meaningless if the contract hasn't been properly audited.
Lukas needs to prioritize formal verification; otherwise, frequent iterations will be a waste.
Changing the governance structure by just updating the organizational chart is useless; you must also guard against integer overflow vulnerabilities in the power structure.
No matter how grand the ecosystem plan, establishing a robust pre-deployment security check system comes first.
It’s not that I lack confidence, but I’ve seen too many issues caused by incomplete audits.
How well is the contract upgrade mechanism designed? That’s the real test of a CTO’s skill.
It sounds very professional, but I’m just worried it’ll turn into another story of "There’s no problem with the code; we misunderstood."
Layered upgrades are rare; this time, external audits must be involved—don’t develop in isolation.
Has the exploit chain been considered? That’s the most easily overlooked aspect.