Four things nobody tells you when you buy your first bitcoin on an exchange:
1) The balance on screen is a claim on the company, not coins you hold. The terms of service say so.
2) Your ID, selfie and address outlive the account. The breach that leaks them may be years away.
3) Depositing was one tap. Withdrawing is where the limits, holds and questions live.
4) None of this is a scandal. It's what a platform is. What's missing is anyone telling you the other kind exists: bitcoin you hold yourself, bought from a person who signs their own reputation.
Which one did you learn the hard way?
Chama
chama@primal.net
npub1m7ny...jsln
โก๏ธ Trade Bitcoin with anyone.
๐ Trust the math, not a middleman.
โป๏ธ A chama is an East African savings circle โ neighbors who pool their money and settle on trust. Chama gives that same circle to the whole world, except here the trust is cryptographic.
๐ธ Buy and sell Bitcoin, goods, and services peer-to-peer behind an escrow that no company can freeze, seize, or switch off โ because there is no company in the middle.
โ No server. No "Chama Inc."
โ
Just you, your counterparty, your community, and Nostr.
"P2P bitcoin is for people with something to hide."
I get it. The peer-to-peer trades that make the news are the ones that ended in court.
But the people who most need to trade without a platform are the ones platforms won't serve. The shopkeeper whose bank won't touch a cross-border supplier. The nurse whose exchange account has been "under review" for six weeks. The son sending money home and losing a tenth of it on the way.
Handing cash to a neighbour for sats isn't hiding. It's what commerce looked like for most of history. The new thing is a trade that reports itself to three databases before it clears. KYC didn't make those trades legitimate; it made them legible to whoever runs the platform.
Who do you think does most of the world's P2P volume?
Twelve women, a living room in Kasarani, Sunday after church. Each puts 1,000 shillings on the table. One walks home with 12,000. Next month, the next name on the list.
No contract, no interest, no treasurer worth bribing. The enforcement is that everyone knows where you live, and the record is that everyone was in the room.
That's the part a sats version has to replace, and it's harder than the money. Building Chama we shipped the boring half first: equal shares, a deadline agreed before anyone locks, the circle fills or every share goes back by arithmetic, and nobody collects the pot yet. Rotation is next, and the hard question isn't who gets paid; the order can be computed. It's what happens when someone collects in round two and stops showing up. In the living room, the answer is social. On Nostr the plan is a signed record that follows the key, so walking away costs the standing you built.
Would you join one with people you've never sat in a room with?
Before our first on-chain trade touched mainnet, we tried to cheat our own escrow. It worked.
A seller could post a lock pointing at an address built from keys they picked, and the code accepted it, because nothing bound the lock to the keys agreed when the seat was taken. The refund height came from each client's own view of the chain tip, so two people could disagree about the address before a sat moved.
The fix was boring: freeze the terms when the seat is taken (address, three keys, who funds, refund height, dispute delay, network), reject any lock that differs, and have the other side watch the chain every thirty seconds instead of trusting the lock message.
Then we ran all of it on Mutinynet with real coins: a cooperative release, an arbiter dispute after 144 blocks, a refund after the timelock, a refund tried early that the network refused, and the funded key-swap attack, rejected before the coins were recovered.
The dangerous bugs are rarely in the signatures. They're in what the signatures are allowed to be about.
I don't know why but it seems obvious that everyone will either choose an AI to attack others, and/or an AI to defend themselves or others.
Chama v6.4.21 is out. Android and desktop users: please update.
This security hotfix adds authentication to the native wallet bridge, rejects amountless or oversized payout invoices, and stops community switching or resets when the wallet balance cannot be read.
An internal review found one critical and six high findings. This release fixes the critical one and three of the highs; other findings remain open. We have no reports of these being used.
Full details, remaining findings and validation:

GitHub
Release v6.4.21 ยท jesuspirate/chama
v6.4.21 โ Only Chama gets in
A security hotfix. An internal review of the money paths on October 7
(docs/money-path-security-review-2026-10.md) f...