Enjin Platform v3 Beta: For Developers and AI Agents

Today we're announcing the public beta of Enjin Platform v3, a complete rewrite of the developer platform that powers Web3 games and applications across the Enjin ecosystem.

This isn't an incremental release. v3 is a ground-up rebuild with a singular focus: reliability, performance, and consistency. To get there, we rebuilt Enjin Platform on the same data layer that already powers Enjin Wallet and NFT.io, bringing the developer surface into alignment with the rest of the stack.

You can start building on it today at platform.beta.enjin.io.

What you need to know

• Beta URL: https://platform.beta.enjin.io
• GraphiQL Playground: https://platform.beta.enjin.io/graphiql
• Wallet Daemon: v3.0.5 or later required for write operations.
• Networks supported: Enjin Relay, Enjin Matrix, Canary Relay, Canary Matrix — all from a single instance.
• Deployment: v3 is cloud-only. Self-hosted is no longer supported.
• For v2 users: new account required; v2 is now officially deprecated (no retirement date as of now).

Why a Rewrite

Enjin Platform has been the front door for hundreds of projects integrating tokens, NFTs, and on-chain functionality. But as the Enjin Blockchain ecosystem grew to include Relay, Matrix, Canary Relay, and Canary Matrix, the original architecture started to show its age. Developers were hitting friction that shouldn't have existed: separate instances per network, manual workflows for things that should be programmatic, and a long backlog of feature requests that the v2 codebase wasn't built to absorb.

Enjin Platform v3 fixes that.

What's New in v3 Today

• One Instance for the Entire Multiverse. Previously, supporting Enjin Relay, Enjin Matrix, Canary Relay, and Canary Matrix meant running four separate instances. v3 consolidates all networks and chains into a single instance — one account, one daemon, all chains.
• Redesigned Transaction Architecture. v3 treats single and batched transactions as the same primitive. The code you write for one extrinsic is the code that handles a batch of 150 — no special batching mode, no separate endpoints, no forked code paths to maintain.
• Fuel Tank Auto-Signing. Using the new requiresSignature rule, fuel tanks can sign extrinsics automatically — removing one of the biggest sources of friction in covering transaction fees on behalf of your users, allowing for instant onboarding of new users.
• Cross-Network Queries. Query data across the entire Enjin Blockchain network without first having to track a collection.
• Relaychain Interaction. Extensive support for Relaychain operations, including staking-related functions.
• Programmatic Metadata Refresh. Refresh metadata for your collections and tokens programmatically — no more manual triggers from the UI.
• Proxy Accounts. Native support for proxy accounts, enabling more sophisticated access patterns and delegated authority.
• Improved API Token Management. Token naming, rotation, and last-used visibility — proper control over your credentials.
• Tailored Notifications. Stay informed when something matters — daemon offline, daemon outdated, and other operational events.

…plus a long list of smaller improvements developers have been asking for.

The Roadmap

What's coming next:

• Wallet Requests — push transaction signing requests from your application directly to a linked player's Enjin Wallet for them to review and authorise. First on the list, first to be delivered.
• Dedicated SDKs and game engine plugins — C# and C++ SDKs are coming, with dedicated Unity and Unreal Engine plugins to follow.
• AI Agent support — full suite of functionality dedicated to provide rails to autonomous AI agents.
• Real-time events mechanism — a new system for streaming on-chain events as they happen.
• Fuel tank creation and management — full UI and API for setting up and operating fuel tanks.

Built for AI Agents

The next class of Web3 actors is already here: AI agents are about to transact at scale. They'll book travel, manage subscriptions, negotiate purchases, and run workflows around the clock, constantly and at machine speed.

We're building Enjin Platform v3 for this. It's the wallet for AI agents on Web3, and the platform humans use to manage them. Same infrastructure, expanded scope. Agent-scoped accounts act on behalf of a user under rules the user defines: what the agent can do, how much, for how long, with which counterparties.

MCP support is shipping imminently. Native compatibility with Anthropic's Model Context Protocol (MCP) lands soon. MCP is the open standard for how AI agents discover and invoke external tools and data, now used by Claude, Cursor, and a growing list of agentic IDEs. Once shipped, the full GraphQL surface of Enjin Platform will be accessible to any MCP-aware client without bespoke integration. MCP is the integration surface, with deeper agent-native functionality following in the coming months.

Getting Started

If you're only reading data, you can start querying immediately — no daemon required, just an API token. For any write operation (creating managed wallets, signing transactions, and so on), you'll need to run Enjin Wallet Daemon v3.0.5 or later.

A note on wallet connectivity: because v3 is designed and intended for developers, it is no longer possible to use an external wallet to interface with Enjin Platform directly, and usage of the Wallet Daemon is required.

For Existing Enjin Platform v2 Users 

A few things you should know:

• A new account is required. Existing v2 users will need to create a new account to access Enjin Platform v3 Beta.
• No retirement date yet. Enjin Platform v2 has no scheduled sunset date. We'll give plenty of notice ahead of any retirement timeline so you have time to migrate cleanly.
• No self-hosted option in v3. If you run v2 self-hosted, you'll need to migrate to the managed v3 service or remain on v2 through the deprecation window.
• v2 is now officially deprecated. This applies to Cloud-hosted and self-hosted.

A Beta, Not a Final

This is an early beta release. Some bugs and incomplete functionality are to be expected, and we are iterating based on developer feedback. Please report anything you encounter.

The documentation site is currently being rebuilt for the v3 architecture and is not yet a reliable reference. In the interim, the GraphQL schema in the GraphiQL playground is fully self-documenting.

Help Us Build It

The point of a beta is to build what works, what doesn't, and what's missing. Your feedback shapes the stable release.

• Try it: https://platform.beta.enjin.io
• Report issues and request features via our developer community on Slack: https://enj.in/ecosystem-slack

We're working to make Enjin Platform v3 the most comprehensive — and most developer-friendly — Web3 game infrastructure available. We'd love your help getting there.