Trustless Agents Plus

TAP solves a simple problem: AI agents registered on multiple blockchains have no way to prove they're the same agent or carry their reputation across chains.

TAP adds two contracts on top of ERC-8004 — without changing any existing per-chain registries.

• TAPRegistry gives each agent one canonical identity. Per-chain ERC-8004 registrations link to it via cryptographic signature proofs. Identity tokens are soulbound and non-transferable.
• TAPReputationRegistry collects per-chain reputation data, normalizes it, and computes a single 0–10,000 basis point trust score factoring quality, volume, chain diversity, and slashing history.

Here's how it works:

• an agent registers once with TAP and receives a unique agentId — a permanent, soulbound identifier derived from its Universal Executor Account address on Push Chain.
• It then submits cryptographic binding proofs (EIP-712 signatures) that link its per-chain addresses to that single agentId.
• From that point forward, any action the agent takes on any bound chain counts toward its unified reputation score.
• That score — tracked by the TAPReputationRegistry — runs from 0 to 10,000 basis points and is composed of four factors: a base anchor score, a volume multiplier for activity, a diversity bonus for operating across multiple chains, and a slash penalty for verified violations.

The result: a trust layer that travels with the agent. Not locked to one chain. Not fragmented. One identity, everywhere.

The first version of TAP is live on Push Chain (Donut testnet).

• TAPRegistry — soulbound agent identity via UEA address. agentId = uint256(uint160(ueaAddress)) % 10_000_000. One canonical ID per agent, non-transferable.
• TAPReputationRegistry — aggregated 0–10,000 bps reputation score. Formula: baseScore × volumeMultiplier + diversityBonus − slashPenalty.
• EIP-712 binding proofs — cryptographic link between per-chain agent addresses and the canonical agentId. Covers chainNamespace, chainId, registryAddress, boundAgentId, nonce, deadline.
• CAIP-2 namespace-agnostic storage — bindings store chain identities as namespace strings, not hardcoded chain IDs. Ready for non-EVM chains at the storage layer.

Currently, reputation data is written to TAPReputationRegistry by a trusted reporter. The next milestone replaces this with a decentralised network of reporters that independently observe agent activity across chains and submit signed attestations.

No single party controls what gets scored. Reporters stake to participate and get slashed for false attestations. The result: a reputation layer that's as trustless as the registry it reports into.

A dedicated web interface that lets existing agents — or the developers running them — register with TAP without touching contract ABIs directly.

Connect your wallet, submit your UEA address, sign the binding proofs for each chain you operate on, and your agent is in the registry. Built for the developer who wants the identity layer without the Foundry scripts.

Any contract on any supported chain should be able to call TAPScoreOracle.getScore(agentId) and get back the aggregated reputation score — without bridging assets or running a full node.

Implementation: a lightweight oracle that caches scores cross-chain, plus a TAPGate modifier contract that lets any protocol gate function calls on TAP score thresholds. Example: a DeFi vault only accepts strategies from agents with score ≥ 7,000 bps.

This turns TAP from a passive registry into an active permissioning layer — the credit score for agents that protocols compose against.

Agents that vouch for or delegate to other agents, creating a directed trust graph on top of TAP identities.

Example: a "portfolio manager" agent delegates execution to specialised "swap" and "bridge" agents, staking its own reputation on their behaviour. If a delegatee gets slashed, the delegator takes a proportional penalty.

This enables composable agent hierarchies with aligned incentives — and makes TAP the coordination layer for multi-agent systems, not just a single-agent registry.

Extend BindProofType beyond ECDSA/ERC-1271 to support Ed25519 (Solana), Secp256k1 with alternative address derivation (Cosmos), and Move-native signatures.

The storage layer is already namespace-agnostic — CAIP-2 strings mean the registry doesn't care what chain the identity lives on. The gap is purely in signature verification. Once this ships, TAP becomes a truly universal agent registry: not just multi-EVM, but multi-ecosystem.