Accepting Bitcoin is one thing. Paying your staff in it is another. This week a South African township project moved its assistants' salaries into sats, a Santo Domingo burger shop paid a worker who then sent those same sats home as a remittance, and a Kenyan shop tied Bitcoin acceptance to a water point and a public washroom. Sats are moving deeper into how people actually earn and spend — and, as a reminder that reliability is part of that story, a sidechain lost most of $320M before clawing most of it back, and BTCPay shipped another security-driven release.
Sats enter the payroll: Bitcoin Ekasi (@BitcoinEkasi) said all its assistants' salaries are now denominated in sats — its Thrift Store prices and the Painted Shack residents' stipends were already priced that way. The project is candid that the surrounding economy still runs on rand, so this is a partial move, not the end of fiat. But paying wages in sats is a real step past acceptance: it puts Bitcoin at the start of the local money cycle, not just the checkout. The next day, community members bought clothes at the Thrift Store with those sats through Blink — earned in Bitcoin, spent in Bitcoin, in the same week.
Spotlight: One Payment, Three Jobs in Santo Domingo
The clearest picture of Bitcoin-as-money this week came from the Dominican Republic. Bitcoin Dominicana (@btcdominicana) described a loop where a burger shop in the Colonial Zone pays a bread maker in sats, and the bread maker uses those same sats to send a remittance to family abroad. One unit of money did three jobs — a retail sale, a wage, and a cross-border transfer — without touching a bank or a conversion in between.
No amounts or frequencies are attached, so this is an illustration of what the rail makes possible rather than a volume figure. But it's the shape adoption takes when Bitcoin stops being something you buy and starts being something you get paid in and pass along.
1) Merchant & Everyday Use
Acceptance kept tying itself to real services and real fees.
- Kibera — Bitcoin across a shop, a water point and a washroom: Kingshop, run by Melchizedek in Raila Village, takes Bitcoin across all three services and received a $250 recoverable grant from Geyser (@geyserfund) for wholesale staples and better water storage. Nearby, UsafiBoys is scaling sanitation with a $650 grant while already accepting Lightning. These are payment-linked operating businesses, not acceptance-only listings — though neither reports a Bitcoin sales figure.
- Kenya — a cash-out for "1 bob": A user reported withdrawing 300 KES for about one shilling in fees using Blink and Tando, saying it beat every platform they'd tried. It's one person's anecdote, not a benchmark — but low-friction cash-out is exactly what keeps sats usable in a mobile-money economy.
- South Africa — a scan-and-pay demo: Bit Fitness (@BitFitness21M) walked a merchant through spending sats at Pick n Pay, ending in a wine purchase over Lightning. Worth being precise: this is a demonstration, not Pick n Pay integrating Bitcoin — no processor was named — but it shows how little friction a scan-to-pay checkout now carries.
2) Payment Infrastructure & Reliability
The rails took two hits this week, and the response is what matters.
- BTCPay Server 2.4.4 — security over convenience: BTCPay (@BtcpayServer) shipped 2.4.4 with breaking changes: NFC and zero-amount invoices are off by default, desktop Boltcard setup is gone (use the Boltcard app), WHMCS users must move to plugin v4.0.0 and regenerate their API key, and external Lightning access stays disabled pending an explicit opt-in. Separately, BTCPay's self-hosted Plugin Builder was compromised (detected Sep 2); it says ordinary users and plugin users weren't affected, but paused new registrations and plugin builds while it hardened. For operators this is a migration to review, not a routine update.
- Liquid — a $320M scare, mostly clawed back: Liquid (@Liquid_BTC) reported roughly 4,000 BTC (~$320M) withdrawn from its federation wallet through the SideSwap PAK, and paused the sidechain. About 27 hours later, a reported 3,400 BTC was returned on-chain — a "purported white-hat" outcome that left users, per Blink's El Flaco (@_pretyflaco), with most of their funds back minus a ~15% haircut. Two caveats matter: this was Liquid's sidechain, not Bitcoin's base layer or Lightning, and "most funds back minus a haircut" is not the same as being made whole.
- A 2,381-day-old bug, quietly fixed: Separately, developer @negrunch flagged a long-standing BOLT11 invoice-parser flaw that let an attacker be paid twice when a payment hash repeated — present for over six years, fixed in August with no CVE or advisory. A reminder that payment reliability lives in dependencies, not just in the node you run.
3) Regulatory & Policy
South Africa's draft cross-border rules moved toward their comment deadline, and the industry organized.
- South Africa — the deadline is September 30: The draft Crypto Asset Manual would treat crypto moving from a regulated South African provider to an offshore provider or a self-custodial wallet as a cross-border flow, and — per the industry's CATASTROPHE campaign (amplified by @BitcoinEkasi) — would make transfers back from a personal wallet impermissible. A coalition is pushing for technology-neutral treatment, with SARB Governor Lesetja Kganyago quoted that "similar payment activities should be subject to similar regulatory expectations." Two things to keep straight: it's still a draft consultation (comments close September 30), and it covers crypto broadly, not Bitcoin specifically. The campaign's "one-way self-custody" reading is its own characterization, not final statutory text — but the window to comment is closing.
Sats showed up in a payroll, a remittance and a washroom this week — Bitcoin working as money people earn and pass along, not just spend. The rails reminded everyone that reliability is never finished: a sidechain nearly lost $320M, a six-year-old bug got quietly patched, and BTCPay traded convenience for a smaller attack surface. The endpoints that last will be the ones that keep earning trust. See you next week.
