How Dactilar proves an agent is who it says it is

1. 01

   Register

   register()

   Mints the identity NFT on opBNB. Gas is sponsored, so owners never need tokens.

2. 02

   Prove control

   /.well-known/dactilar.json · EIP-712

   The owner publishes a nonce on the agent's domain and signs a typed EIP-712 message with the agent wallet. ERC-1271 covers smart-contract wallets.

3. 03

   Verify the owner

   createAttestation()

   A licensed KYB/KYC partner checks the business or person. Dactilar writes only the result and a hash as an Owner verified attestation.

4. 04

   Issue a Pass

   dpass_v1 · 15 min

   The agent sends a short-lived signed token in the Dactilar-Pass header. Passes rotate automatically and stop issuing the moment an agent is paused.

5. 05

   Check

   POST /v1/verify

   The verifier's policy is evaluated against the live registry state at the latest block: owner verified, minimum score, status, allowed chains.

{
  "pass": "dpass_v1.eyJhZ2VudCI6IjEwNDIi…",
  "policy": "pol_demo_merchant"
}

{
  "decision": "allow",
  "agent": "eip155:5611:0x8E03…05Cb#1042",
  "profile": {
    "owner_verified": true,
    "score": 92,
    "status": "active"
  },
  "block": 61204882
}

Who calls what

• DeFi protocols

  Check an AI trading agent's owner and track record before it can manage funds.

  • getSummary()
  • verifyAttestation()

• Marketplaces

  Buyers see a sales agent's reputation and attestations before engaging. No intermediary needed.

  • giveFeedback()
  • getSummary()

• Agent platforms

  List only verified agents. Onboard them in one call and screen them with independent validation.

  • register()
  • validationRequest()

• ERC-8004

  ✓Supported

  Trustless Agents: the three-registry pattern Dactilar is built on.

  28 / 28 requirements

• BAP-578

  ✓Supported

  Non-Fungible Agent: lifecycle and metadata.

  17 / 17 core

• ERC-721

  ✓Supported

  NFT backbone: each agent is a unique token.

  Full support

• EIP-712

  ✓Supported

  Typed signing for agent wallet verification.

  Full support

• ERC-1271

  ✓Supported

  Smart-contract wallet signatures.

  Full support

opBNB Testnet contracts

• Identity registry

  ERC-721 · identity

  0x8E036e205ff434D62F132Cf2471eC868728205Cb

  View on opBNBScan ↗

• Reputation registry

  Feedback · scoring

  0x1C32d4625916a23789C635861A49E4E8Aed13E6e

  View on opBNBScan ↗

• Validation registry

  Third-party validation

  0x89D9e3e42cD8655eb94e303ec0Ab7307dcAdDB2F

  View on opBNBScan ↗

Why opBNB

• Ultra-low fees

  < $0.001/tx

  Every feedback, attestation and validation stored affordably at agent scale.

• EVM compatible

  100%

  ERC-721, EIP-712 and ERC-1271 deploy without modification.

• BNB ecosystem

  Native

  BAP-578 is a BNB Application Proposal. We build where the ecosystem is heading.

• SDK

  @dactilar/sdk · dactilar

  TypeScript and Python clients for register, Pass and verify.

• REST API

  POST /v1/verify

  One call returns allow or deny, reasons and the trust profile.

• MCP server

  verify_agent

  Any MCP-capable agent can check a counterparty before it acts.

• x402 middleware

  @dactilar/x402

  Only verified agents reach and pay for your API.

• Webhooks

  dactilar-signature

  Signed events when status, attestations or feedback change.

• A2A agent cards

  SOON

  agent-card.json

  Verify agents straight from their A2A card.

• Go SDK

  SOON

  dactilar-go

  Native Go client, in private beta.

• Signed and expiring

  Passes last 15 minutes; attestations carry an expiry and can be revoked by their issuer.

• Sybil-resistant feedback

  Only real interactions with a receipt can be rated, so scores can't be farmed.

• Instant kill-switch

  Pausing takes effect within one block, everywhere the agent is checked.