Development Environments

Credentials, schemas, and programs are network-specific. Credentials issued on Testnet are not available on Mainnet (and Devnet-issued credentials are not available on either). Re-issue on the target network when you migrate. Issuance schemas and programs may need to be recreated; Issuer and Verifier DIDs may also differ per network.

​

Production mainnet access

​

Sandbox Environment Changes

​

What’s Changed

​

Impact

• Credentials issued on Devnet are not available on Testnet or Mainnet
• Smart Account addresses remain the same across networks
• Re-issue test credentials on Testnet, or on private Mainnet for approved production launches

​

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,
  enableLogging: true
});

await airService.init({
  buildEnv: BUILD_ENV.PRODUCTION,
  credentialNetwork: "mainnet",
  enableLogging: true
});

await airService.initialize(
  partnerId: 'YOUR_PARTNER_ID',
  navigatorKey: navigatorKey,
  env: Environment.sandbox, // or Environment.production
  enableLogging: true,
);

​

Chains