LIVE · STABLE TESTNET · chainId 2201
Antilles / Shyft RMT stack — deployed & verified on-chain
Reputation + fee + attestation system, live on Stable testnet (native gas USDT0). 18 contracts, deployed fresh, independently verified.
Live proof (read fresh from rpc.testnet.stable.xyz):
chainId 2201 · block 59,324,748 · RMTToken.name() = "Reputational Merit Token" (RMT) · Resolver.reputationEngine() wired ✓ · deployer sent 77 txs · gas spent ~0.04 USDT0 · all 18 contracts return live bytecode ✓
What's deployed
Grouped by layer. Click any address to open it on Stablescan (testnet.stablescan.xyz).
① Attestation infra (Shyft core + identity)
③ RMT / oracle / citations
How it flows
A Trust Anchor attests an agent's identity (Shyft, USDT-fee → PaymentModule → FeeRouter split). Attested agents in a trust channel can be cited via the ShyftGatedResolver (EAS), which records into CitationCounters. The off-chain oracle reads citations → PageRank → ReputationEngine (tier-capped reputation).
What I did — the journey
- Built the new contracts (FeeRouter, ERC-8004 registry/bridge) + the phased deploy harness + the MachineConsentHelper auto-signer + the auto-co-signer governance. 5 cross-model CODE_REVIEW/AUDIT passes, real defects caught & fixed each round.
- Convergence audit 3/3 — Grok + Gemini + Codex all approve the hardened code.
- Fork dry-run against the real chain state → COMPLETE, gas measured tiny.
- Red-team (independent session) → testnet-safe, no critical/high; 4 findings hardened + re-verified.
- Funded: deployer + auto-co-signer from your seed (71 + 30 USDT0).
- Attempt 1 FAILED — caught live: a stale local-test ledger made the harness try to reuse 4 addresses that hold foreign contracts on Stable. It fail-closed (reverted) — no bad state shipped.
- Root cause fixed — the harness now verifies on-chain code is ours (codehash) before reusing, + binds the ledger to chainId.
- Attempt 2: fresh, clean, COMPLETE — all 18 contracts deployed + wired + the trust-channel route live (identity attestation working both directions).
- Independently verified on-chain (fresh reads above).
How to explore it yourself
Use Stablescan (blockscout is down right now):
testnet.stablescan.xyz
- See every deploy + call in one place: open the deployer address → Transactions tab (117 txs). The ones marked "Contract creation" are the deploys (one per contract); the rest are the wiring/setup calls (onboard anchor, set channel, wire fee path, register schema, attest…).
- Inspect any contract: click its address (above) → its page has Transactions, Contract (code), and Read/Write Contract tabs. Try Read Contract → reputationEngine on the Resolver, or name/symbol on RMTToken.
- The co-signer's confirmations: 0x7527A3… (the automated 2nd admin — 11 threshold-2 confirmation txs).
Deployer: 0xD26E5b… (77 txs)
Auto-co-signer: 0x7527A3… (11 confirmations)
Gas total: ~0.04 USDT0
Commit: e9a9301e