← Protocols
Enjin
NFT / Marketplace·Enjin Blockchain (Relaychain) · Enjin Matrixchain · Canary Matrixchain

Enjin

01Description

Long-standing gaming NFT platform. Enjin Blockchain (a Substrate/Polkadot-style L1 with a Relaychain + Matrixchains) provides protocol-level NFT primitives, gas tank sponsoring, and a managed Wallet Daemon for studios. The Enjin Platform exposes a GraphQL API plus official SDKs (TypeScript, C#/Unity, Unreal, Godot) so games can mint, distribute, and trade NFTs without writing Substrate pallets.

02Best for
  • 01Unity and Unreal games minting NFTs at scale
  • 02fungible + non-fungible items as native assets (no ERC-20/721 boilerplate)
  • 03gas-sponsored player UX via the Enjin gas tank
  • 04studios needing a managed wallet daemon for backend signing
  • 05ENJ-denominated reward economies
03Install
  • pnpm add @enjin/platform-sdk graphql graphql-request
04Environment variables
VariableScopeDescription
ENJIN_PLATFORM_URLServerEnjin Platform GraphQL endpoint (e.g. https://platform.enjin.io/graphql).
ENJIN_PLATFORM_TOKENServerEnjin Platform API bearer token from your Enjin developer account.
ENJIN_WALLET_DAEMON_URLServerURL of your Wallet Daemon instance (signs transactions server-side).
05Prompt snippet
Use the Enjin Platform GraphQL API as the backend integration point: send mutations like `CreateCollection`, `MintToken`, `TransferToken`, `BatchSetAttribute` against `https://platform.enjin.io/graphql` with a bearer token. Run the official Wallet Daemon (Docker) to sign and broadcast queued transactions on your behalf — the platform queues operations until the daemon picks them up and submits to the Matrixchain. Game clients integrate via `enjin/platform-csharp-sdk` (Unity), the Unreal plugin, or `@enjin/platform-sdk` for web. Players hold an ENJ-funded wallet (or use the Enjin gas tank for sponsored txs). NFT metadata and balances are queried via the same GraphQL schema; do not try to hit Substrate RPC directly unless you've migrated off the platform.
06Gotchas
  • Enjin Blockchain is Substrate-based (its own L1, Polkadot-style consensus) — Solidity/EVM contracts and viem/wagmi do not work; everything goes through the Enjin Platform GraphQL or the Substrate RPC at the protocol level.
  • The Wallet Daemon is a separate service you must self-host or run as a managed instance; without it, mutations queue indefinitely on the platform with no visible error in the GraphQL response.
  • Bridging ENJ / Matrixchain assets to Ethereum/EVM is custodial via Enjin's bridge service and has historically been paused during migrations (e.g. ENJ -> ENJ migration to the new chain) — design for week-long bridge outages.
  • Game engine integration uses the official C# (Unity) and Unreal SDKs, but they wrap GraphQL so latency = platform + chain finality (~12s blocktime); avoid putting mints on the gameplay critical path.
  • Gas tank sponsoring requires you to fund a tank with ENJ and configure rules; an exhausted tank reverts player txs with a generic error rather than auto-refilling.
  • Peer-to-peer transfers between players via the platform are gated on KYC tier in some jurisdictions, and royalties are enforced at the asset (token) level — secondary venues that ignore the Enjin marketplace contract still pay royalties because they're protocol-native.
07Alternatives