Weekly Brief 2026/35

The week's biggest number comes with an asterisk. A South African payments network reported 95% growth — but it now runs Bitcoin and stablecoins side by side, so that figure isn't a Bitcoin-only adoption rate. Meanwhile the real story was reliability: when a shared service went down, one wallet told its users and the rest went quiet. Payment plumbing, not payment hype, defined the week.

The grassroots layer is maturing from "we accept Bitcoin" toward how merchants actually run the money.

• Onitsha, Nigeria — a cash-flow playbook, not a hodl pitch: Bitcoin Anambra says it onboards Onitsha merchants by covering their naira obligations first — restocking, rent, staff, apprentices — then holding no more than 10% of genuine profit in Bitcoin (not 10% of revenue, not 10% of each payment). That's a concrete risk-control rule that lets a business accept Bitcoin without putting daily liquidity at risk. The most useful "how" we've seen from a local initiative this week.
• Mossel Bay, South Africa — another named township endpoint: Bitcoin Ekasi announced Lightning acceptance at Jabulani Shop No. 3 and describes its Thrift Store & WiFi Zone running on circular sat micropayments — clothes, shoes and children's goods bought with Bitcoin. Availability and use-case breadth, not a sales count.
• Nairobi, Kenya — a priced everyday purchase: A customer paid 495 sats for one litre of water at Aqua Selim, per BitBiashara. One priced transaction for an essential good isn't throughput — but it's more concrete than another map pin.

This was a reliability week. The signal wasn't a shiny new feature — it was how the stack behaves when something breaks.

• The Spark outage — and who said what: When Spark went down Monday, Blink told its users within the hour and posted an all-clear once service returned — the outage was temporary, resolved the same day, and no funds were ever at risk. The other wallets built on the same Spark SDK — Wallet of Satoshi, Cake, and Blitz — said nothing about it on X. Transparency during an incident is itself part of the product.
• Core Lightning — offline first, fix later: A serious Core Lightning vulnerability warning led operators to run nodes with --offline while technical details stay under a two-week embargo. Important nuance: there's no fixed release yet — the latest published build predates the advisory, so the current posture is running offline (with trusted-peer reconnects) and awaiting signed binaries, not upgrading to a patch that doesn't exist.
• BTCPay Server — shrinking the blast radius: BTCPay disabled routes to CLN and Eclair in its default deployment following the advisory, directing operators to update through its maintenance tools. It's an access-and-receiving constraint by design — protect channel state now, restore compatibility carefully later.
• What "offline" looks like on the ground: Machankura — the USSD service that puts Lightning on feature phones with no smartphone or internet — showed the real-world shape of the mitigation: Lightning receiving went "--offline," while Lightning spending, on-chain spending and on-chain receiving stayed functional. A temporary receiving constraint at a live African endpoint, not a full outage — the exact tradeoff the advisory forces.
• Agentic payments — pay-per-request gets concrete: Lightning Enable showed a weather API that normally can't charge an unknown caller returning data after an agent paid 1 sat over Lightning — no account, API key or subscription. A working demonstration of machine-native commerce, not a usage series yet.

One clear provider-formalization step, and one clarification that acceptance stays voluntary.

• Pakistan — a licensing door opens: The Pakistan Virtual Assets Regulatory Authority announced the notification of its Licensing Regulations and opened a licensing portal, with its chairman framing it as the end of "8 years of prohibition." Read it precisely: this is an announced provider-licensing route — the supplied announcement carries no effective date and no operative licensing text, and it's not a legal-tender change or proof of merchant-payment access. A path, not yet a rollout.
• Dominican Republic — voluntary, and taxable on conversion: Bitcoin Dominicana reiterates that Bitcoin is not legal tender but may be accepted voluntarily; a sale is recorded at its peso value when paid, and gains are taxable on conversion. Forms and valuation mechanics remain unresolved — a clarification of the operating environment, not a new rule.

Three threads, one lesson: the quality of a payment signal now matters more than its headline size.

• Attribution is the new discipline. A 95% growth number that blends Bitcoin and stablecoins tells you the region is transacting — but not how much of that is Bitcoin. The next decision-useful evidence is a Bitcoin-only split of those figures and repeat-payment data.
• Reliability is part of adoption. A provider outage, a Lightning advisory, and a payment processor disabling routes all show that whether a merchant can receive a payment now depends on operational response as much as checkout UX — and that how a wallet communicates during an incident is a feature.
• Design beats listings. Onitsha's cash-flow rule and Chama's earn–spend–save loop are stronger indicators of durable payment adoption than another acceptance pin — but both still need repeat settlement counts to graduate from case study to proof.

A 95% number you can't fully attribute, an outage one wallet owned and three others ignored, and a Nairobi litre of water for 495 sats. The week's lesson isn't that Bitcoin payments are booming or stalling — it's that the honest signals are getting more specific, and so should we. See you next week.