Namecoin (NMC): Satoshi’s First Altcoin and the Uncensorable .bit Revolution
The true story of the world’s first altcoin designed with Satoshi Nakamoto, and the pioneering quest for an uncensorable, decentralized .bit internet domain.

3-Minute Fast Briefing
- The ParadoxIn November 2010, the BitDNS thread exposed the paradox: names still answered to registries, but a second blockchain would split miners—who could allocate names without an owner?
- The Turning PointSatoshi proposed separate chains sharing hashing power; on April 18, 2011, vinced launched Namecoin, and merged mining activated at block 19200.
- The LegacyAs of August 24, 2026, the project FAQ says .bit is outside conventional DNS, while blockchain naming re-emerged on Ethereum when ENS launched in 2017—a chronology and editorial comparison, not descent.
Chronological Timeline
appamatto posts "BitDNS and Generalizing Bitcoin" from a November 14 IRC discussion, asking for authority-free naming.
Satoshi Nakamoto argues BitDNS should be its own chain borrowing Bitcoin's CPU power, with each network keeping its own fate.
A PGP-signed forum post launches a Bitcoin fork for names, aimed at a distributed TLD, possibly .bit.
Namecoin accepts its first AuxPOW block; the project dates production deployment to October 2011.
ENS's initial .eth registrar deploys to the Ethereum mainnet; blockchain naming re-emerges on smart contracts.
1. The Forum Thread That Asked Who Owns a Name
On November 15, 2010, a BitcoinTalk member writing as appamatto opened "BitDNS and Generalizing Bitcoin" after an IRC discussion held the day before. The opening post said earlier distributed-DNS attempts had not fully removed authority and proposed a Bitcoin-style clone for authority-free name allocation.[1]
The question was already in the air. Replies on the thread's first page pointed to Peter Sunde's separate decentralized-DNS effort, and among the early participants were Cdecker and Gavin Andresen. For this community, naming had become the sharpest test of whether proof-of-work could replace an institution.[1]
One problem, though, was admitted in the opening post itself: two chains mean split mining. Any given miner, appamatto warned, "can only generate for one at a time". The post said this would be especially dangerous as more Bitcoin-like applications were developed, because they would be vulnerable to attack early in their development. A naming chain launched alone would defend itself with a fraction of Bitcoin's power.[1]
2. Satoshi's Answer: Share the Work, Split the Chains
On December 9, 2010, Bitcoin's pseudonymous creator, Satoshi Nakamoto, answered the thread — not with code, but with the design argument later known as merged mining. His opening accepted the premise of separation and refused its cost, in a post timestamped 21:02 UTC.[2]
I think it would be possible for BitDNS to be a completely separate network and separate block chain, yet share CPU power with Bitcoin. The only overlap is to make it so miners can search for proof-of-work for both networks simultaneously.[2]— Satoshi Nakamoto, BitcoinTalk BitDNS thread, December 9, 2010
The mechanics were almost playful. Miners would subscribe to both networks in parallel and scan for hashes such that a single hit could solve both chains at once; an external miner could even combine work pulled from both programs. Satoshi framed the gain as collective: instead of fragmenting into networks that could gang up on one another, chains would share and augment each other's total CPU power — making small networks far safer to start.[2]
The next day, December 10, 2010, Satoshi closed the door on the simpler alternative: one chain carrying every use case. Each network, he argued, must stay usable on its own and free to set its own rules. A naming chain could tolerate data that payment-chain users would never accept. His conclusion was exact: "The networks need to have separate fates." Two sentences from that post still read like a design brief for a multichain world.[3]
Piling every proof-of-work quorum system in the world into one dataset doesn't scale.[3]— Satoshi Nakamoto, BitcoinTalk BitDNS thread, December 10, 2010
3. Namecoin Ships: vinced's Fork and the .bit Namespace
On April 18, 2011, a developer posting as vinced signed Namecoin onto the same forum with a PGP key. The project's lineage was declared in its first lines, and it ran straight through the BitDNS thread: this was not Satoshi's software, but software his discussion had inspired.[4]
Namecoin is a naming system based on bitcoin with a few modifications. It is inspired by the bitdns discussion and recent failures of the DNS.[4]— vinced, Namecoin launch announcement, BitcoinTalk
The announcement's quick facts describe a system still recognizable today: a new blockchain separate from Bitcoin's; name/value pairs stored in transactions; registration through dedicated transaction types — new, first-update, and update; and names that expire after 12,000 blocks unless renewed. The DNS namespace aimed at a distributed top-level domain, tentatively ".bit," and the code went straight to GitHub.[4]
The primary record draws a precise actor line. Satoshi discussed the separate-chain, shared-work design in December 2010; vinced implemented and announced Namecoin in April 2011. The launch post calls Namecoin a naming system based on Bitcoin and says it was inspired by the BitDNS discussion. Inspiration and implementation belong to different actors, and that distinction is the story.[4][2]
4. Block 19200: The Sketch Becomes Merged Mining
A newborn chain defends itself with newborn hashrate — exactly the risk the BitDNS thread had flagged. The answer, once built, was Satoshi's sketch made real. The Bitcoin Wiki's merged-mining specification identifies Namecoin block 19200 — hash d8a7c3e01e1e95bcee015e6fcc7583a2ca60b79e5a3aa0a171eddd344ada903d — as the first block that allowed AuxPOW authentication.[1][2][6]
Auxiliary proof-of-work, or AuxPOW, is the formal name. An auxiliary chain accepts a block whose own header misses its difficulty target, provided attached data proves the miner performed real work on a parent chain that does meet that target. The parent chain never needs to know its hashes are being borrowed.[6]
Namecoin's own documentation frames the milestone in production terms. It states that Satoshi Nakamoto first proposed the sidechain concept in 2010 and that Namecoin first deployed it in production in October 2011, with P2Pool (December 2011) and Liquid (October 2018) following in production. The project also notes merged mining can anchor to any SHA-256d parent chain, with Bitcoin merely the most common. Those are the project's claims about its own history.[5]
5. As of 2026: .bit Outside the DNS, ENS on Ethereum
A namecoin-core commit authored on August 17, 2026, merged the repository's auxpow branch, directly documenting project-code activity that month. As of August 24, 2026, the project's FAQ says its flagship .bit TLD is not part of the DNS. It says asking public DNS infrastructure to mirror Namecoin would probably be seen as hostile by IETF and ICANN, and that the project seeks a special-use listing like the one .onion holds. The commit proves repository activity, not chain liveness.[7][5]
The same FAQ is careful about what censorship resistance means. If ISPs resolved .bit on users' behalf, they "would be in a position to censor names without easy detection" — so the design favors resolution on the user's own machine. The FAQ therefore shows that removing the central registry does not remove every intermediary between a name and its reader.[5]
On May 4, 2017, six years after vinced's announcement, blockchain naming re-emerged on a different foundation: the Ethereum Name Service's initial .eth registrar was deployed to the Ethereum mainnet, as ENS's own ENSIP-2 specification records, with names allocated through Vickrey auctions intended to mitigate speculation and squatting.[8]
Nothing in ENS's founding record claims descent from Namecoin: ENSIP-2's prior-work section credits ENSIP-1, ERC-26, and a hash-registrar implementation, not .bit. CoinYQ's evidence-bounded editorial comparison places Satoshi's separate-chain/shared-work pattern beside ENSIP-2's later focus on adoption and network effects. It compares two design records; it does not claim that ENS descended from Namecoin.[8][2][3]
Key Takeaways for Investors & Builders
Separate chains can share security
Satoshi's 2010 reasoning — one dataset doesn't scale, and networks need separate fates — plus AuxPOW showed how a separate chain can reuse qualifying parent-chain work without sharing application data. Namecoin block 19200 was the first block to allow AuxPOW authentication.
Distribution decides a naming network
Technical priority is not distribution. As of August 24, 2026, Namecoin's FAQ says .bit is outside the DNS, while ENSIP-2 records ENS's 2017 deployment inside Ethereum and explicitly treats adoption and network effects as design concerns. Value infrastructure narratives by their paths to users; this is comparison, not causation.
Removing the registry is not removing power
A blockchain can delete the registrar, yet Namecoin's own FAQ shows who remains: ISPs, resolvers, and the politics of IETF and ICANN. Censorship resistance is an engineering posture maintained against named intermediaries, not a finished state that ships once.
Connected Stories in this Universe
Explore the chain reaction of historical breakthroughs, blunders, and legends.

