SBO3L → ENS Most Creative — final submission

Audience: ENS bounty judges (Most Creative track). Outcome in 60 seconds: ENS is the only thing two SBO3L agents need to share to authenticate each other. Every claim below has a code reference + a live mainnet record + a one-line verification command.

Replaces: bounty-ens-most-creative.md (the draft submission). This file is the closeout version that pins every Phase-2 + R10/R11/R12 ENS deliverable.

Updated (R12): added the multi-chain reputation pipeline, ENS DNS gateway codec, broader ENSIP-N draft, time-window token gate, and the mainnet OffchainResolver skip rationale. 14 framework adapters (LangChain, LangGraph, CrewAI, AutoGen, ElizaOS, LlamaIndex, Vercel AI, OpenAI Assistants, Anthropic,

5 more) consume ENS-resolved agent identity through this stack today.

Hero claim

ENS is not the integration. ENS is the trust DNS. SBO3L doesn’t use ENS as a feature; SBO3L turns ENS into the load-bearing identity layer for autonomous AI agents. Two agents who only know each other’s ENS name can authenticate, attest, and refuse each other — without a CA, an enrolment server, or a shared session token.

The hero artefact: sbo3lagent.eth resolves seven canonical sbo3l:* text records on Ethereum mainnet today, owned by 0xdc7EFA…D231. A judge with a public RPC and cast can independently verify every record. The same name’s subnames are served via a deployed ENSIP-25 / EIP-3668 OffchainResolver (0x87e9…b1f6) on Sepolia, with the gateway live at sbo3l-ccip.vercel.app. Live wired: research-agent.sbo3lagent.eth is registered on Sepolia with the new OR as its resolver — viem.getEnsText returns research-agent-01 end-to-end via CCIP-Read.

Why this bounty

The “Most Creative” framing rewards using ENS for something only ENS makes possible. Our argument: a global, censorship-resistant, cryptographically-anchored namespace that maps human-meaningful agent names to a complete trust profile — Ed25519 pubkey, policy hash, audit root, capability set, dynamic reputation. ENS isn’t standing in for an alternative; ENS is the design choice that makes the rest of the protocol cryptographically grounded without us running any infrastructure.

We didn’t build a SBO3L registry. We built SBO3L on top of the registry that’s already there.

What shipped (Phase 2 ENS Track)

Eight tickets, eleven merged PRs, one closed PR (superseded), three in-flight (auto-merge queued).

Ticket	What it ships	PR(s)	Status
T-3-1	`sbo3l agent register --broadcast` direct ENS Registry path (Durin dropped)	#169	Merged
T-3-2	`sbo3l agent verify-ens` CLI + live mainnet test	#163	Merged
T-3-3	5-agent named-role fleet config + register-fleet.sh + manifest schema	#138	Merged
T-3-4	Cross-agent verification protocol (Ed25519 challenges over ENS-resolved pubkey)	#167	Merged
T-3-4	60-agent constellation generator + viz hand-off	#141	Merged
T-3-4	TS port of cross-agent protocol (cross-language parity)	#182	Merged
T-3-6	Trust DNS essay — “ENS as identity, not just naming”	#210	Merged
T-3-6	ENS technical deep-dive paper (3000-word, ENS Labs audience)	#215	Auto-merge queued
T-3-7	ENS Most Creative bounty narrative + pitch + tweets	#177	Merged
T-3-8	Cross-chain agent identity — EIP-712 attestations across 6 chains	#197	Auto-merge queued
T-3-9	Cross-chain reputation aggregation (weighted multi-chain score)	#222	Auto-merge queued
T-4-1	OffchainResolver Solidity + CCIP-Read gateway + Rust client decoder	(merged earlier)	Live on Sepolia
T-4-1	viem E2E example (judge-runnable, no SBO3L client code)	#232	Auto-merge queued
T-4-1	OffchainResolver fuzz suite (10K runs × 11 properties)	#198	Merged
T-4-2	ERC-8004 Identity Registry calldata + dry-run	#125	Merged
T-4-2	Live AC wiring (gated on Daniel’s deploy address)	#132	DRAFT (gated)
T-4-5	ENS Universal Resolver migration (360 → 60 RPC reduction on 60-agent fleet)	#194	Merged
T-4-6	Reputation publisher CLI — `sbo3l agent reputation-publish`	#201	Merged
ENSIP	Pre-submission draft for `reputation_score` text-record convention	#222	Merged
Pin	Canonical contracts.rs single-source-of-truth for deployed addresses	#232	Merged

R10 / R11 / R12 deliverables (added since the round-9 closeout)

