AAS - Agent Attestation Service

AAS is an on-chain credential and reputation system for autonomous AI agents, built natively on Chainlink's Confidential Runtime Environment (CRE).

THE PROBLEM:
As AI agents become infrastructure executing trades, managing portfolios, and coordinating with other agents, there's no trustless way for smart contracts to verify an agent's track record, and exposing raw performance data reveals competitive intelligence.

THE SOLUTION:
AAS issues tier-based EAS attestations (STANDARD: 10+ tasks at 70% success, VERIFIED: 100+ tasks at 95% success) backed by zero-knowledge proofs. Chainlink CRE's Confidential HTTP fetches sensitive performance data inside a Trusted Execution Environment (TEE), ensuring raw metrics never leave the enclave. An UltraHonk ZK proof (via Noir) proves threshold compliance without revealing actual numbers. The proof is verified on-chain and anchored as a tamper-proof Ethereum Attestation Service (EAS) record.

HOW IT WORKS:

1. Agent requests STANDARD or VERIFIED attestation
2. CRE Workflow A (attestation-issuance) triggers with the requested tier
3. ConfidentialHTTPClient fetches performance data from the agent platform API
4. ZK proof is generated with tier-specific thresholds (STANDARD: 10 tasks, 70% / VERIFIED: 100 tasks, 95%)
5. CRE submits the proof + tier metadata on-chain via EVMClient.writeReport() after multi-node consensus
6. AASRegistry creates a tier-stamped EAS attestation
7. Any smart contract or agent can verify credentials via CRE Workflow B (attestation-verification) in a single call

ARCHITECTURE:
Smart Contracts (Solidity 0.8.24, deployed on Sepolia):

• AASRegistry: Core registry managing agent identities, attestation metadata, tier validation, and EAS schema integration
• AASZKVerifier: Wrapper for UltraHonk proof verification
• HonkVerifier: Auto-generated Barretenberg verifier contract
• EAS integration: Four schemas on Ethereum Attestation Service for StandardTier, VerifiedTier, Endorsement, and TaskCompletion attestations

Zero-Knowledge Proofs (Noir v1.0 + Barretenberg UltraHonk):

• Circuit: capability-threshold.nr - proves task_count >= threshold_tasks AND success_rate >= threshold_rate_bps
• Private witnesses: task_count, success_count, data_commitment_preimage
• Public inputs: threshold_tasks, threshold_rate_bps, data_commitment (Poseidon2 hash)

Chainlink CRE Workflows (TypeScript, CRE SDK):

• Workflow A (attestation-issuance): ConfidentialHTTPClient fetches performance data from agent platform API inside TEE, checks tier eligibility, generates ZK proof calldata, submits on-chain via EVMClient.writeReport() after multi-node consensus
• Workflow B (attestation-verification): Queries AASRegistry on-chain via EVMClient.callContract(), decodes EAS attestation data, validates tier/expiry/revocation, returns verification result
• Workflow C (reputation-graph): Event-triggered via EAS logTrigger, builds IPFS reputation graph from on-chain attestation/endorsement events, pins to IPFS, commits CID hash on-chain
• Secret management: Vault DON injects PLATFORM_API_KEY at runtime
• Consensus: consensusIdenticalAggregation() ensures multi-node agreement before on-chain writes

Backend Infrastructure:

• REST API (Node.js + Express): Exposes /attest, /verify, /reputation endpoints, integrates with CRE workflows via CLI simulation
• Mock Performance API: Simulates external agent platform (OpenClaw, LangChain, etc.) for demo purposes
• Proof generation service: TypeScript wrapper around nargo execute + bb prove for UltraHonk proof generation

Frontend (Thirdweb SDK + Next.js 14):

• Agent dashboard: Register agents, request attestations, view tier status, explore reputation graph
• Thirdweb Connect: Wallet connection, signature-based agent ID derivation
• Thirdweb SDK: Contract interactions, transaction signing, event subscriptions