Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.moca.network/llms.txt

Use this file to discover all available pages before exploring further.

Breaking Change: Sandbox Now Defaults to TestnetStarting with AirKit 1.8.0-beta, the Sandbox environment defaults to Moca Chain Testnet.
Make sure you’re selecting the correct chain when using different build environment. Otherwise, your app may hit unexpected errors
EnvironmentMoca ChainPurposeDeveloper Dashboard
Sandbox (Testnet)TestnetFor development & testinghttps://developers.sandbox.air3.com/dashboard
Once Mainnet is available, Production credentials will be validated against Mainnet and hence previously issued credentials on Testnet will need to be re-issued. Issuance Schemas and Programs may be migrated. Your Issuer and Verifier DID may also change.

Sandbox Environment Changes

Starting with AirKit 1.8.0-beta, the Sandbox environment defaults to Moca Chain Testnet instead of Devnet. Both Testnet and Devnet remain available for development, with Testnet being the recommended choice to align with Production.

What’s Changed

Before (< 1.8.0)After (1.8.0-beta+)
Sandbox → Devnet (Chain ID: 5151)Sandbox → Testnet (Chain ID: 222888)
Dashboard: https://developers.sandbox.air3.comDashboard: https://developers.sandbox.air3.com

Impact

  • Credentials issued on Devnet are not available on Testnet
  • Smart Account addresses remain the same across networks
  • You will need to re-issue test credentials on Testnet
We recommend migrating to Testnet as soon as possible to align with production.

Initializing AirService with the correct Environment

import { AirService, BUILD_ENV } from "@mocanetwork/airkit";

const airService = new AirService({
  partnerId: YOUR_PARTNER_ID
});
await airService.init({
  buildEnv: BUILD_ENV.SANDBOX, // BUILD_ENV.PRODUCTION
  enableLogging: true
});

Chains

ChainChain IDRPCExplorer
Testnet222888https://testnet-rpc.mocachain.orghttps://testnet-scan.mocachain.org
Mainnet2288coming sooncoming soon