Bitcoin privacy wins have empirically come from interactive protocols like coinjoin, lightning, and ecash. Payjoin is the base case interaction that works in a normal payment flow. 2 parties, 1 interaction. That's why I bet it's got the highest odds to evolve into a lasting fix.

Payjoin 1.0.0 has been released! What a journey it has been. Congrats to the PDK team. Expect excellent news on the same to follow shortly. We at BULL been working very hard to improve Payjoin, it's privacy and its adoption across the network.

Seconding this… at our recent Kikuyu Bitcoin glossary translation drive, all contributors were paid in sats and the wallets mentioned here were represented! BTW all contributors working with us get paid in sats. No redtape. Just peer-to-peer!

MELA MEIN KYA MILEGA? A chance to meet Tando’s Co-founder @waithiraah! We're excited to have Sabina G joining us at Bitmela this October. Are you excited to meet her? Get your tickets now!

There has only been 18 submissions - we need more! The Draft Crypto Asset Manual and Capital Flow Management Regulations remain unfinished and procedurally flawed - it is a clear waste of taxpayer money. Submit by 30 September @BitcoinZAR : #PropertyRightsDefense#

Bitcoin Core v32.0 is targeted for release in October: - Up to 3x faster initial sync. Block validation now fetches transaction inputs from disk in parallel instead of one at a time - The libevent external dependency is fully removed, continuing Core's push to cut third-party dependencies - Max peer connections raised from 125 to 200 to have more open slots for new nodes to sync from, faster block propagation, and a harder network to eclipse or partition - Mempool-based fee estimation to cut fee overestimation (in progress) - Transaction relay rate limiting is now global instead of per-peer, keeping a node's CPU and memory usage steady when transaction volume spikes - Ships with features from libsecp256k1 0.8.0 with verification up to 11% faster, plus the new Silent Payments module (BIP 352) - PSBTv2 (BIP 370) support, now the default for PSBT-creating RPCs for better coordination of unsigned transactions for multisig and hardware wallet setups - New exportwatchonlywallet command to export a wallet as a watch-only file, no private keys, and restore it on your online node - Core now enables Tor's proof-of-work DDoS defense on the onion service it creates for your node, where the Tor daemon supports it Additional tests, bugfixes, and features included as well. Feature freeze is ~August 20, rc1 ~September 10, final release targeted for ~October 10. (Test the release candidates when they ship!)

I empirically tested the mathematical theory of payment channel networks. I simulated 1 million payments on the 2-party channel LN, compared to a 3-party channel Network (same total cap) Supported amounts increase by almost two orders of magnitude! Payment Failure rates halved!

Here's some data worth sitting with. The price of everyday essentials in India has climbed steadily for decades. The item didn't change, the value of the money did. Economists call it inflation; most people just call it 'everything's expensive now.' Understanding this is the first step to doing something about it. At Bitmela, we'll walk through what these numbers mean and why high stock to flow ratio enters the conversation. Data, not hype. See you in Oct! Early Bird tickets live now:

Welcome back to the main chain. 🟠 The BIP-110 fork taught us something important, not about who was right, but about how we disagree. Many of you believed in mandatory signaling. You fought for it because you care about Bitcoin's soul, even when the rest of us said the adoption wasn't there and the direction would lead us down a dangerous road. That conviction deserves respect, not mockery. The fork is behind us now. What matters is what we do next. We have real adversaries, financial censorship, regulatory overreach, CBDCs, and an army of rent seekers who want Bitcoin locked down. They're not fighting among themselves. Neither should we. The path forward isn't "my implementation wins." It's making Bitcoin so resilient, so open, and so undeniable that the people trying to control it have no lever left to pull. Welcome back. Let's build together.

This was the essence of our talk at @btcplusplus Clearly identify your customer, and speak their language. Protocol devs don't necessarily need to speak end users languages. That's the job of the application layer to be the translation layer and let end users communicate with bitcoin without needing a dictionary. Of course protocol devs DO have their own set of customers too, most likely layer 2 protocol devs. And they need to speak their languages. Essentially we're all translators for each of our respective customers all the way up the application stack.

We’ve been on a side-quest, and we have good news from the other side! 40 million Kenyans now have a bitcoin Lightning Address! They didn’t need to sign up for one because they had it this entire time, attached to the phone number in their pocket! Try it: send bitcoin to 0717252303@bitcoin.co.ke (254 is optional). The BTC arrives as KES in their M-Pesa. ⚡ EVERY M-Pesa number works. All 40,000,000. Wallets with LUD-09 support give you a nice clickable link to see your M-Pesa receipt. For example: