Cowrie Research

moca-network-primary-sources-2026-05-11

3 min read

Moca Network primary sources — 2026-05-11

Official docs and site reviewed

Key excerpts / claims captured

1) Core positioning

  • docs.moca.network/learn describes Moca Network as a “chain-agnostic decentralized identity network with privacy-preserving infrastructure for identity verifications and data interoperability.”
  • The same page reduces the stack to Moca Network = Moca Chain + AIR Kit, which is the most useful high-level decomposition for corpus purposes.

2) Moca Chain as the identity anchor

  • docs.moca.network/mocachain says Moca Chain is a “Layer 1 EVM-compatible blockchain purpose-built for decentralized identity.”
  • The page says it is built on EVMOS / Cosmos SDK with CometBFT consensus and that “oracles and bridges relay identity data to other chains, so Moca Chain becomes the single source of truth for identity while staying interoperable with the rest of Web3.”
  • The same page says the chain houses credential and identity smart contracts, manages decentralized storage, and lets users relay proofs across chains.
  • The MCSP storage section describes a BNB-Greenfield-like storage network where payloads are stored by independent providers while metadata, permissions, and payments are recorded on-chain.

3) AIR Kit as the developer-facing control plane

  • docs.moca.network/airkit/quickstart presents AIR Kit as the onboarding/authentication/session layer, including SSO login, wallet-style account services, and secure session management.
  • The login quickstart says successful login enables both account services and credential services.

4) Credential issuance policy surfaces

  • docs.moca.network/airkit/quickstart/issue-credentials shows that partners must obtain Partner IDs and Issuer DIDs, configure JWKS-backed JWT authentication, create schemas, and then create issuance programs before credentials can be issued.
  • The same page notes a backend API path for issuing credentials on behalf of users, which is a meaningful centralization / operator-control surface.
  • The issuance flow exposes schema design, issuer DID custody, JWT signing, and program management as the real governance surfaces beneath the interoperability pitch.

5) Verification policy surfaces

  • docs.moca.network/airkit/quickstart/verify-credentials shows that verifier apps must configure verifier programs and question sets, fund verifier fee wallets, and supply verifier DIDs plus JWT auth.
  • The docs use the concrete example of proving “age > 18” without exposing the underlying identity document, making selective disclosure / verifier-query design a core mechanism.
  • The verification flow includes a redirect path to issue credentials when users lack them, which is analytically useful because issuance and verification are coupled operationally.

6) Product / ecosystem framing

  • moca.network markets the system as “one identity, verifiable everywhere” and says AIR Kit powers login and identity across apps while Moca Chain makes credentials into portable assets.
  • The public site also frames MOCA as paying for transactions, data generation, storage, verification, and governance.

Working interpretation for corpus placement

Moca Network belongs in the identity / attestation / social-graph cluster because it separates identity anchoring, developer onboarding, credential issuance, zero-knowledge verification, storage custody, and cross-chain relay into a legible chain-plus-SDK stack. The most reusable comparison question is not whether it is “decentralized identity,” but where practical authority sits: partner admission, schema creation, JWT/JWKS auth, issuer/verifier DID custody, verifier query design, fee-wallet funding, storage-provider dependence, or bridge/oracle relay policy.

Graph View