
Creating a ₿itcoin certificate authority 🔑 @spacesprotocol @impervious 5E18 8EC1 571D 32AC F1B8 85CC 12B0 037C E1D4 54E5
Joined January 2020
- Tweets96
- Following92
- Followers125
- Likes871
Replying to @zooko @robin_linus
why is that better? every major platform today uses usernames/handles.
buffrr@bitcoin retweeted
I now own a name ON btc using @spacesprotocol
Not a domain or a username.
A name I hold like a coin.
Why that matters:
Today you pay someone by pasting this:
bc1pknhdaw3jyhvcalyrkulw2hwmqvc5q65ch9gkpnvvhrfajyedjgvqmn3w0c
62 characters. Terrible.
Names fix that but the names we have are rented. A registrar keeps the record, and a chain of companies and governments sits above it. They can drop you from it at any time.
Spaces puts the name on Bitcoin itself:
• @bitsaga is a small Bitcoin coin & only my key can move it.
• rob@bitsaga is a handle I issued myself. One 32-byte fingerprint on Bitcoin covers all handles I might attach.
• It points to a silent payment address, so every payer gets a fresh private address ^^
How does a wallet trust the answer? It does not trust, it checks. A relay hands over a proof (about 3 KB). The wallet verifies it against Bitcoin. The relay can be slow or offline but it cannot lie.
I run my own relay at spacesrelay.bitsaga.be, on my own node. I resolved rob@bitsaga through it and checked the answer against my own node.
Same address, two names:
- [email protected], found through DNS (BIP 353)
- rob@bitsaga, found through Bitcoin (Spaces)
Cost: 6,882 sats in network fees. I renew it once a year.
BUT: almost no wallet reads Spaces names yet. It is very early. So I wrote it all down, with the commands to check it yourself on your own node.
Full article on the website:
Replying to @SinorWorks @spacesprotocol
its just a UI classification issue. we will get it fixed!
buffrr@bitcoin retweeted
Imagine paying robin@bitcoin
That’s it. The wallet picks the rail: onchain, Lightning, Silent Payments, Ark, Glass Coins,...
All behind one handle.
spacesprotocol.org
Replying to @whispawallet @robin_linus
This is just the faucet. its to get a quick pre-generated handle for testing only! handles are issued by submitting your name/pubkey only to the operator never the private key.
My shirt is my payment address. Get your own name@bitcoin at atbitcoin.com @spacesprotocol
Replying to @keet_io
I'm rooting for you guys! Spaces could make pubkeys a lot friendlier: alice@bitcoin instead of a long string spacesprotocol.org/blog/hand…
buffrr@bitcoin retweeted
Replying to @Bitcoin
@bitcoin genesis tx
If you missed the launch, here's the post: Handles on mainnet spacesprotocol.org/blog/hand…
The first tx for @bitcoin on mainnet: 41 handles hashed and anchored to Bitcoin.
Transaction: 09075a71532d08bd...e39008b2 mempool.space/tx/09075a71532…
Commitment root: f31722fdd85df8cae7112024e454d73740d56058f8107beb7c316eb1ade96ba0
That root is the only thing that goes on-chain. 32 bytes, whether the batch holds 41 handles or 41,000. The cost of committing does not grow with the number of names.
Verify it yourself: github.com/buffrr/atbitcoin-…
stacker.news/items/1576127
buffrr@bitcoin retweeted
atbitcoin issued the first batch of handles on Bitcoin mainnet!
stacker.news/items/1576127
buffrr@bitcoin retweeted
Handles on Mainnet!
by buffrr in ~bitcoin, ~nostr
9,273 sats and 8 comments so far
stacker.news/items/1573912
I just registered my bitcoin handle "evan@bitcoin". This is your alpha, go get one. This will get quote tweeted in 10 years as the reason for some of you collecting the most valuable real estate of your lives. It's like registering .com's in the late 1980's. don't be an idiot.
Get your@bitcoin handle through the Nacho app!
Bitcoin handles finally on mainnet!
spacesprotocol.org/blog/hand…
A name that lives off-chain, anchored to Bitcoin. No authority can revoke it. Soon, yourname@bitcoin.
Replying to @robin_linus @rodarmor
i could talk about spaces spacesprotocol.org
buffrr@bitcoin retweeted
Next Monday, the EU decides on Chat Control 1.0. Will they let the Trojan Horse through the gate and let Google, Microsoft, LinkedIn etc continue to scan all your messages?
We at Tuta say NO.
❌ No scanning
❌ No mass surveillance
❌ No age verification
Instead we fight for:
✅ Encryption
✅ Privacy
✅ Open Source
And so should the EU. Call your local representatives! 🥊
Privacy is not negotiable. Speak up now. ✊ #Privacy











