Over a billion tokens have been minted on Enjin. Game items, collectibles, rewards, tickets: behind every one is a developer who needed the blockchain to do something specific, reliably, at scale. The Enjin Platform is the API that makes that possible.
In May, we opened the doors to the Enjin Platform 3 beta, a ground-up rebuild of that API, and asked you to test it, break it, and tell us what was missing.
You did all three. And it made the platform better.
Today, Enjin Platform 3 is out of beta and live at platform.enjin.io.
If you sat out the beta, here's what the rebuild delivers.
TransactionInput that can be used for one-off or batched transactions. The code you write for one extrinsic is the code that handles a batch of 150. Complete flexibility over how the chain handles failures within a batch using batchMode. No separate endpoints, no forked code paths. And every transaction takes the same options: sponsor it with a Fuel Tank, execute it through a proxy, or attach an idempotency key so a retried transaction never lands twice.requireSignature rule to the tank instead, setting the value to that of your daemon, and the Platform handles the rest automatically: the tank covers the fee, your daemon provides the signature, and nobody needs to be registered in advance. A new player can receive their first token the moment they arrive, without ever seeing a signing prompt.Plus a long list of smaller improvements shaped directly by beta feedback: token groups, configurable batch failure handling, Fuel Tank rule-set targeting, preflight transaction validation, stricter GraphQL validation, corrected ENJ base-unit scaling throughout the API, a built-in Canary testnet faucet, and so much more.
Put a few of those together and a bigger story appears. A new player can start playing without setting up a wallet, paying fees, or approving a single prompt: a managed wallet holds their items from the first session, and a Fuel Tank covers their fees. Ownership arrives when they're ready for it, not before. And the final piece of that story is next.
The most-requested item on the beta roadmap was the first one we promised — and it ships today in Enjin Wallet v3.6.
With Wallet Requests, your application can push a transaction signing request directly to a linked player's Enjin Wallet. The player gets a push notification, opens their wallet, sees exactly who is asking and what they're being asked to approve, and signs or rejects it. No browser extension, no external signer, no friction.
And players always know who's on the other end. Only developers with a complete profile can send requests, and every request carries your Developer Profile: your name and logo, shown to the player everywhere your requests appear. Set yours up in the Platform's Settings page before you send your first one.
The updated Enjin Wallet is available now on Google Play and the App Store.
When we announced the beta, we said the next class of Web3 actors would be autonomous agents, and that this platform would be built for them. As of today, that's not a roadmap item. It's in production.
Enjin Platform 3 ships with a native MCP server at platform.enjin.io/mcp. Point Claude, Cursor, or any MCP-aware client at it, authorize the connection with OAuth, and your agent can query everything the Platform knows, resolve addresses across every Enjin network, and, if you allow it, submit transactions.
You stay in control. Every agent connection is approved from your dashboard and scoped to read-only or write access. Write access is deliberately narrow: agents can create transactions, create managed wallets, and refresh metadata, nothing else, and you can restrict them to signing only with the wallets you choose. Revoke a connection at any time. Your agent works at machine speed; the rules are yours.
Two things to know before you wire one up. The MCP server ships as an experimental feature: agents are the fastest-moving corner of software right now, and we'd rather ship early and improve in the open, so expect rough edges and the occasional thing that doesn't work as it should. And how far an agent gets depends heavily on the model driving it; a stronger model simply makes better use of the Platform. Start read-only, keep signing restricted, and widen access as your agent earns it.
This is the foundation, not the finish line. In a future update, agents get dedicated wallets of their own, operating under limits you define.
When we launched the beta, we published a roadmap. Here's the scorecard:
| Promised in May | Status |
|---|---|
| Wallet Requests | Shipped. Push signing requests to any linked Enjin Wallet. |
| C# SDK | Shipped. v3.0.4 stable, server-side, and Unity-ready by extension. Sample projects for Unity, Godot, C++, and a full game server. |
| Fuel Tank creation & management | Shipped. Full UI and API. |
| Real-time events | Shipped. WebSocket event streaming for transactions, wallets, and daemons. |
| AI agent support | Shipped. A native MCP server with dashboard-approved, scoped agent connections. |
Where is v2 now? platform.enjin.io serves Platform 3. v2 has moved to platform.legacy.enjin.io, where it will keep running until retirement. Don't worry though, those performing v2-related queries/mutations are still being temporarily routed to the correct service; the change was non-breaking.
When does v2 retire? November 2, 2026. After that date, v2 goes offline and requests using v2 API keys will fail.
Do I need a new account? Beta accounts carry over unchanged. If you're coming straight from v2, create a new account at platform.enjin.io.
Can I still self-host? No. Platform 3 is cloud-only. If you're running v2 self-hosted, migrate to the managed platform before November 2.
Release doesn't mean finished. Active development continues, and the near-term roadmap includes:
And we still want your feedback. If something you need is missing, tell us.
To everyone who tested, reported, and requested throughout the beta: thank you. Platform 3 is live because of you — now go mint the next billion.
You'll receive:
