BLOG |

Weekly Brief

Weekly Brief 2026/36

Blink brings the BTC Map merchant directory inside the wallet on a shared open standard, a single Nairobi settlement reports 3.78M sats circulating locally, and BTCPay keeps its Lightning rails in careful recovery.

Weekly Brief 2026/36
September 5, 2026
Blink Team

This week the most useful upgrade wasn't a new payment — it was a better way to find where you can spend. Blink pulled the whole BTC Map merchant directory inside the wallet, turning "where can I pay with Bitcoin?" into a first-class part of the app — and onto a shared open standard the rest of the ecosystem is converging on. Underneath that, a Kenyan settlement put a real number on its circular economy, and BTCPay kept its Lightning rails in careful recovery. Discovery is moving into the wallet while the infrastructure stays cautious about safety.

Merchant discovery is now in the wallet: Blink (@blinkbtc) rolled out BTC Map inside Blink — so finding a nearby Bitcoin-accepting merchant no longer means leaving the app. There's a bigger story underneath it, told by Blink's El Flaco (@_pretyflaco): Blink shipped the first bitcoin wallet with a merchant map, but that early version was open source in the wrong shape — a data silo. BTC Map fixed the architecture and kept it open, so Blink ported the map back in on that shared standard — and, in his telling, other wallets adopted a merchant map thanks to BTC Map too. The rollout standardizes clean tags (separate Lightning, on-chain and contactless markers replacing the old catch-all), and Blink is asking communities to verify old listings, add new merchants and remove inactive ones, warning that stale data can send someone to a shop that no longer accepts Bitcoin. As El Flaco puts it, adoption "lives or dies on where you can actually spend it" — and the map is that on-ramp.
Spotlight: Kibera Puts a Number on Its Circular Economy

Grassroots adoption usually comes without figures. This week Afribit Kibera (@AfribitKibera) supplied one: 3.78 million sats activated in a single Nairobi informal settlement, described as sats earned, spent and circulated locally — and, per Geyser (@geyserfund), across 11 local projects launched, supported or promoted, more than any other Field Partner in its network.

The caveat matters as much as the number: there's no time window or transaction count attached, so 3.78M sats is a circulation signal, not a throughput or adoption rate. But a self-reported, sats-denominated measure of money moving inside one community is exactly the kind of ground-level evidence the merchant listings usually can't give us.

1) Merchant & Enterprise Adoption

Community programs kept turning acceptance into everyday checkout — with training attached.

  • Huanchaco — acceptance paired with teaching: Motiv Perú (@MotivPeru) says more artisans in the Peruvian surf town are accepting Bitcoin in daily transactions, and its Educa Bit program runs hands-on training so more local businesses can follow. Linking acceptance to business capability is a stronger signal than a lone listing — though no merchant count or settled value is given.
  • Calabar — sats for a haircut: Bitcoin Calabar (@BitcoinCalabar) reported paying for a haircut at V Brown Barbing Clinic over Lightning, extending everyday use from goods into personal services. One event-level payment, no amount disclosed.
  • Mossel Bay — education reaches the till: Bitcoin Ekasi's August update says Cohort 6 celebrated its first Bitcoin restaurant payment after earning Certificates of Excellence, with students now using Lightning for real-world payments. The bridge from classroom to checkout is the point; the meal isn't quantified.
  • Freshness caveat, repeated on purpose: Several BTC Map records behind this week's posts date to 2025 and still ask for verification — which is exactly why Blink's in-wallet "verify the map" push (above) matters. Treat these as reported use at known endpoints, not fresh onboarding.
2) Payment Infrastructure

The Lightning rails stayed in careful recovery, while one wallet widened its asset scope.

  • BTCPay — updated, but external access still closed: BTCPay Server (@BtcpayServer) shipped Core Lightning v26.06.7 in its Docker deployment, but external CLN access remains disabled and may not return for another week or two. It also warned that some ARM32 devices (older Raspberry Pis) may not work with the release. This is a recovery-and-hardening phase following last month's Lightning advisory — not a return to normal interoperability.
  • Wallet asset scope: Wallet of Satoshi added opt-in self-custodial "Digital Dollars" (a "Show Stablecoins" toggle). Noted for completeness — it's a wallet UX/asset-scope change, not additional Bitcoin-payment usage.
3) Circular Economy & Ground-Level Proofs

Beyond sales, Bitcoin showed up as community support for the merchants themselves.

  • A shop gets repaired in sats: Geyser (@geyserfund) reported an anonymous contributor sending 273,000 sats to Manu Groceries for shop repairs and improvements. It's merchant support, not customer-sales volume — but it shows Bitcoin funding the physical upkeep of a real store, not just tallying its receipts.
  • The loop keeps its shape: From Kibera's circulating sats to Ekasi's earn-and-spend students, the pattern holds: money that is earned locally and spent locally is worth more as a signal than any one-off acceptance listing.
4) Regulatory & Policy

Two policy stories pulled in opposite directions — a consultation in South Africa and a reported crackdown in Afghanistan.

  • South Africa — the clock is ticking on a draft: The Treasury/SARB manual published August 3 would treat movements between a domestic authorised crypto provider and an offshore provider or a non-custodial wallet as cross-border flows reportable to the Financial Surveillance Department; purely domestic transfers between local providers would stay non-reportable. MoneyBadger (@MoneyBadgerPay) amplified warnings that the rules could undermine self-custody and push activity offshore. This is still a draft consultation — comments close September 30, it covers crypto broadly, not Bitcoin specifically, and the underlying Capital Flow Management Regulations aren't finalized yet.
  • Afghanistan — a reported ban, and a voice from the ground: BitcoinNewsCom (@BitcoinNewsCom) reported that the Taliban government has effectively banned Bitcoin and crypto trading, with more than 20 crypto shops closed in Herat, at least 13 traders reportedly arrested, and monthly crypto inflows falling from above $150M to below $80,000. Those figures are crypto-wide, not Bitcoin-only, and come from a single report. Afghan Bitcoiner Janey Gak (@janeygak), writing from the ground, offered the local nuance: authorities reach for blanket bans because they can't police the scam complaints they receive, and she argues that legalizing and educating Afghans would serve them far better than prohibition. Bitcoin's censorship-resistance is precisely why direct-counterparty settlement reportedly continues even as visible exchanges are squeezed.

Two things moved forward this week: the merchant map now lives in the wallet, and a Nairobi settlement is counting its own circulating sats. The work now is keeping that map fresh and the Lightning rails safe — and remembering that where Bitcoin gets banned, like in Herat this week, it's often needed most. See you next week.

Did you find this valuable? Tip the author!

Did you find this valuable? Tip the author!

Social Share Component

Download Blink

Start receiving and sending bitcoin now

Community