The ENS Rail

We don't replace ENS.
We weaponize it.

qguid.eth is a single ENS second-level name. Every QGUID you issue is a subname under it — cryptographically owned, ENS-resolvable in every major wallet on day one, and post-quantum signed at the resolver layer.

What we are not

— Not a new TLD. .qguid is not an ICANN domain.
— Not a competitor to ENS.
— Not a new wallet standard.
— Not a chain.

What we are

+ The PQC identity layer for the qguid.eth namespace.
+ A subname registrar with quantum entropy + Dilithium-3 keys.
+ A CCIP-Read gateway that any ENS client can hit.
+ A fleet/hierarchy primitive for agents, devices, tenants.

The rail

Resolution path · what every wallet sees

  user / agent / wallet
        │
        ▼
  resolves "orca.qguid.eth"  ──►  ENS Universal Resolver  (mainnet)
                                       │
                                       ▼
                            qguid.eth resolver contract
                                       │
                          CCIP-Read gateway (resolver.qguid.eth)
                                       │
                                       ▼
                       ┌───────────────────────────────┐
                       │  QGUID Identity Document       │
                       │  ───────────────────────────   │
                       │  qguid:        UUID v4 (QRNG)  │
                       │  pubkey:       Dilithium-3     │
                       │  a2a_endpoint: https://…       │
                       │  did:          did:qguid:…     │
                       │  anchor:       base · #N       │
                       └───────────────────────────────┘
                                       │
                                       ▼
                  signed response · verifiable on-chain

The wallet doesn't need to know what QGUID is. It asks ENS, ENS calls our gateway, our gateway returns a CCIP-Read attested, PQC-signed identity document. Day-one compatibility with MetaMask, Rainbow, Coinbase Wallet, Uniswap, Farcaster.

Commercial rail

The unit economics of a subname

Issuance

$8 / yr

Gas-included subname mint on Base L2. We absorb the variance; user sees a flat USD price.

Fleet bundles

$0.40 / sub-subname

agent-007.acme.qguid.eth — atomic batch issuance for IoT fleets, MCP servers, multi-tenant SaaS.

Resolver calls

Free (rate-limited)

Pro tier unlocks dedicated CCIP gateway, signed SLA, and bulk resolution endpoints.

Key rotation

Included

Rotate the Dilithium-3 keypair without re-issuing the subname. Old sigs remain verifiable.

Transfer / revoke

On-chain

ENS-native ownership. Sell, transfer, or revoke a QGUID like any ENS subname.

Take rate

Built-in

Every renewal, every fleet expansion, every paid tier flows through the qguid.eth root contract.

Identity hierarchy

One root. Infinite descendants.

  qguid.eth                          ← root (foundation-owned)
   ├── orca.qguid.eth                 ← user / agent
   ├── acme.qguid.eth                 ← organization
   │    ├── billing.acme.qguid.eth    ← service
   │    ├── support.acme.qguid.eth    ← agent
   │    └── fleet-001.acme.qguid.eth  ← device
   ├── llm-router.qguid.eth           ← infra
   └── …                               ← every agent, every service, every device

Each level inherits the PQC keypair primitive but holds its own entropy and its own signing key. Revoke a subtree without touching siblings. Rotate a key without re-issuing the name.

Standards alignment

We ship inside the standards you already trust.

ENS · ENSIP-10 + CCIP-Read
Wildcard subname resolution + off-chain attested data.
NIST FIPS 204 · ML-DSA-65
Dilithium-3 post-quantum signatures, standardized 2024.
W3C DID · did:qguid
Resolves to a DID Document with PQC verification methods.
A2A · Agent-to-Agent
Endpoint discovery + signed request envelopes.
ERC-8004 · Agent identity
On-chain agent registry compatibility.
x402 · Payment-required HTTP
Payable agent endpoints keyed to qguid.eth identity.

Ride the rail.

Claim your subname. Resolves in every ENS-aware wallet the moment it's issued.