[BIOS] VERIFIED AI v1.0.0 — Base Mainnet Node [INIT] Loading attestation module........ [OK] AttestationRegistry @ 0x3dBF...81eb [OK] ProviderRegistry @ 0x8E17...4c2A [OK] Groth16Verifier @ 0xA23d...891F [OK] AgentCapabilityRegistry @ 0xF910...33bC [NET] Connecting to Base mainnet RPC... [OK] Chain ID: 8453 — CONNECTED [ZK] Initializing Groth16 verifier circuit... [OK] zkML engine ready [BOOT] All systems operational. Starting UI...
Loading
VERIFIED AI/// BASE MAINNET/// ZKML ATTESTATION/// ERC-8004/// ON-CHAIN PROOF/// GROTH16 VERIFIED/// ATTESTATION REGISTRY/// OPEN SOURCE/// MIT LICENSE/// VERIFIED AI/// BASE MAINNET/// ZKML ATTESTATION/// ERC-8004/// ON-CHAIN PROOF/// GROTH16 VERIFIED/// ATTESTATION REGISTRY/// OPEN SOURCE/// MIT LICENSE///
System Status: All Systems Operational

SSL certificates
for the age
of agents.

AI systems are making consequential decisions — loan approvals, medical triage, legal analysis. But there's no way to prove which model ran, what input it received, or what it actually produced. Verified AI anchors every inference to an immutable on-chain record.

$VERIFIEDAI CA 0xaf0d3d0a26411aCbAbC4205d74764145aC5CEB07 TRADE
0Attestations
4Contracts
8453Chain ID
~$0.002Gas / Attest

On-chain proof that your AI actually ran

AI outputs are currently unverifiable. Any bad actor can claim their output came from GPT-4o, Claude, or any other model. Verified AI closes that gap with cryptographic attestation anchored to Base.

The Problem

No proof, no trust

AI systems make consequential decisions without any mechanism to verify which model ran, what input it received, or what it produced. AI accountability is theater.

The Solution

Hash. Prove. Anchor.

Verified AI hashes both the prompt and response, generates a Groth16 zkML proof, and anchors everything permanently to Base mainnet in a single transaction.

Three cryptographic commitments

Every attestation produces three immutable commitments stored in the on-chain registry.

// Three immutable commitments per inference
keccak256(prompt)   → inputHash
keccak256(response) → outputHash
Groth16(π)          → proofHash

// Stored in AttestationRegistry on Base
// Contract: 0x3dBF622ABC705d2Ec0E07EB0fCbb1AbFDe0281eb
inputHash

Prompt binding

Cryptographic commitment to the exact input. Cannot be retroactively changed or forged.

outputHash

Response binding

Immutable record of the exact output. Prove the model said exactly this — nothing more.

proofHash

ZK verification

Groth16 zkML proof that the inference ran inside a verified TEE. Trustless, permissionless verification.

From zero to verified in 5 minutes

01 //

Install SDK

Add verified-ai-sdk to your project, or integrate directly via ethers.js / viem.

02 //

Connect Base

You need a Base mainnet wallet. Gas is ~$0.002 per attestation.

03 //

Register Provider

One-time call. Declare your TEE type and signing key in ProviderRegistry.

04 //

Attest Inference

Hash model fingerprint + prompt + response. Submit the three commitments on-chain.

05 //

Verify

Permissionless read — no private key needed. Works from any environment.

// SDK — TypeScript / JavaScript
import { VerifiedAI } from 'verified-ai-sdk'

const client = new VerifiedAI({
  network: 'base-mainnet',
  privateKey: process.env.PRIVATE_KEY,
})

// Register your inference node (once)
await client.registerProvider({
  name: 'My Inference Node',
  teeType: 'AWS_NITRO',
  publicKey: myTEESigningPublicKey,
})

// Attest an inference
const result = await client.attest({
  model: 'gpt-4o',
  prompt: userPrompt,
  response: modelResponse,
})

console.log(result.id)      // bytes32 on-chain ID
console.log(result.txHash)  // basescan.org/tx/0x…

Four contracts deployed on Base

All contracts are open source, MIT licensed, and verifiable on BaseScan.

/* ════════════════════════════════════════════ $VERIFIEDAI ════════════════════════════════════════════ */

$VERIFIEDAI — governance + access

Token is the key to the network. Stake to become a verified provider, vote on whitelist decisions, earn from attestation fees.

1B Total Supply
Base Chain
0% Team Allocation
100% Community
$VERIFIEDAI CA 0xaf0d3d0a26411aCbAbC4205d74764145aC5CEB07 TRADE
/* ════════════════════════════════════════════ ROADMAP ════════════════════════════════════════════ */

From token to infrastructure

Community-first. Infrastructure follows.

✓ Done

Phase 1 — Foundation

  • Token deployed on Base
  • 4 contracts live
  • SDK published (npm)
  • Landing page live
▶ Now

Phase 2 — Community

  • Token/community growth
  • Twitter presence
  • Provider outreach
  • Base ecosystem grant
Next

Phase 3 — Providers

  • Onboard first provider
  • Gaia / Akash integration
  • Attestation volume live
  • SDK v1.0 stable
Future

Phase 4 — Scale

  • Multi-chain expansion
  • Enterprise tier
  • zkML mainnet proofs
  • DAO governance
# Install SDK
npm install verified-ai-sdk
# v0.2.0 · MIT · 0 dependencies · Base mainnet