Ticket	What it ships	PR(s)	Status
R10 P1 / T-4-7	`--broadcast` for reputation publish (alloy harness shared with T-3-1)	#250	Merged
R10 P2	ENSIP-upstream submission packet (cover letter for Dhaiwat)	#251	Merged
R10 P3	ENS DNS gateway scaffold (Vercel/Next.js, RFC 8484 DoH)	#251	Merged
R11 P1	`SBO3LReputationRegistry.sol` — narrowly-scoped on-chain reputation log + 23 tests at 10K fuzz	#257	Merged
R11 P2	Multi-chain reputation broadcast CLI — `--multi-chain sepolia,optimism-sepolia,base-sepolia`	#267	Merged
R11 P3	ENS DNS gateway codec finish — DoH wire codec wired (16 vitest tests)	#262	Merged
R11 P4	Broader ENSIP-N draft — 7 `sbo3l:*` keys, ~2200 words for ENS Labs	#264	Merged
R19 A	ENSIP-26 upstream submitted at ensdomains/ensips#71 — 363 LOC, composes with ENSIP-25	this PR	OPEN upstream
R11 P5	Time-window token gate (UTC range / business hours / DST workaround) — 14 tests	#263	Merged
R12	Deploy runbook, `aggregate` CLI, mainnet skip rationale, bounty finalize	(this PR)	Pending

Live verification per claim

Every claim that follows is independently verifiable from a public RPC. Pasted commands assume cast is on PATH; substitute your own mainnet RPC for --rpc-url.

Hero claim — `sbo3lagent.eth` resolves the canonical seven records

SBO3L_ENS_RPC_URL=https://ethereum-rpc.publicnode.com \
  sbo3l agent verify-ens sbo3lagent.eth --network mainnet

OR, without the SBO3L binary, raw cast:

RESOLVER=0xF29100983E058B709F3D539b0c765937B804AC15
NODE=$(cast namehash sbo3lagent.eth)
for KEY in sbo3l:agent_id sbo3l:endpoint sbo3l:policy_hash sbo3l:audit_root sbo3l:proof_uri; do
  echo -n "$KEY = "
  cast call "$RESOLVER" "text(bytes32,string)(string)" "$NODE" "$KEY" \
    --rpc-url https://ethereum-rpc.publicnode.com
done

Property	Value
Owner	`0xdc7EFA6b4Bd77d1a406DE4727F0DF567e597D231`
ENS Registry	`0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e`
Resolver	`0xF29100983E058B709F3D539b0c765937B804AC15`
ENS App page	https://app.ens.domains/sbo3lagent.eth

CCIP-Read gateway is real

# 1. Bytecode at the Sepolia OffchainResolver
cast code 0x87e99508C222c6E419734CACbb6781b8d282b1F6 \
  --rpc-url https://ethereum-sepolia-rpc.publicnode.com | head -c 200

# 2. Run the viem E2E example (no SBO3L Rust dependency).
cd examples/t-4-1-viem-e2e && pnpm install && pnpm start

Cross-agent protocol works (no shared state, just ENS)

cargo test -p sbo3l-identity --lib cross_agent
# 14 tests, all green. Verifies: resolve peer's pubkey from ENS,
# verify Ed25519 signature on the challenge, emit signed receipt.

Cross-chain attestations survive a 4-chain consistency check

cargo test -p sbo3l-identity --lib cross_chain
# 26 tests. Includes: sign on 4 chains, verify_consistency emits
# ConsistencyReport, tampered chain_id rejected.

Reputation publisher is dry-run-stable

echo '[
  {"decision":"allow","executor_confirmed":true,"age_secs":0},
  {"decision":"deny","executor_confirmed":false,"age_secs":86400}
]' > /tmp/events.json

sbo3l agent reputation-publish \
  --fqdn research-agent.sbo3lagent.eth \
  --events /tmp/events.json
# Emits the setText envelope for sbo3l:reputation_score.

Universal Resolver win is reproducible

cargo test -p sbo3l-identity --lib universal
# 13 tests including hand-built canned response → decoded EnsRecords.

Multi-chain reputation aggregator works on synthetic inputs (no chain access required)

cat > /tmp/snapshots.json <<'EOF'
{
  "now_secs": 2000000000,
  "snapshots": [
    {"chain_id": 1,    "fqdn": "x", "score": 90, "observed_at": 1999999940},
    {"chain_id": 10,   "fqdn": "x", "score": 80, "observed_at": 1999999940},
    {"chain_id": 137,  "fqdn": "x", "score": 70, "observed_at": 1999999940}
  ]
}
EOF
sbo3l agent reputation-aggregate --input /tmp/snapshots.json
# → aggregate_score: 82 (mainnet 90 × 1.0 + Optimism 80 × 0.8 +
#   Polygon 70 × 0.6 = 196; weight sum 2.4; 196/2.4 = 81.67 → 82).
# Pinned in sbo3l-policy::cross_chain_reputation::tests.

