250M+
Players across the MapleStory franchise globally, a Web2 player base that needs to onboard onto Web3 without ever feeling friction in the core game.
How Nexon brought MapleStory, a 250M-player MMORPG, onto its own L1.
Nexon, the inventor of free-to-play, is rebuilding MapleStory Universe as a hybrid Web3 game with real asset ownership, without breaking the gameplay 250M+ players already love.
GamingHybrid Web3KoreaSovereign L1
The scale of the problem
20+ years
MapleStory has been live since the 2000s, the golden age of MMORPGs. Web3 features have to integrate with two decades of accumulated game economy and content.
Hybrid
Onchain ownership, item history, and randomness, offchain gameplay performance. The architecture has to give Web3 benefits without taking Web2 speed.
A 250M-player game does not get to slow down.
MapleStory is one of the longest-running MMORPGs in the world. The fanbase is huge, the economy is mature, and the gameplay tempo is fast. Web3 features cannot be allowed to introduce a wait time. They cannot crowd out a beloved interaction. They cannot require players to learn what a private key is.
Henesys, Nexon's dedicated Avalanche L1 on AvaCloud, is engineered around that constraint. Ownership, item history, and verifiable randomness are anchored onchain. Everything else, gameplay performance, matchmaking, latency-sensitive systems, stays in the Web2 systems that already work.
What players actually feel
- Real ownership. Items players earn or trade are theirs, with verifiable history that survives the game itself.
- Player-to-player markets. Secondary markets become native, not gray-market.
- Creator economy. Outside developers can build on MapleStory's IP and economy under appropriate licensing.
What the studio gets
A studio of MapleStory's scale runs many environments. Henesys mirrors production with lightweight development, test, QA, and staging chains, so a designer can iterate on an economy change in dev without touching live player balances.
Results
Chain
Henesys L1, dedicated Avalanche
Architecture
Hybrid on/off-chain
Studio workflow
Mirrored dev/QA chains