Brian Armstrong Wants Human-Readable Crypto Names. Bitcoin Already Has the Answer.
Brian Armstrong highlighted a problem almost everyone in crypto still feels every day: Bitcoin and cryptocurrency addresses look like random strings of numbers and letters.
At the World Economic Forum he pointed to the Ethereum Name System (ENS) as one way to fix that friction, arguing that ordinary people should be able to send money the same way they flip a light switch. They should not need to understand private keys or hex addresses.
The goal, in his view, is that most users will eventually use crypto applications without even knowing it is crypto underneath.
That diagnosis is correct. Random addresses are a real barrier. A 34-character string is easy to mistype, hard to remember, and impossible to share verbally. Human-readable names remove that friction for payments, Lightning invoices, Nostr identities, and everyday coordination. The electricity analogy is useful up to a point. Most people do not need to know how a power plant works to turn on a lamp. They do, however, need confidence that the switch cannot be flipped by someone else.
This is where Armstrong’s framing and Bitcoin’s actual design diverge.
The private key is not an unfortunate complication to be hidden. It is the feature that makes Bitcoin different from every other payment system. When you control the key, no bank, exchange, or application can freeze, reverse, or confiscate the funds. Removing that control in the name of simplicity simply recreates the custodial model Bitcoin was built to escape. Any naming system that requires users to hand keys to a third party, or that can be revoked by a company, undermines the reason people use Bitcoin in the first place.
Bitcoin therefore needs its own naming layer.
The most secure, decentralized monetary network should not depend on a naming system that lives on a different chain, requires a separate token, requires ongoing renewal fees, or can be censored by a registrar.
That is the gap Spaces Protocol fills.
Spaces Protocol gives Bitcoin human-readable names that stay sovereign.
A top-level Space such as @bitcoin functions like a community identifier, comparable to a top-level domain on the traditional web. Inside that Space, individuals receive handles such as bob@bitcoin. The handle is bound to a cryptographic key the owner controls.
Once issued, it cannot be taken away by an operator, a company, or a committee. Ownership is proven against Bitcoin itself through an inclusion proof and certificate. Extra records (a Lightning address, a Nostr npub, a website, a silent payment address) can be attached and updated off-chain so the blockchain does not fill with large or frequently changing data.
https://bitbane.com/brian-armstrong-wants-human-readable-crypto-names-bitcoin-already-has-the-answer/
#Bitcoin #BrianArmstrong #WEF #WorldEconomicForum #SpacesProtocol #ENS #Spaces #Nostr #DNS #Keys #Sovereign
curiousbitcoin / curious@bitcoin
npub13a…u3m02
2026-10-16 13:34:25 UTC
Author Public Key
npub13a78vq9z0dn4se7f9jtqk0wmx6adc646d576uw86nskxuqd6v6eqeu3m02Seen on
wss://relay.damus.ioPublished at
2026-10-16 13:34:25 UTCEvent JSON
{
"id": "6cb512a7c5711ae24e6ddeddc0cdc35ae12459ff7aae9fa43a74b103e212ce39",
"pubkey": "8f7c7600a27b675867c92c960b3ddb36badc6aba6d3dae38fa9c2c6e01ba66b2",
"created_at": 1792157665,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
],
[
"t",
"brianarmstrong"
],
[
"t",
"wef"
],
[
"t",
"worldeconomicforum"
],
[
"t",
"spacesprotocol"
],
[
"t",
"ens"
],
[
"t",
"spaces"
],
[
"t",
"nostr"
],
[
"t",
"dns"
],
[
"t",
"keys"
],
[
"t",
"sovereign"
],
[
"client",
"iris"
]
],
"content": "Brian Armstrong Wants Human-Readable Crypto Names. Bitcoin Already Has the Answer.\n\nBrian Armstrong highlighted a problem almost everyone in crypto still feels every day: Bitcoin and cryptocurrency addresses look like random strings of numbers and letters.\n\nAt the World Economic Forum he pointed to the Ethereum Name System (ENS) as one way to fix that friction, arguing that ordinary people should be able to send money the same way they flip a light switch. They should not need to understand private keys or hex addresses.\n\nThe goal, in his view, is that most users will eventually use crypto applications without even knowing it is crypto underneath.\n\nThat diagnosis is correct. Random addresses are a real barrier. A 34-character string is easy to mistype, hard to remember, and impossible to share verbally. Human-readable names remove that friction for payments, Lightning invoices, Nostr identities, and everyday coordination. The electricity analogy is useful up to a point. Most people do not need to know how a power plant works to turn on a lamp. They do, however, need confidence that the switch cannot be flipped by someone else.\n\nThis is where Armstrong’s framing and Bitcoin’s actual design diverge.\n\nThe private key is not an unfortunate complication to be hidden. It is the feature that makes Bitcoin different from every other payment system. When you control the key, no bank, exchange, or application can freeze, reverse, or confiscate the funds. Removing that control in the name of simplicity simply recreates the custodial model Bitcoin was built to escape. Any naming system that requires users to hand keys to a third party, or that can be revoked by a company, undermines the reason people use Bitcoin in the first place.\n\nBitcoin therefore needs its own naming layer.\n\nThe most secure, decentralized monetary network should not depend on a naming system that lives on a different chain, requires a separate token, requires ongoing renewal fees, or can be censored by a registrar.\n\nThat is the gap Spaces Protocol fills.\n\nSpaces Protocol gives Bitcoin human-readable names that stay sovereign.\n\nA top-level Space such as @bitcoin functions like a community identifier, comparable to a top-level domain on the traditional web. Inside that Space, individuals receive handles such as bob@bitcoin. The handle is bound to a cryptographic key the owner controls.\n\nOnce issued, it cannot be taken away by an operator, a company, or a committee. Ownership is proven against Bitcoin itself through an inclusion proof and certificate. Extra records (a Lightning address, a Nostr npub, a website, a silent payment address) can be attached and updated off-chain so the blockchain does not fill with large or frequently changing data.\n\nhttps://bitbane.com/brian-armstrong-wants-human-readable-crypto-names-bitcoin-already-has-the-answer/\n\n#Bitcoin #BrianArmstrong #WEF #WorldEconomicForum #SpacesProtocol #ENS #Spaces #Nostr #DNS #Keys #Sovereign",
"sig": "19576d7da4862811cb9a85df071aad11016d455c100511707259e98d2ce31c0beddb3b085990e5c6d4681e6d9e52e67ea23de004f9c5f2158059ed2132e9cb11"
}