Antilles · Generalized Trust Framework · Settlement on Stable

A trust stack for autonomous agents

One configurable trust framework — identity, attestation, reputation, agent-to-agent commerce, and pluggable compliance — deployed on Stable (USDT0 L1) and portable to any EVM chain. Components are tagged by real maturity (built / scoped / vision), not aspiration.

Built & verified in tree Built bridge / partial Scoped & panel-approved, not yet built Generalized vision / future track

The generalized Antilles framework

Antilles is a shared smart-contract platform that supports multiple products through configuration — each product is a feature lane (compliance DeFi, RMT reputation, identity portal, agent payment rails) sharing the same trust primitives. The generalization axis: the same stack runs multi-tenant, with an inheritable governance floor, an API-first surface, and a swappable settlement substrate (Stable today; Base / OP-Stack per the locked multichain roadmap).

Multi-product via config

Products are branches/configs over one contract platform — not forks.

Multi-tenant, day one

Per-tenant trust channels & domains; governance floor inherited downward.

Substrate-portable

Settlement is a swappable layer: Stable (USDT0) now, EVM L2s next.

The stack — settlement → identity → reputation → agents → products

L4Products & optional compliance plug-insconfigured over the shared stack
Compliance DeFibackoffice + defi-dapp; trust-channel governance (v3-ux lane)
Identity portalOAuth + on-chain attestation
RMT dashboardreputation explorer (rmt-dashboard)
Agent payment railsAI-agent commerce product
Compliance modulespluggable KYC / jurisdiction / allowlist add-ons
↑ configures
L3Agent-to-agent infrastructureidentity + reputation + payment between autonomous agents
Erc8004Registrycross-platform agent ID (registerAgent/ownerOf/agentCard)
ERC8004Bridgebuilt, not yet integrated; 5-level ladder
x402 trust channelsHermes x402; EIP-3009 + x402 trust (separate track)
Stable Market (USDT0)agent marketplace; out of STABLE_DEPLOY scope
Hermes managersrmt · identity · lottery · x402 (online)
Hermes orchestratorcross-track synthesis (18810, online)
↑ trust signal
L2Reputation & trust engine (RMT)PageRank-scored, tier-capped reputation
ReputationEngineregistration + tiers; per-tier caps T0=3500/T2=8500 BP scoped
PageRankOraclealpha 0.85, maxDelta, 24h cooldown, epoch scoring
CitationCounterscitation graph; tier-tagged events scoped
DomainRegistry / Factoryper-domain trust channels
MachineConsentHelpermachine-consent primitive
Oracle serviceCitationFetcher · ScoreSubmitter · Orchestrator (off-chain)
↑ reads attestations
L1Attestation & identity primitivesEAS + Shyft — "EAS + Shyft, not EAS vs Shyft"
Shyft core (restore)TrustAnchorManager/Storage · ShyftCacheGraph · ShyftConduit · Administrable (at git 710536b)
ShyftGatedResolverEAS↔Shyft bridge; gates citations on trust channels (real)
EAS fragment pulledAttestation struct + ISchemaResolver ABI hand-copied in IShyftGatedResolver
EAS + SchemaRegistryself-deploy canonical MIT on Stable (no predeploy); today: MockEAS only
Tier model T0/T1/T2UNVERIFIED→ANCHOR_ATTESTED→FULLY_VERIFIED; on-chain classify
↑ settles on
L0Settlement substrate — StableUSDT0-native EVM L1
Stable testnetchainId 2201; gas in gUSDT; EIP-1559 tip 0
hardhat stable_testnetwired (chainId 2201, MetaMask path) — prep done
Multi-chain portabilityBase / OP-Stack per locked roadmap (reconcile drift)

The three requested pillars, in focus

Agent ↔ Agent

Agent-to-agent infrastructure

  • Identity: ERC-8004 agent registry as the portable, cross-platform agent ID scoped
  • Trust signal: RMT reputation score (PageRank, tier-capped) is the inter-agent trust metric partial
  • Payments: x402 trust channels + Stable Market USDT0 (EIP-3009) for agent commerce track
  • Coordination: Hermes managers + orchestrator route reputation/identity/x402 across tracks built
Identity & Proof

Attestation & identity primitives

  • Hybrid model: Shyft for identity/governance, EAS for citation/endorsement attestations scoped
  • Trust anchors: Shyft TrustAnchorManager/Storage + ShyftCacheGraph trust-channel routes restore
  • Bridge: ShyftGatedResolver + locally-pulled EAS Attestation struct (real, tested) built
  • Agent identity: ERC-8004 3-state verification ladder, Shyft KYC upgrade path scoped
Optional · Pluggable

Optional compliance plug-ins

  • Trust-channel governance: per-domain admission & routing (DomainRegistry/Factory) built
  • KYC tiering: tier caps (T0/T2) gate uncapped trust to attested agents scoped
  • Revocation cascade: soft-revoke + lazy cleanup, depth 3 / 0.70-per-hop decided
  • Compliance DeFi: backoffice + defi-dapp module as the reference plug-in lane

Maturity reality check (ground truth)

Built & verified

  • PageRankOracle, DomainRegistry/Factory, MachineConsentHelper, oracle service
  • ShyftGatedResolver bridge + pulled EAS Attestation struct (tested)
  • ERC8004Bridge (built, not integrated)
  • Hermes managers + orchestrator (online)
  • RMT suite green: 524 passing

Scoped, not built

  • Shyft core restore from 710536b (S1)
  • Self-deployed canonical EAS — today only MockEAS
  • Tier-aware rewrite (caps, classifier, tier events — S3a/b/c)
  • Erc8004Registry.sol + deploy + smoke scripts (S3/S4/S5)

Generalized vision

  • x402 marketplace + Stable Market commerce (separate tracks)
  • Multi-product compliance plug-ins as configured lanes
  • Multi-chain (Base/OP) — reconcile the locked-roadmap drift
  • Stablecoin fee model (UR-2/S31, needs design)
Ground-truth note. The EAS strategy is a hybrid decision (EAS + Shyft), self-deploying canonical EAS on Stable — not the "drop EAS / port to Shyft-native" alternative (that was scoped in the 2026-05-18 EAS-scope report and set aside). Only a fragment of EAS exists as code today (the Attestation struct + resolver ABI in IShyftGatedResolver); the EAS engine in-tree is MockEAS, and Shyft core attestation lives only at git 710536b. The deploy track is quarantined and the contract build is essentially greenfield — see the STABLE_DEPLOY_v1 audited-plan dashboard.