Testnet Deployment

EarnProof should remain testnet-only until security review is complete.

Contract Scripts

The contracts repo includes PowerShell deployment automation:

.\scripts\deploy-testnet.ps1 -Source deployer -Admin G... -IssuerAddress G... -Output scripts\deployment-manifest.testnet.json

The script installs wasm32v1-none if needed, builds release WASM artifacts with stellar contract build, deploys the three contracts, initializes them, approves schema version 1, registers the backend issuer, and writes a deployment manifest with contract IDs and WASM hashes. Validate the generated manifest before using it in backend or frontend environments:

.\scripts\verify-manifest.ps1 -Manifest scripts\deployment-manifest.testnet.json

Deployment Order

Deploy protocol config contract.
Deploy issuer registry contract.
Deploy proof registry contract.
Initialize contracts.
Approve schema version 1.
Register the initial EarnProof issuer.
Deploy backend with contract IDs.
Deploy frontend with backend URL.

Contract Manifest

The live testnet manifest is checked into the contracts repository at:

scripts/deployment-manifest.testnet.json

{
  "network": "stellar-testnet",
  "deployedAt": "2026-08-11T00:00:00Z",
  "admin": "GCDPMNCCMADKEL4YJAJNJXTCGZFAGWQCEFXJYBZVLJCFYOI76FTX6HMV",
  "source": "deployer",
  "initialIssuer": {
    "address": "GCDPMNCCMADKEL4YJAJNJXTCGZFAGWQCEFXJYBZVLJCFYOI76FTX6HMV",
    "issuerIdHash": "d0aaef7dc73ae306d32c58b54829e422737a8a936c41991ce490f5822af294ce",
    "metadataHash": "75f7b32c6a13e9d7000b52b33ee1a657dd1359a6bd79837af6fdc6a1d393d87b"
  },
  "contracts": {
    "protocolConfig": "CC3OREX5QBIKJ5JOW36JFJJW7TLAKJOVT5WJXEITGALO7MU32KHICS2A",
    "issuerRegistry": "CB73TVWVJIIVNTKLWSHZB5NL2UIF3B3EUL4YH4MUD6EYX6SFIHE77D2F",
    "proofRegistry": "CCMTAXBWN2ZGEDVKGHT6GQENZSTBSLQAGYGGKJWNMDSTVRT2QNMMNWRK"
  },
  "wasm": {
    "protocolConfig": {
      "path": "target/wasm32v1-none/release/protocol_config.wasm",
      "sha256": "..."
    },
    "issuerRegistry": {
      "path": "target/wasm32v1-none/release/issuer_registry.wasm",
      "sha256": "..."
    },
    "proofRegistry": {
      "path": "target/wasm32v1-none/release/proof_registry.wasm",
      "sha256": "..."
    }
  },
  "schemaVersions": [1],
  "commands": ["..."]
}

Backend Environment

STELLAR_NETWORK=testnet
STELLAR_HORIZON_URL=https://horizon-testnet.stellar.org
STELLAR_NETWORK_PASSPHRASE=Test SDF Network ; September 2015
PAYMENT_ENCRYPTION_KEY=<32-byte-base64-or-hex-key>
CONTRACT_ANCHORING_ENABLED=true
CONTRACT_ANCHORING_REQUIRED=false
STELLAR_CLI_PATH=stellar
STELLAR_CLI_SOURCE=deployer
PROOF_REGISTRY_CONTRACT_ID=CD...
EARNPROOF_ISSUER_ADDRESS=G...
EARNPROOF_SCHEMA_VERSION=1

For the current testnet deployment:

PROOF_REGISTRY_CONTRACT_ID=CCMTAXBWN2ZGEDVKGHT6GQENZSTBSLQAGYGGKJWNMDSTVRT2QNMMNWRK
EARNPROOF_ISSUER_ADDRESS=GCDPMNCCMADKEL4YJAJNJXTCGZFAGWQCEFXJYBZVLJCFYOI76FTX6HMV

The backend proof service signs credentials, serves public verification, and can optionally anchor proof commitments, revoke anchored proofs, and check public on-chain proof status with the Stellar CLI. Keep CONTRACT_ANCHORING_REQUIRED=false during early testnet runs if proof creation should continue when anchoring fails.

Verification

Before announcing a demo, confirm:

frontend loads,
backend health passes,
payment sync can reach Horizon,
contracts are initialized,
deployment manifest contains real contract IDs and real WASM hashes,
backend contract anchoring returns an anchored result or a clearly logged best-effort failure,
verification endpoint returns safe public responses.

Guides

Operations

Testnet Deployment

Contract Scripts

Deployment Order

Contract Manifest

Backend Environment

Verification

​Contract Scripts

​Deployment Order

​Contract Manifest

​Backend Environment

​Verification

Contract Scripts

Deployment Order

Contract Manifest

Backend Environment

Verification