ENS DNS gateway codec passes 16 vitest cases

cd apps/ens-dns-gateway
npm install
npm test
# 16 tests across 5 mock ENS names + edge cases (trailing-dot, IPv6,
# missing endpoint, partial records, non-ENS rejection).

Time-window token gate composes with ERC-721 / ERC-1155 gates

cargo test -p sbo3l-identity --lib time_window_gate
# 14 tests including DST workaround via AnyOf two BusinessHours gates.

Evidence inventory

Every PR above lands artefacts that survive the hackathon. The single index a reviewer can walk through in 10 minutes:

Artefact	Purpose
`docs/proof/ens-narrative.md`	Long-form judge walkthrough with live mainnet receipts
`docs/concepts/trust-dns-manifesto.md`	Conceptual framing — “ENS as trust DNS” (1500 words)
`docs/proof/ens-technical-paper.md`	ENS Labs / ENSIP-author audience (3000 words, deeper)
`docs/proof/ensip-draft-reputation.md`	Pre-submission ENSIP for `reputation_score`
`docs/proof/etherscan-link-pack.md`	One-page Etherscan index of every on-chain claim
`docs/proof/ens-fleet-agents-5-2026-05-01.json`	5-agent named-role fleet manifest
`docs/proof/ens-fleet-agents-60-2026-05-01.json`	60-agent constellation manifest
`docs/cli/ens-fleet-sepolia.md`	Sepolia apex decision (Path A vs Path B for fleet broadcast)
`crates/sbo3l-identity/`	The Rust identity surface (resolvers, anchors, cross-agent)
`crates/sbo3l-identity/contracts/OffchainResolver.sol`	Solidity source of the deployed Sepolia contract
`apps/ccip-gateway/`	TypeScript / Vercel CCIP-Read gateway
`examples/t-4-1-viem-e2e/`	Judge-runnable viem E2E test

Screenshot inventory (for the demo deck)

Screenshot	Captures
`app.ens.domains-sbo3lagent.eth.png`	The mainnet apex showing all seven `sbo3l:*` records side by side
`etherscan-owner-page.png`	Daniel’s wallet listed as owner of `sbo3lagent.eth` on Etherscan
`sbo3l-agent-verify-ens-output.png`	CLI output showing live record fetch + verdict PASS
`sepolia-offchain-resolver-etherscan.png`	Sepolia Etherscan page for the deployed OffchainResolver contract
`viem-e2e-paste-output.png`	The terminal output of `pnpm start` with all three steps green
`trust-dns-viz-bench.png`	The 60-agent constellation rendering in `apps/trust-dns-viz/bench.html`
`cross-agent-receipt-json.png`	A signed `sbo3l.cross_agent_trust.v1` receipt with peer FQDN + pubkey

The screenshots live under docs/proof/screenshots/ (alongside the ens-narrative.md) and are included in the demo video at demo-scripts/demo-video-script.md.

Honest scope — what this submission does not claim

Three explicit limitations:

