Fistbump vs. ENS

ENS and Fistbump are often grouped together as "blockchain naming," but architecturally they are solving different problems. ENS is a wallet-and-content-addressing layer on Ethereum. Fistbump is a DNS root zone.

What ENS actually is

The Ethereum Name Service is a set of smart contracts on Ethereum that maps human-readable names (primarily ending in .eth) to wallet addresses, content hashes, and arbitrary key-value pairs. It was launched in 2017.

Under the hood, ENS uses a resolver pattern: a registry contract maps each name to a resolver contract, and the resolver contract holds the actual records. A name can store things like:

• An Ethereum address (so you can send ETH to alice.eth)
• A multi-coin address (BTC, SOL, etc.)
• A content hash (IPFS, Swarm, Arweave)
• A text record (avatar, email, URL)

Importantly, ENS does not store DNS resource records (A, AAAA, MX, NS, TLSA, CAA). Resolving alice.eth in a normal browser does not return an IP address — it requires an ENS-aware resolver or browser extension.

Summary table

1. Records: DNS vs. resolver

This is the foundational difference. ENS stores resolver records: mappings keyed by a type identifier (addr, text, contenthash) with values interpreted by the ENS ecosystem. Fistbump stores DNS resource records: A, AAAA, NS, MX, CNAME, TXT, TLSA, CAA, DS, and glue records.

The consequence is that a Fistbump name is immediately addressable by anything that speaks DNS — web browsers, email servers, SSH clients, CDN providers, certificate validators. An ENS name needs to be wrapped in a layer that understands resolver records and maps them to whatever protocol is asking.

ENS has added DNSSEC-import support so that ICANN-TLD DNS records can be bridged into ENS, but this is fundamentally the opposite direction from Fistbump: ENS treats DNS as an external data source, while Fistbump is a DNS implementation.

2. Resolution path

Resolving alice.eth in a standard browser fails. The name is not in any DNS hierarchy that the OS stub resolver, the recursive resolver, or the TLD server know about. Resolution requires either:

• A browser extension (MetaMask, for example)
• A browser with native ENS support (Brave, Opera)
• A DNS-over-HTTPS service that reads ENS

Fistbump resolves through any fbd full node. The node includes a built-in authoritative DNS server (default mainnet port 32870) that answers queries from on-chain state. Point your system resolver or a recursive resolver at a Fistbump node and Fistbump names become indistinguishable from ICANN names.

3. TLD vs. subdomain

ENS names ending in .eth are not top-level domains — they are subdomains of .eth, which itself is registered nowhere in the ICANN hierarchy. This works inside the ENS ecosystem but does not interact with global DNS.

Fistbump registers true top-level domains. Any name (subject to ICANN reservations at genesis) can be registered as a TLD. A name like fistbump is a root-level name, resolvable as example.fistbump if the owner enables subdomains.

Fistbump also supports on-chain subdomains with independent ownership, so you can register shop.example.fistbump as its own chain-level name with its own auction history and renewal lifecycle.

4. Gas and fees

Every ENS operation — registration, renewal, record update, transfer — is an Ethereum transaction and costs gas. Gas prices are volatile: updating a single record has cost anywhere from cents to tens of dollars depending on Ethereum congestion. This is a structural property of ENS, not an implementation detail.

Fistbump transactions pay network fees denominated in bumps (1 FBC = 1,000,000 bumps). Because Fistbump does not run a general-purpose VM, transaction validation is fast and cheap, and typical name operations cost a negligible amount of FBC in network fees.

5. Consensus and security

ENS inherits Ethereum's consensus. Its security is bounded by the security of the Ethereum validator set and the correctness of the ENS contracts. A bug in an ENS contract or a consensus change in Ethereum directly affects ENS.

Fistbump has its own consensus: memory-hard proof of work (Balloon Hashing) with a 2-minute block time. Name state is stored in an Urkel tree whose root is committed in every block header, allowing light clients to verify name ownership and records without downloading the full chain.

Neither security model is strictly superior, but they are different: ENS is as secure as Ethereum; Fistbump is as secure as whatever hash rate secures its own chain.

6. Governance

ENS has an on-chain governance process via the ENS DAO and the ENS governance token (airdropped in 2021). Protocol changes are proposed and voted on by token holders.

Fistbump has no governance token and no on-chain governance mechanism. Protocol changes require a hard fork. The development fund is disbursed from a multisig controlled by core contributors — a governance parameter but not a consensus-critical one. The signer set and threshold can change without a fork; the consensus rules cannot.

Which should you use?

Use ENS if you want:

• A human-readable handle for your Ethereum wallet
• Integration with the existing Ethereum and DApp ecosystem
• A content-addressing layer pointing at IPFS or similar

Use Fistbump if you want:

• A real DNS name that resolves in any browser
• Full TLDs (not .eth subdomains)
• Certificate issuance via DANE without a CA
• Predictable, tiny operation costs instead of Ethereum gas
• A naming system that runs independently of any other blockchain