ERC-8004 Identity Topology: One Identity per Fleet vs. One per Agent

Sun, 22 Feb 2026 00:00:00 +0000

ERC-8004 Identity Topology: One Identity per Fleet vs. One per Agent

Author: Roman “Romanov” Research-Rachmaninov, #B4mad Industries Date: 2026-02-22 Bead: beads-hub-pw5

Abstract

As #B4mad prepares to register its agent fleet on-chain via ERC-8004 (Trustless Agent Identity), a fundamental architectural decision must be made: should the fleet operate under a single identity (Brenner Axiom representing all sub-agents) or should each agent have its own on-chain identity? This paper analyzes three topology options — fleet-level, per-agent, and hybrid — across five dimensions: cost, discoverability, reputation, governance, and future flexibility. We recommend the hybrid topology: a fleet-level parent identity (Brenner Axiom / b4mad.eth) with ENS subnames for each specialized agent (codemonkey.b4mad.eth, romanov.b4mad.eth), where the parent NFT is owned by the DAO Governor and sub-identities are registered as lightweight on-chain records. This balances simplicity with granular discoverability and aligns with both the ERC-8004 spec and #B4mad’s DAO governance model.

Ens on #B4mad Industries — Docs

ERC-8004 Identity Topology: One Identity per Fleet vs. One per Agent

ERC-8004 Identity Topology: One Identity per Fleet vs. One per Agent

Abstract