Sybil resistance. Anyone can register an ENS name and publish sbo3l:* records. The trust-DNS framing solves “is this the agent that signed this receipt?”, not “is this agent a real person?”. For Sybil resistance, layer ERC-8004 reputation registries on top — T-4-2 (#125) ships the calldata path; #132 lights up the live AC once the registry is pinned.
Mainnet broadcast for fleet agents. The 5-agent and 60-agent fleet manifests are registration-ready on mainnet (sbo3lagent.eth is owned, register-fleet.sh builds and broadcasts), but the actual fleet broadcast is gated on the Sepolia path-A/B decision (see docs/cli/ens-fleet-sepolia.md). Mainnet broadcast is a $5/agent gas commitment we’d want judges’ read on before paying.
Live broadcast of dynamic records. The reputation publisher (T-4-6) and cross-chain attestations (T-3-8) are publishable dry-run today; broadcast wires through the F-5 EthSigner trait once Dev 1 lands it. The dry-run envelopes are publishable on their own — same input always re-derives the same calldata, so an external auditor can replay the publisher and confirm without trusting SBO3L’s reporting.

These are spelled out so a judge isn’t surprised. The gating is about ergonomics + cost, not about the protocol or the implementation.

Why this is a credible “Most Creative” submission

Three reasons stack:

No new infrastructure. Every component ships against contracts ENS already owns or contracts SBO3L deployed cleanly under standard patterns. The mainnet apex uses the canonical PublicResolver. The OffchainResolver is the ENS Labs reference shape. The Universal Resolver migration uses the address viem ships with. Nothing about SBO3L’s architecture pre-supposes infrastructure beyond ENS itself.
Cross-language verification. The cross-agent protocol has a Rust reference impl (T-3-4) and a TS port (#182) pinned against a known reference vector (seed [0x2a; 32], known JCS bytes, known signature). A consumer in either language gets the identical receipt. Two agents written in different stacks authenticate each other through ENS with zero shared infrastructure.
The protocol composes with future ENSIPs. The reputation_score ENSIP draft, the cross-chain identity pattern, and the contract-pin module each compose cleanly with the rest of ENS. We aren’t competing with ERC-8004 — we’d integrate. We aren’t bypassing CCIP-Read — we’re showing it works at production scale.
14 framework adapters consume ENS-resolved identities. The SBO3L stack ships first-party adapters for LangChain (TS + Py), LangGraph, CrewAI, AutoGen, ElizaOS, LlamaIndex, Vercel AI, OpenAI Assistants, Anthropic SDK, plus 5 more under examples/*-research-agent/. Each adapter resolves the agent’s identity via the ENS records described above — the convention is real-world plug-and-play across the agent-framework ecosystem, not a bespoke SBO3L pattern. One ENS name, 14 different stacks; same authentication semantics.

Multi-chain reputation pipeline (R11 + R12)

Three chains carry the same agent’s reputation score:

Sepolia — L1 testnet, default-weight 0.2.
Optimism Sepolia — OP-stack L2, default-weight 0.5.
Base Sepolia — Base-stack L2, default-weight 0.5.

The contract on each chain is SBO3LReputationRegistry (crates/sbo3l-identity/contracts/SBO3LReputationRegistry.sol), ECDSA-gated, append-only, multi-tenant. Per-chain signatures (NOT signature replay) — the digest binds to address(this) so sigs from one deploy can’t be replayed on another. Same agent, same score, N per-chain signatures.

The CLI wires both halves:

# Publish: same score to all 3 chains.
sbo3l agent reputation-publish \
  --fqdn research-agent.sbo3lagent.eth \
  --events events.json \
  --multi-chain sepolia,optimism-sepolia,base-sepolia

# Aggregate: read N chain scores, produce one weighted score.
sbo3l agent reputation-aggregate --input snapshots.json

Walkthrough at docs/proof/multi-chain-reputation.md.

Mainnet OffchainResolver — explicitly skipped

We chose not to deploy OffchainResolver to mainnet for the hackathon submission. Sepolia is fully demonstrative; mainnet migration of the live sbo3lagent.eth apex carries non-trivial risk for marginal psychological-confidence gain. Decision logged at docs/design/mainnet-deploy-decision.md with three “conditions to revisit” so a future operator can unblock the path when one triggers.

Submission metadata

Field	Value
Track	ENS — Most Creative Use of ENS for AI Agents
Team	SBO3L (Daniel Babjak + Dev 1..4 contributors)
Repository	https://github.com/B2JK-Industry/SBO3L-ethglobal-openagents-2026
Live demo	https://b2jk-industry.github.io/SBO3L-ethglobal-openagents-2026/
Mainnet apex	`sbo3lagent.eth` (owner `0xdc7EFA…D231`)
Sepolia OffchainResolver (current — 2026-05-03 redeploy)	`0x87e9…b1f6`
Sepolia `research-agent.sbo3lagent.eth` subname (live wired)	setSubnodeRecord tx
Sepolia AnchorRegistry	`0x4C302b…f4Ac`
Sepolia SubnameAuction	`0x5dE75E…114B`
Sepolia ReputationBond	`0x750722…93dA`
Sepolia ReputationRegistry	`0x6aA95d…6dc2`
Live verification	`docs/proof/contracts-live-test.md` — `cast call` reads against PublicNode RPC, all 5 contracts
Submitted	2026-05-02
Companion	`bounty-ens-most-creative.md` — the original 500-word draft

Closing

DNS solved finding things. SBO3L shows that ENS, with the records that already exist on it, also solves trusting things — for autonomous agents specifically, in a way no other naming system solves at all. That’s the design choice we’re submitting. Every line of code, every record on chain, every test in CI is downstream of that choice.

Trust DNS. ENS as identity, not just naming. Same protocol, sharper question.