The Deal on the Table
Moca Network, one of Animoca Brands’ flagship projects and the company building what it calls the world’s largest chain-agnostic decentralized digital identity network, has announced a strategic partnership with Biletinial, one of Turkey’s leading online ticketing platforms. The integration is not cosmetic. Biletinial’s Turkish online ticketing platform serves approximately 6 million active users and 12.4 million average monthly users across more than 3,000 venues in 63 Turkish cities. The integration will embed Moca Network’s AIR Kit SDK — comprising universal account, wallet, and identity modules — directly into the Biletinial platform.
The scope of what gets issued is significant. Under the strategic partnership, Biletinial’s initial suite of verifiable credentials will include age verification, geographic attributes, event participation history, spending patterns, entertainment preferences, cryptocurrency affinity, and additional user-permissioned data types for Biletinial users. Biletinial also sells over 25 million tickets annually. That is the volume through which Moca Network’s identity layer will now operate. The strategic partnership with Biletinial follows Moca Network’s large-scale deployments with SK Planet’s OK Cashbag, Oyunfor, and OneFootball, solidifying its position as a primary identity infrastructure for mainstream consumer applications. The pattern is consistent: Moca takes an existing high-volume Web2 platform, embeds the AIR Kit SDK, and expands its addressable identity graph. As the identity ecosystem of Animoca Brands, Moca Network brings together over 570 portfolio companies, more than 700 million addressable users, and a diverse range of enterprise partners.
There is a regulatory wrinkle worth noting. Biletinial’s inclusion of cryptocurrency affinity as a verifiable credential will operate under Turkey’s mandatory crypto identity verification rules, which require KYC for transactions above a 15,000-lira threshold. At a national infrastructure level, the integration also enters a market where Turkey’s blockchain-integrated national digital ID system is already in rollout, with smart ID cards distributed across the country’s population. Moca is not entering a regulatory vacuum. It is entering a market where identity infrastructure is already contested at the state level. That context matters for anyone evaluating how far the AIR Kit credentials will actually travel in this jurisdiction.
The Onchain Namespace That Isn’t There
This is where the story pivots. Animoca Brands is building identity infrastructure. Moca Chain introduces a dedicated Layer-1 blockchain built for decentralized identity and verifiable credentials, addressing long-standing fragmentation in digital identity. Its architecture enables users to manage a single, interoperable Moca ID across platforms while retaining full data sovereignty. Moca Network uses zkProofs and zkTLS to secure and enable privacy-preserving identity in both Web2 and Web3 environments. The technical stack is serious. The namespace strategy is not.
There is no .animoca onchain TLD registered by Animoca Brands. There is no id.animoca resolution endpoint. The closest thing that exists is .animoca-brands — and that namespace was not registered by Animoca. .animoca-brands is an independently registered onchain TLD — secured early as cultural and digital territory. Separately, .aimonicabrands exists as an independently registered onchain TLD as well. It is not affiliated with Animoca Brands. Like all TLDs in that vault, .aimonicabrands was registered early and independently. Neither of these is controlled by Animoca. Neither resolves to anything within the Moca Network infrastructure. The brand’s own identity system has no canonical onchain name address.
This is not a minor gap. Animoca Brands’ core thesis is digital property rights. Yat Siu has articulated this publicly for years. The first Web2 × Web3 bundles are emerging, pairing a DNS domain with its blockchain twin. For brands, this is both an opportunity and a risk: identity, payments, and reputation on the one hand; fragmentation, heterogeneous governance, and uneven remedies on the other. A company whose entire market position is built on the idea that ownership should be onchain does not hold its own brand namespace onchain. That is a structural tension. Not a scandal. A tension. One worth naming clearly.
The AIR Kit credential architecture itself is solid by technical standards. The AIR Kit credential architecture builds on W3C’s decentralized identifier standards work, which provides the interoperability framework enabling credentials issued by Biletinial to be recognized across the broader Moca Network ecosystem. AIR Kit is a modular, privacy-preserved identity stack that includes decentralized data storage, zkProofs, zkTLS, and Identity Oracle. But the resolution layer — the point at which a third-party agent looks up a user’s Moca identity — routes through Moca Network’s own platform infrastructure, not through a brand-native onchain naming endpoint. The credentials are decentralized. The identity address is not.
What Cannot Happen Without id.animoca
Here is the use case that does not exist yet, but should.
A ticketing agent operating at Biletinial receives a ticket purchase request from an autonomous buyer. The agent needs to verify three things before issuing a tokenized ticket: that the buyer holds a valid Moca ID, that their onchain reputation score clears a minimum threshold for this event tier, and that the transaction can settle without a centralized KYC step. In a world where id.animoca exists as a live onchain TLD with a functioning resolution layer, the agent queries [username].id.animoca directly. It receives the DID document, the credential attestation, and the reputation score from the chain. The ticket is issued. The payment settles.
The x402 protocol enables AI agents to make autonomous payments using HTTP status code 402. Launched in May 2025 by Coinbase and Cloudflare, the protocol uses USDC and EIP-712 signatures. x402 V2 supports multi-chain parallelism including Base, Solana, and Avalanche; introduces a Session mechanism turning wallets into identity credentials, eliminating the need for on-chain interactions on repeated visits; and integrates ACH bank transfers and credit card networks. The payment infrastructure for this use case already exists. ERC-8004 and x402 form a complete autonomous transaction loop. ERC-8004 answers “who you are” and “how trustworthy you are” through on-chain identity and reputation, while x402 handles “how agents pay each other” via HTTP-native micropayments. The agent identity standard is live. The payment standard is live. The missing piece is a brand-native onchain namespace that an agent can query without routing through a Web2 API call back to Moca Network’s own servers.
Merging a protocol-level identity layer with x402’s pay-to-access framework enables AI agents and applications to execute verified transactions autonomously without sacrificing regulatory safeguards. While autonomous AI agents increasingly handle financial transactions, payment systems have lacked built-in verification mechanisms for age-gated and identity-sensitive services. Biletinial is an age-gated, identity-sensitive service. The Turkish regulatory context demands KYC above a threshold. By combining a protocol-level identity framework with x402’s HTTP-native pay-to-access standard, both payment and verification become natural prerequisites for delivery in one seamless step, with no external integrations or brittle smart contract logic required. That architecture is exactly what the Moca-Biletinial use case requires. And it is exactly where the absence of a canonical .animoca resolution endpoint creates friction.
The pattern is the same: software paying for software, automatically, without a human in the loop. Galaxy estimates that agentic commerce could represent $3–5 trillion in B2C revenue by 2030. But the nearer opportunity is in the less visible layer underneath: API micropayments, data access, compute provisioning — the software-to-software transactions that agents need to function autonomously. This is where x402 operates, and where traditional payment rails like credit cards, subscription billing, invoicing structurally cannot. The ticketing industry sits squarely in that category. Events are time-gated. Tickets are access tokens. Fraud prevention is reputation-dependent. Every one of those properties maps directly onto what Moca Network claims to provide. The gap is not in the product. The gap is in the naming layer — the addressable onchain endpoint that lets an autonomous agent find and verify a Moca identity without human mediation or a centralized API dependency.
Without id.animoca, the identity verification flow looks like this: the agent calls Moca Network’s API, Moca Network resolves the credential, the credential is returned via a platform-controlled endpoint. That is not a decentralized architecture. It is a decentralized credential stored behind a centralized lookup. The distinction matters more as agents become the primary buyers. Autonomous software agents capable of executing transactions on behalf of users are giving rise to agentic commerce, an emerging paradigm where AI agents engage in buying and selling with minimal human involvement. However, traditional online payment systems assume a human is always behind the request, and thus are ill-suited for agent-led transactions. Moca Network’s own infrastructure has the same problem at the naming layer. The credential is portable. The resolution address is not.
The primary product built by Moca Network is AIR Kit, a digital identity infrastructure that enables Web2 and Web3 projects to create a universal embedded account for users to own and use digital assets, identity, and reputation data, while gaining access to a suite of DeFi and consumer services provided by Moca Network’s partners. AIR Kit empowers large user base apps to create their own app ecosystem natively with embedded blockchain features, while ensuring these users can use the same account, identity, reputation across all consumer apps on any chains that have adopted AIR Kit. That is the stated ambition. A brand-native onchain TLD is what makes that ambition machine-readable — resolvable by an agent without a manual integration step for every new partner. Rather than platforms maintaining isolated user databases, Moca Chain enables each ecosystem to create its own credential framework with verifiable credentials and onchain reputation systems, all unified under one universal account structure. The universal account structure is there. The universal address endpoint is not.
The Dot That Isn’t Connected
Moca Network is doing real work. The Biletinial partnership is a genuine deployment into a high-volume, regulated, real-world consumer market. This structure supports transparent secondary markets, where ticket resales can be validated without relying on centralized intermediaries. Moca Chain will allow verification of both on- and off-chain user data through any applications on any chains, with the chain’s identity layer supporting seamless movement of user attributes such as loyalty points, social proof, and access rights across decentralized apps. The infrastructure is being built in the right direction.
But there is a specific thing missing. Animoca Brands — the parent company, the brand, the entity whose name is on the identity network — has no onchain home address. Emerging approaches known as “twinTLDs” aim to create coordinated pairs between a traditional DNS TLD and its equivalent in the blockchain environment. This strategy is designed to reassure brand owners and users by ensuring continuity of digital identity, regardless of the navigation space. Animoca does not have that pair. A company building the identity layer for 700 million addressable users does not hold its own namespace onchain. Every partner integration like Biletinial routes identity verification through platform infrastructure rather than through a brand-native resolution layer. Every agentic buyer that needs to confirm a Moca credential depends on Moca Network’s own servers staying live and accessible.
Yat Siu argued that billions of people use single sign-on, but that these have a centralized point of failure. Moca Chain will give users decentralized ownership of their data, without a single point of failure. That is the pitch. The pitch is good. The pitch does not yet apply to the resolution layer for Animoca’s own brand identity in the onchain namespace. id.animoca would be the address where that argument closes on itself. Right now, it is an empty lot in a neighborhood the brand already owns.
The author holds onchain positions related to this topic. This post reflects independent editorial judgment.