Skip to main content
Moca Network is an identity infrastructure platform. Security is foundational to every design decision — from how credentials are issued to how keys are managed and how data flows between parties.

Trust model

AIR Kit separates issuer source data and signing authority from encrypted credential storage and holder-controlled disclosure:

Security layers

Zero-knowledge proofs

The Verification Program determines the requested claims, whether ZK proofs are required, and whether verification is off-chain or on-chain. Successful verification returns a Verifiable Presentation with user-approved claims and any required proof. A ZK proof can confirm a condition without disclosing the underlying value.

MPC-based key management

User accounts are backed by multi-party computation (MPC). Private keys are never held in one place — shards are distributed so that no single party (including Moca) can reconstruct the key. Keys are only assembled in a secure execution environment at the moment of signing.

On-chain anchoring

The issuer’s signature makes the credential tamper-evident. Programs that require on-chain verification can submit proofs to Moca Chain; other programs verify off-chain. DStorage object metadata is distinct from these optional verification records.

Encrypted storage

Raw source documents remain with the issuer. Encrypted credential payloads may be stored in DStorage, while users control decryption and disclosure. Credential payloads are encrypted by default. See Privacy & Compliance.

Agent delegation

Agents act for a user only through a key the user bound, with consent, to their AIR Account. Scopes are fixed at bind time. Each operation uses a 15-minute agent JWT with no refresh token, and checkout tokens are restricted to a single merchant audience. Rotating a key invalidates issued agent JWTs. See How agentic commerce works.

Account abstraction

User wallets use smart accounts (ERC-4337 account abstraction), with AIR’s MPC wallet as the signer. Smart account deployment gas is sponsored by AIR Kit. Other gas is sponsored when the operation matches your Paymaster policy; otherwise the user pays, optionally in supported ERC-20 tokens.

Further reading

How credential issuance works

Signing, holder binding, and envelope encryption, step by step.

How credential verification works

Presentations, key-binding JWTs, and backend checks.

How agentic commerce works

Agent keys, scoped sessions, and checkout tokens.

Keys & cryptography

Every key, token, and primitive in one reference.

Credential security

How credentials are signed, encrypted, and verified with user-controlled disclosure.

Data privacy

Where data lives, what is encrypted, and who can access it.

Security checklist

Integration best practices for partners.

Privacy & Compliance

Encryption, ZK proofs, and user consent.