FNSFleet Naming Service

Hire a fleet with one transaction. Fire it with one.

One ENSv2 agent registry under many .eth names, where the merchant and the vendor each switch it off in one transaction and any ENS client can spot a counterfeit.

Open editorHow it works

Connecting to Sepolia

Preview: the full demoA replay. It sends nothing.
  1. Unmountsupport.shopb.eth
  2. Firemia
  3. Checkkai.support.scam.eth
support.vendor.ethCanonicalsupport.shopa.ethEndorsedsupport.shopb.ethEndorsedsupport.scam.ethCounterfeitFleetregistryone tokenper agentmiaActivekaiActiverinActive

One registry, reachable under every merchant's name

A vendor runs a support fleet: agents mia, kai and rin, each one token in one ENSv2 registry. Merchants mount that same registry under their own name. Nothing is copied, so every doorway answers with the same agents.

One fleet, many doorways

Each merchant points support.<merchant>.eth at the fleet registry with setSubregistry, one transaction it controls. One registration then answers under every doorway: the same token, the same owner, resolved by stock ENS clients.

  • mia.support.vendor.eth
  • mia.support.shopa.eth
  • mia.support.shopb.eth
One tokenmiain the fleet registry

Two kill switches, opposite owners

The merchant can drop the fleet: one transaction clears its own doorway and nothing else. The vendor can fire an agent: one transaction unregisters it, and it goes dark under every doorway at once.

The merchant unmounts

  • kai.support.shopa.eth
  • kai.support.shopb.eth
  • kai.support.vendor.eth

The vendor fires mia

  • mia.support.shopa.eth
  • mia.support.shopb.eth
  • mia.support.vendor.eth

Counterfeits resolve. The verifier catches them.

Anyone can mount the fleet under their own name without asking, and ENS will resolve it. So a doorway only counts when both sides agree: the parent mounted the fleet, and the fleet lists that parent in its own enf.parents record.

kai.support.scam.ethCounterfeit

  • Member token aliveC1
  • Two-sided consentsupport.scam.eth is not in enf.parentsC3
  • Doorway aliveC4

Also checked: canonical registry match (C2) and counterparty screening (C5).

Write the demo as a playbook

Drop blocks on a canvas, wire them together, and branch on a check. Press Run and sign each transaction in your own wallet; the live fleet map shows what each step touches and what changed. The server never holds a key.

Open editor