Skip to content

Developers

Schemas and proof formats

The protocol-level schemas developers can inspect when they need exact structures rather than overview copy.

Build for people, not just protocols

Start with the product experience. Drop into protocol detail when you need it.

The developer surface is organized around practical primitives—AI jobs, verification, escrow, payments, agents, contracts and cross-chain messaging—without hiding what remains under development.

Temporary Unsplash placeholder · Photo by AllGo

Verifiable AI output

Applications consume receipts instead of trusting opaque execution blindly.

Engineering
ProofOfAIReceipt typeTypeScriptIllustrative
type ProofOfAIReceipt = {
  jobId: string;
  providerId: string;
  modelId: string;
  modelVersion?: string;
  inputHash: string;
  outputHash: string;
  configHash?: string;
  timestamp: number;
  nonce: string;
  verificationType: string;
  providerSignature: string;
  teeAttestationHash?: string;
  zkProofHash?: string;
};

Illustrative — conceptual shape only. Not a published or stable interface; field names and types will change.

Proprietary model path

Engineering

Closed APIs cannot be re-executed. Receipts bind provider identity, model ID, input/output commitments and a provider signature.

Open model path

Planned

Open weights can be hashed (weights, container, tokenizer, config) and independently re-run or spot-checked.

Verification tier

Engineering

verificationType states how strong the evidence is: hash, signed provider, independent verifier, TEE or zkML.

Work verification

AIPoW claims bind work, identity, epoch, and optional AI evidence.

Engineering
Conceptual
chainId + epoch
Prevents replay on another chain or epoch.
bitcoinHeaderHash
Ties the claim to Bitcoin-compatible work.
workWeight
1.00 standard, 1.05 with a qualifying Proof-of-AI receipt — a relative weight inside a fixed budget, not extra issuance.
proofOfAI
Optional evidence that qualifies the higher weight.
AIPoWClaim typeTypeScriptIllustrative
type AIPoWClaim = {
  chainId: string;
  epoch: number;
  minerAddress: string;
  auxpowWorkId: string;
  bitcoinHeaderHash: string;
  workCommitment: string;
  workWeight: "1.00" | "1.05";
  proofOfAI?: ProofOfAIReceipt;
  nonce: string;
};

Illustrative — conceptual shape only. Not a published or stable interface; field names and types will change.

Multichain message format

Carry AI intent across chains without coupling the protocol to one bridge.

Testnet TBD
CrossChainAIRequest typeTypeScriptIllustrative
type CrossChainAIRequest = {
  sourceChain: string;
  destinationChain: string;
  requester: string;
  jobId: string;
  payloadHash: string;
  paymentReference?: string;
  callbackAddress?: string;
  timeoutHeight?: number;
  nonce: string;
};

Illustrative — conceptual shape only. Not a published or stable interface; field names and types will change.

  1. 01Transport-agnostic semantic objectThe request means the same thing whichever transport carries it.
  2. 02IBC preferred for Cosmos-native routesLight-client-verified packets with acknowledgements and timeouts.
  3. 03External adapters for other ecosystemsEVM and Solana routes use adapters, each with its own security model.
Cross-chain AI jobs are asynchronous state machines with explicit request, acknowledgment, timeout, verification, and settlement states.
Developer experience improves when builders can work together around clear primitives and tooling.Photo by Mushvig Niftaliyev · Unsplash