Namecoin forked Bitcoin's code to register names, not money

Inherited archive entry · retained from the earlier edition. Its factual, legal and policy claims have not all been reverified for 19 September 2026. Research scope.

A code fork aimed at names, not money

On 18 April 2011, a user posting as vinced announced a new blockchain built by reusing Bitcoin's own software: Namecoin. The post is explicit that this was 'a new blockchain, separate from the main Bitcoin chain,' with its own coin and its own transaction history. The stated purpose was not payments but a distributed alternative to parts of the domain name system, plus a namespace for personal identity records. Namecoin's own account now describes the project as 'the first fork of Bitcoin' and says it 'was first to implement merged mining' — mining Namecoin blocks with the same proof-of-work effort already spent on Bitcoin, rather than competing for a separate pool of hashing power.

What the registry actually enforces

The mechanism set out in the original announcement layers new transaction types — new, first-update and update — onto Bitcoin's format. Consensus rules reject any block containing two live claims to the same name, and a name expires after roughly 12,000 blocks unless its holder renews it. That is the whole guarantee: whoever holds the private key tied to a name controls the data attached to it, up to 520 bytes, and no other key can hold the same string at the same time. The Namecoin Core project still describes this today as recording 'arbitrary names (keys)' and attaching values that can carry email addresses, GPG keys, Bitcoin addresses or TLS fingerprints — a general-purpose key/value store secured by a blockchain, not a Bitcoin feature grafted onto DNS.

The boundary: registration is not verification

A registry enforced by consensus can guarantee uniqueness and continuity of possession. It cannot guarantee that a name means what a visitor assumes it means. Registering a name on Namecoin proves only that one key currently controls that string; it says nothing about the identity of the key-holder, the accuracy of the attached data, or whether any given piece of software resolves a .bit address correctly at all — resolution has always depended on separate, non-consensus tooling such as browser plugins and proxies. This is the distinction that recurs in every later blockchain-identity claim: the chain enforces exclusivity of a claim, not the truth of what is claimed. Namecoin's early date also meant it inherited none of the wallet support, liquidity or developer tooling that later forks built once reusing Bitcoin's code became routine, which is one editorial reason its registry model never displaced conventional DNS at scale.

Questions to carry forward

• Does a naming or identity system built on a chain verify anything beyond exclusive possession of a key?
• What software outside consensus has to run correctly before a registered name resolves to anything?
• Who is expected to notice an expiring registration and renew it before the claim lapses?

Namecoin's contribution was procedural rather than financial: it demonstrated that Bitcoin's validation rules could be repurposed for a different kind of record, and that mining security could be shared rather than duplicated. Reading it as a name system rather than a currency is the more useful frame, and it is also the more modest one.