BitcoinErrorLog @BitcoinErrorLog

If the assumed topic is scale, along with an assumed goal of adoption, then you have about 3 options: 1. Bitcoin is only ever used by about 10M people, everyone else uses credit 2. More blockchains 3. Bigger blocks The practical choice, and the one the market has expressed since the beginning, is already (2), but there is some movement toward (1). Bigger blocks aren't really communism because everyone actually does have to bear the same costs, and bitcoin is exclusive by costs. As a solution it has a limit that interplays with the fees to make a transaction, and the speed of internet. At some size, it still becomes too expensive for low-tier users, whether by hardware costs, or tx fee costs, or, too slow to keep the network in sync. The real issue is Ponzi Bitcoiners unwilling to own that title. If they did, then an irrational desire to get everyone on one blockchain would be logically consistent. In the end, raising block sizes modestly can increase the number of people that can use the original Bitcoin, but it isn't really enough to get us to billions of users, and it is an odd assumption that everyone would use one coin anyway.

0 0 0 292 1

View Details

BitcoinErrorLog @BitcoinErrorLog

2 days ago

I am here for the @MagicalTux redemption arc.

8 2 18 2K 1

View Details

Miguel Medeiros @_miguelmedeiros

5 days ago

Ghostly started with a question: what if a public key could be an address? Not one controlled by a company. Just a key, discoverable through a network nobody owns. That's Pkarr. I saw it up close at Synonym, and the idea never left my head. While I was working with Pkarr, I wanted to understand the DNS side of it better. That led me to build Selfie Records, a small experiment that linked a domain to Nostr keys, PGP keys and BOLT12 offers through BIP 353. At first it was mostly a way for me to learn how these pieces fit together. Then it hit me: if I could publish those records this way, they could carry much more than identity and payment information. So one weekend I built a tiny chat directly on top of the DHT. It worked. Ghostly was born. Then came the criticism: this would never scale. And they were right. Every message had to fit inside 1,000 bytes. No photos, no files, no calls. Years around Bitcoin, layer twos and drivechains taught me to think in bridges. What if the DHT wasn't where the conversation happened, but just where two peers agreed on how to meet? Now that tiny message negotiates the real connection: WebRTC, Iroh, HyperDHT. And when nothing else works, the DHT is still there. The first chat never went away. From there came files, calls, payments, identity proofs, games, even sharing your localhost with a friend. None of it started from scratch. Pkarr, the Mainline DHT, the libraries and the relays were built by people who believe in an open internet. I just wanted to see what else they could hold. A thousand bytes. Endless ways to meet. 👻

Miguel Medeiros @_miguelmedeiros

2 weeks ago

No account. No phone number. No server in the middle. Ghostly 1.0 is out: chat, calls, files and sats, straight from your app to theirs. Open source. Browser, desktop and extension.

34 82 517 34K 509

2 12 31 1K 4

View Details

Miguel Medeiros @_miguelmedeiros

2 days ago

I hid a chat app inside BitTorrent's DHT 👻 No central server. No accounts. Just millions of strangers holding sealed notes they can't read. How it works, in 90 seconds 👇

2 11 38 2K 6

View Details

BitcoinErrorLog @BitcoinErrorLog

2 days ago

@BitcoinEsVe Well, we'd need to go back to first-seen mempools too...

1 0 0 135 0

View Details

BitcoinErrorLog @BitcoinErrorLog

3 days ago

The Bitcoin Lightning Network

8 0 14 6K 1

View Details

BitcoinErrorLog @BitcoinErrorLog

2 days ago

@bc1q30 They are stats, what do they mean to you?

1 0 0 148 0

View Details

BitcoinErrorLog @BitcoinErrorLog

3 days ago

Cancelled my Adobe subscription today.

6 1 51 3K 0

View Details

BitcoinErrorLog @BitcoinErrorLog

3 days ago

@antirez @CatalinAdler Imagine progress.

0 0 0 70 0

View Details

Pubky @getpubky

3 days ago

In development: Pubky Noise, a library for private communication between Pubky users. The idea: your Homeserver can deliver a message without being able to read it. Each person writes encrypted messages to their own Homeserver, and the recipient retrieves them from there. They don’t need to be online at the same time. Built on the Noise protocol, it supports mutual authentication and encrypted session backups to help apps recover interrupted sessions. A building block for private messaging and payment coordination on Pubky. pubky.org/pubky-noise/