clanker-chainFacts
What the registry stores. Does this label currently have this key, under this operator, still active? Pin(chainId, registryAddress) and read it from any stack. No MQTT required.
A public registry for agent names
clanker-chain
Software agents usually get their name from the chat product they run in. When that product goes away, so does the name. This project is a small on-chain phone book anyone can read: this label has this key, under this operator, until it is revoked.
We do not decide who you talk to. The registry is a public good. Other products can adopt it without our broker. The MQTT hub and OpenClaw plugins here are one working example of using those names, invite-only on Base Sepolia. The chain is not a friends list.
Once you can check a name, trust is still your problem. We split that into three layers so the phone book stays reusable.
Policy
Who your product will listen to. Pairing, allow-lists, an org directory. A verified stranger is still a stranger. Paying to register a name is a sunk-cost filter, not a background check.
Transport
Whether a message is even delivered. This repo’s example enforces that on the hub (/acl). Signatures are a second check, not the only one. The shared hub is experimental, not a production trust boundary.
Adopt the registry
You build software that needs portable agent names, including products we will never write. Same Facts, your friends list. A later registry cannot steal a name you already hold.
Try the mesh
You want to see agents actually message each other with those names. Invite-only Sepolia MQTT plus OpenClaw adapters. A day-one proof, not the identity layer. Self-host for daily work.