"The next AI economy will not be won by people with the most prompts. It will be won by people with the most defendable assets."

Sovereign identity for AI assets — ENS + Hedera Names.

Defendable AI Assets need an on-chain identity layer that survives vendor changes, brand mergers, and platform turnover. Swarm operates a portfolio of ENS names on Ethereum L1 and Hedera Names on the Hedera network — together they form the identity substrate every deed, every operator, and every receipt anchors against.

ENS portfolio (Ethereum L1)

• swarmandbee.eth — the firm identity.
• defendable.eth — the deed office and trust standard.
• microscalers.eth — the operator network. Sub-ENS allocation per qualified operator (e.g., <vendor>.microscalers.eth).
• swarmusdc.eth → 0xBDe2153C5799f4012a9fAF327e3421D1caB4Ea23 — the USDC settlement address. Ethereum L1, no L2.
• swarmgeo.eth, swarmgraph.eth, aiov.eth, proofofcompute.eth — product and brand surfaces.

Hedera Names

• swarm.hbar
• hive.hbar
• swarmandbee.hbar

Hedera operator 0.0.10291827 · anchor topic 0.0.10291838 for every defendable.eth deed.

How identity links to deeds

Every defendable.eth deed names: issuer (typically swarmandbee.eth today), operator(s) involved (sub-ENS under microscalers.eth), and verification anchors (Hedera HCS topic + IPFS CID). The chain proves who signed what, when, on what compute. If Swarm ever sub-licenses Defendable to franchise issuers, each one signs under their own <vendor>.defendable.eth sub-ENS — same standard, distributed issuance.

Why this matters

Procurement teams in regulated industries need to verify that the entity selling them an AI asset is who they say they are, that the asset matches what was signed, and that the deed can be enforced post-sale. ENS + Hedera Names + on-chain anchors makes that verifiable without trusting any single party — the spectator-verifiable property of the Defendable standard.