Bancor (BNT): When 396,720 ETH Flooded the First AMM and Froze Ethereum
The invention of the first AMM, a record 396,720 ETH rush, and the day an ICO brought down the Ethereum network.
Read story →
ai16z to ElizaOS: How a $2.5 Billion Token Died but Its Code Survived
An AI VC parody named after a16z peaked near $2.5 billion in market cap — before its founder buried the token and saved the open-source code.
Read story →
A Billionaire's $50,000 Bitcoin Grant and the First AI Millionaire: The Wild Rise of GOAT
An AI bot, a billionaire's $50,000 Bitcoin grant, and the GOAT memecoin it never created — the verified story of Truth Terminal's paper millions.
Read story →Sources & References
- [1]Source 1: BitDNS and Generalizing Bitcoin — BitcoinTalk thread opening (Internet Archive)BitcoinTalk via Internet ArchiveAccessed 2026-08-24
- [2]Source 2: Satoshi Nakamoto, Re: BitDNS and Generalizing Bitcoin, December 9, 2010 — Satoshi Nakamoto InstituteSatoshi Nakamoto Institute · 2010-12-09Accessed 2026-08-24
- [3]Source 3: Satoshi Nakamoto, Re: BitDNS and Generalizing Bitcoin, December 10, 2010 — Satoshi Nakamoto InstituteSatoshi Nakamoto Institute · 2010-12-10Accessed 2026-08-24
- [4]Source 4: vinced, [announce] Namecoin — a distributed naming system based on Bitcoin, April 18, 2011 (Internet Archive)BitcoinTalk via Internet Archive · 2011-04-18Accessed 2026-08-24
- [5]Source 5: Namecoin FAQ — official project documentationNamecoinAccessed 2026-08-24
- [6]Source 6: Merged mining specification — Bitcoin WikiBitcoin WikiAccessed 2026-08-24
- [7]Source 7: namecoin/namecoin-core commit 68fb8b945e5c — Merge branch 'auxpow'GitHubAccessed 2026-08-24
- [8]Source 8: ENSIP-2: Initial Hash Registrar — ENS documentationEthereum Name ServiceAccessed 2026-08-24