We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Bitcoin Payment Adoption Tracker
by kemal 109 sources
Monitors Bitcoin adoption as a payment medium and currency worldwide, tracking merchant acceptance, payment infrastructure, regulatory developments, and transaction usage metrics
Bitcoin Anambra
Bitcoin Aves
Bitcoin Dua
Major Adoption News
South Africa — MoneyBadger’s 2026 report provides the period’s clearest demand-side measure, but it is not Bitcoin-only. The report measures completed payments across South African merchants and describes routine spending on groceries and fuel, generally in amounts under R200, both online and in-store. It says activity that began in 2023 as Bitcoin payments at a major national retailer is now a mix of Bitcoin and rand-backed stablecoins; payments across the network grew 95% in the first half of 2026 versus the same period a year earlier, while rand value spent grew 176%. The business significance is the shift from exchange or cross-border proxies to observed retail payments; the limitation is that neither headline growth rate can be attributed to Bitcoin alone.
Awka, Anambra, Nigeria — Sario Eventers is a concrete low-friction Lightning payment example. Bitcoin Anambra says a community member bought an attachment and settled the bill over Lightning with a QR code and swipe, with “no transfer” and “no POS.” The post gives a Blink address, while BTCMap places the merchant in Awka and flags Lightning and Bitcoin acceptance; the map does not classify the business sector. This demonstrates a completed payment path without dedicated point-of-sale hardware, but not repeat demand or merchant scale.
Akatsi, Ghana — Padis Eatery is a mapped Lightning food merchant. The current post identifies the venue as Ghanaian, gives its Blink Lightning address, and links to BTCMap; the listing supplies an Akatsi address and shows Lightning acceptance. The listing is dated November 2025, so this is evidence of continued visibility and spendable supply rather than proof of a new current-period onboarding.
Calabar, Nigeria — Chef Green adds a food-payment use case. A current post says meals were paid for with Bitcoin and supplies a Blink address; BTCMap identifies Chef Green Signature Local Cuisine Hub at Atekong Junction, Calabar, with Lightning and Bitcoin acceptance indicators.
Payment Infrastructure
BTCPay Server — location not stated; processor and node-operator impact. Version 2.4.3 is the final, fully open-source release, described as security-focused with a strong upgrade recommendation. External access to the LND API remains restricted, however, so remote integrations such as Zeus may not work with BTCPay-hosted LND nodes for now. The release therefore pairs security-focused maintenance with a specific compatibility constraint for operators using remote Lightning tooling.
BULL Wallet — location not stated; mobile-wallet layer. Version 6.13.0 restores Lightning sends and receives after the suspension of Boltz services, along with manual and automatic Liquid-to-Bitcoin transfers. It also improves Payjoin v2 recovery after interruptions or restarts and adds BTCMap discovery of nearby Bitcoin-accepting businesses without requesting device-location access. The combination addresses both payment continuity and merchant discovery, though the release itself supplies no usage measure.
Blink/Spark — location not stated; temporary availability dependency. Blink said Spark, the service provider it uses for non-custodial accounts, was temporarily down while an issue was investigated; Blink later said the outage had been resolved and service was back up. The episode is a reliability signal for payment accounts that depend on an external service, not evidence of lost funds or a lasting interruption.
Agent-to-service payments — location not stated. Lightning Enable MCP now supports MPP over Lightning alongside L402, allowing agents to use either flow without accounts, cards or checkout; the update provides .NET, Python and Docker distribution paths. A companion illustration reduces the interaction to an API quoting 5 sats, an agent paying, and the API returning the result. This lowers the apparent integration friction for machine-initiated micropayments, but the illustration is a capability flow rather than an adoption or volume metric.
Regulatory Landscape
No qualifying change — no jurisdictional rule is stated in the current-period material read. The payment-relevant sources reviewed here describe South African payment behavior and software, wallet and merchant operations; they do not announce a legal-tender, licensing, taxation or transaction-rule change.
Usage Metrics
The period contains one aggregate network measure and several isolated merchant-payment examples. They should not be combined into a Bitcoin adoption rate.
| Geography / scope | Reported measure | What it indicates |
|---|---|---|
| South Africa — MoneyBadger network | Payments grew 95% year over year in H1 2026 and rand value spent grew 176%; the network now combines Bitcoin and rand-backed stablecoins. | The strongest aggregate retail-payment signal in the period, but not a Bitcoin-only count or value series. |
| Awka, Anambra, Nigeria — Sario Eventers | One community member’s bill was settled over Lightning; no amount is stated. | A completed low-friction payment, not a frequency or population measure. |
| Calabar, Nigeria — Chef Green | Meals are reported as paid with Bitcoin; no amount or frequency is stated. | A food-sector use anecdote, not transaction volume. |
| Akatsi, Ghana — Padis Eatery | Lightning acceptance is listed; BTCMap dates the listing to November 2025. | Merchant availability and discoverability, not a current-period transaction count. |
| De Rust, South Africa — Nouvelle Saison | The current post says sats left the wallet; BTCMap lists the deli at 3 Kerk Street and dates the listing to January 2025. | A payment-use signal attached to an existing listing, not confirmed new onboarding or repeat use. |
| Location not stated — Haven food court | Chips were reported paid for in sats via Bolt Card. | Evidence of a Bolt Card payment path, with no amount or frequency. |
No read source supplies a comparable Bitcoin-only transaction count, settled Bitcoin value, merchant total or repeat-use rate. The only aggregate growth figures explicitly combine Bitcoin and stablecoins, while the merchant records expose acceptance routes and individual examples rather than demand totals.
Emerging Markets
Everyday household use — location not stated. BTC Shule describes a mother using a Fedi wallet to buy soap with sats and frames the payment as a simple transaction for an ordinary need. This is a stronger usability signal than a generic acceptance announcement, but the post gives no amount, merchant total or location.
Education-linked circular use — location not stated. Bitcoin Dua says students earn and spend to keep a circular economy in motion and pairs the message with a Blink merchant address and BTCMap listing. The model links payment practice to education and local circulation, but the post reports neither student participation nor transaction volume.
Across the African examples, the recurring distribution pattern is a named Lightning endpoint plus BTCMap discoverability, with food, household goods and small retail purchases providing the visible use cases. The current evidence is therefore richer in payment availability and practical demonstrations than in sustained, geographically comparable demand.
Adoption Outlook
The period shows two different kinds of progress. South Africa offers measurable growth in a mixed Bitcoin-and-stablecoin retail network, while Awka, Calabar, Akatsi and De Rust provide concrete merchant-level payment or acceptance signals without Bitcoin-only scale measures.
Payment plumbing is advancing through distinct tradeoffs: BULL restored Lightning functionality and added merchant discovery, BTCPay is prioritizing a fully open-source security release while retaining an LND API compatibility constraint, and Lightning Enable is broadening machine payments beyond L402 to MPP. Spark’s temporary outage and subsequent restoration show that service dependencies remain part of the user-facing payment experience.
The near-term viability question is whether these endpoints and demonstrations become repeatable, measurable Bitcoin payments. This period provides mixed-asset network growth, individual transactions and better tooling, but still no comparable Bitcoin-only transaction count, value or repeat-use rate.
Bitcoin Sisonke
Bitcoin Victoria Falls
Lightning Enable
Major Adoption News
Oslo Airport, Norway — a duty-free Bitcoin checkout is reported to settle directly into self-custody. Blink’s linked brief says Tax Free Norway’s shop routes all of its Bitcoin “freedom money” sales through BTCPay Server directly to a non-custodial Blink account, with no custodian between the till and the merchant’s wallet. It describes a live deployment at one store, with no sales figures disclosed. The significance is a concrete airport-retail integration that removes a custody layer at settlement; it is not evidence of airport-wide scale.
Witsand, Western Cape, South Africa — a small-town acceptance footprint remains the strongest grassroots scale signal. Blink reports roughly 600 residents and about 45 Bitcoin-accepting establishments across groceries, restaurants and fuel. The linked report dates that count to April 2025, so it is a footprint baseline rather than current-period growth. Merchants reportedly receive guaranteed fiat exchange rates, while the initiative began with a local programmer and restaurant owner and benefits from Garden Route tourism; no transaction volumes are reported.
Payment Infrastructure
Online creator payments — Blink has extended its Donate Button to non-custodial accounts. The same one-minute embed and donor experience now work for custodial and non-custodial Blink users, with sats arriving in a wallet where the recipient holds the keys. The button resolves a username to a Lightning address and generates an invoice; Blink says it needs no backend, server, Lightning node or installation, and any Lightning wallet can pay the invoice. For non-custodial accounts, payment uses LNURL-pay and lands in Bitcoin Balance; the feature currently supports only blink.sv Lightning addresses and cannot route those donations to Dollar Balance. Blink cites Molo BTC in South Africa as using the button as its only donation channel, an implementation example rather than a donation-volume measure.
Payment-processor security — BTCPay is trading feature velocity for a smaller attack surface, according to Blink’s brief. BTCPay founder Nicolas Dorier is quoted as saying the project will put the brakes on new features, with future releases potentially removing features or breaking compatibility because combining features creates attack surface. The same brief says ZEUS’s post-mortem of an August 5 breach found that an exploited BTCPay vulnerability closed most of its LSP channels, but channel closures settled balances back to their owners and no customer funds were lost or put at risk. These are reported hardening and resilience signals, not evidence of higher payment throughput.
Agentic payments — Lightning Enable is specifying an audit layer for machine-initiated spending. Its proposed payment receipt would show the service called, sats spent, policy authorizing the payment, remaining budget and how access can be revoked; the account describes the wallet balance as the leash and the receipt as the evidence. This is a control specification for auditable Lightning payments, not a reported deployment or usage metric.
Regulatory Landscape
No country-specific legal-tender, licensing, taxation or transaction-rule change can be grounded from the current-period material reviewed. Blink’s roundup labels @btcdominicana under “Policy” but provides no rule, jurisdictional change or implementation detail, so it supplies only an unelaborated policy signal.
Usage Metrics
The measurable evidence is concentrated in acceptance footprints rather than settled value or transaction frequency:
| Geography | Reported measure | Interpretation |
|---|---|---|
| Witsand, Western Cape, South Africa | About 45 accepting establishments among roughly 600 residents; the count is dated April 2025. | Historical footprint baseline, not current-period growth; no transaction volume is reported. |
| Berlín, El Salvador | Bitcoin Berlin SV says four pizza places now accept direct sat payments. | A food-sector availability count, not a sales or repeat-use statistic. |
| Livingstone, Randwest 1759, De Rust 6650 and Agbozume | Four current-period posts advertise individual Blink paycodes and BTCMap entries. | Supply-side discoverability; the posts do not report settled amounts or transaction counts. |
No source read here supplies a comparable total transaction count, settled value or repeat-use rate, so the figures should not be combined into an adoption rate.
Emerging Markets
African grassroots networks — payment discovery is being packaged as paycode plus map listing. In Livingstone, Bitcoin Victoria Falls posted firstspringenterprise@blink.sv; the linked entry identifies First Sping Enterprise on John Hunt Way, lists Lightning acceptance and associates the location with Bitcoin Victoria Falls.
In Randwest 1759, Bitcoin Sisonke posted Mucambe@blink.sv; the linked BTCMap record identifies Mkambi on Folly Ledwaba Street and shows an LN acceptance icon. In De Rust 6650, Bitcoin Karoo promoted herries@blink.sv; the Herries record shows Lightning and Bitcoin acceptance icons plus a “Contactless” label. In Agbozume, Bitcoin Dua promoted leni12@blink.sv; Leni Boutique’s listing explicitly accepts Lightning, on-chain and contactless payments.
These records are useful for merchant discovery but are not a count of newly onboarded businesses: Mkambi’s map activity is nine months old, Herries was created two years ago, and Leni Boutique was created five months ago. The current posts therefore show continued promotion and payment-route visibility, not confirmed settlement activity. The listings also do not state merchant sectors in the fields read, so industry should not be inferred from names alone.
Adoption Outlook
The period’s strongest progress is in the payment path: a reported direct-to-self-custody airport checkout, a no-server Lightning receiving tool for creators, and explicit controls for auditable agent spending. African communities are simultaneously making local acceptance searchable through Blink paycodes and BTCMap, but the evidence remains richer in availability than demand. The principal constraint is measurement: Witsand’s 45-business figure is an April 2025 baseline, Berlín’s four-pizzeria count has no sales data, and the promoted merchant endpoints expose payment routes rather than settlement totals.
Lightning Enable
Bitcoin Chama
Jesse Posner
Major Adoption News
Aruba — Bitcoin Aruba is marketing a free BTCPay onboarding path. The BTC.aw page advertises a free BTCPay Server for accepting Bitcoin online or in-store, with no processing fees. It opens registration for a free “Bitcoin Aruba” account, instructs users to connect an external wallet, and says funds go directly to that wallet rather than being held by the service. The offer includes point of sale, payment buttons, invoicing, e-commerce integrations and Lightning support. This is a supply-side onboarding initiative, not evidence of merchant enrollment, settled sales or repeat use; its business proposition is to reduce processor-fee and custody friction for prospective acceptors.
Online, location not stated — Shopinbit is being promoted as a Bitcoin-paid shopping service. @JoeNakamoto’s post says a customer can ask Shopinbit to find a car, watch or gift, pay in Bitcoin and receive the item, while offering a first-purchase discount code. That broadens the visible spending proposition beyond local checkout, but the post is an endorsement rather than evidence of a completed order or transaction volume.
Payment Infrastructure
Lightning channel security — threshold custody is being presented as compatible with today’s channels. Jesse Posner linked a paper arguing that a counterparty can use multisignature protection in a Lightning channel without changing the protocol. The paper’s abstract describes “Iceberg,” a nested-threshold MuSig2 construction that lets one side of a channel operate as a $t$-of-$n$ group while appearing to the counterparty as a standard participant. It says this can be deployed on today’s Lightning Network without modifying Bitcoin, Lightning or channel counterparties; it also reports a prototype integrated into a production Lightning node and more than 93% of the payment throughput of an unmodified endpoint when the threshold group tolerates one corrupted member. If deployed beyond the prototype, this could distribute signing authority for payment nodes without requiring changes by merchants or channel peers. The abstract-level benchmark is not evidence of network-wide deployment.
Agentic payments — Lightning Enable is packaging invoice and L402 payments into an MCP wallet workflow. Its current post recommends giving an agent a small Lightning wallet separate from the main wallet, connecting Strike or NWC, and running test_l402_payment; one small live payment is presented as confirmation that the path works. The linked quickstart lists paying invoices, automatic micropayments to L402-protected APIs, and purchases from L402 stores as supported agent actions. Strike is described as requiring no node infrastructure and supporting L402, with NWC wallets and self-hosted LND offered as alternatives. The documentation also includes configurable approval tiers and per-payment and per-session limits. This lowers the integration barrier for machine-to-service payments, but the live micro-payment is a capability check, not an adoption or demand metric.
Regulatory Landscape
No qualifying regulatory change. The grounded payment material reviewed for this brief is operational rather than legal—merchant endpoints, a Fedi purchase and payment-acceptance tooling. No source-stated legal-tender, licensing, taxation or transaction-rule change was identified for inclusion.
Usage Metrics
The period’s measurable signals are heterogeneous: a few payment anecdotes, wallet-education examples, merchant endpoints and a technical benchmark. They do not form a comparable adoption series.
| Geography or system | Reported measure | What it indicates |
|---|---|---|
| Location not stated — BTC Shule/Fedi | One reported biscuit purchase using Bitcoin sats at BTCMap merchant 26331. | A completed retail-payment anecdote; no amount, frequency or repeat-use rate. |
| Location not stated — surf shop | One user reported making a first Bitcoin payment there in 18 months. | An individual usage-frequency signal, not a population measure. |
| Location not stated — Richland General Shop | Children are said to have learned to pay with a Lightning wallet. | Household usability and education; no child, merchant or transaction count. |
| Location not stated — grassroots merchant posts | Current posts provide actionable endpoints for a Zap merchant, Blink merchants and BTCMap listings at several named businesses. | Acceptance discoverability and supply-side activity, not aggregate merchant adoption. |
| Lightning protocol — Iceberg | A threshold group tolerating one corrupted member is reported at more than 93% of unmodified-endpoint payment throughput. | A cryptographic performance benchmark, not settled payment volume. |
| Agentic Lightning — Lightning Enable MCP | One small live payment is used to confirm the payment path. | A test signal, not agent-payment demand or network throughput. |
No current item supplies a comparable total transaction count, settled value, merchant total or repeat-use rate.
Emerging Markets
Location is not stated in most of the source posts, but the grassroots distribution pattern is clear. Bitcoin Chama pairs an “everyday money” message with a Zap merchant address and BTCMap location. Bitcoin Dua combines a circular-economy message with a Blink merchant address and map listing. BitFitness adds the instruction “Spend sats where you live” to a Blink address and BTCMap listing, while Bitcoin Victoria Falls posts a Blink merchant and the line “Money must be used.” Bitcoin Aves likewise advertises sats for an extension socket at Speare Electricals with a Lightning address and map entry.
The emerging-market signal is therefore a low-cost acceptance loop—named paycode, map discoverability and an explicit reason to spend—rather than a reported market share. Education is part of that loop: the Fedi biscuit purchase and the Richland child-wallet example place Bitcoin payments in ordinary household contexts. Because the posts do not identify most merchant locations or provide settlement data, they should not be converted into country-level adoption rates.
Adoption Outlook
The payment stack is advancing on three fronts: Aruba is lowering the advertised cost and custody barrier to acceptance, Iceberg targets resilience of Lightning signing keys without channel-counterparty changes, and Lightning Enable is turning L402 and invoice payment into an agent workflow with spend controls.
The demand-side evidence remains local and anecdotal: one biscuit purchase, one reported 18-month gap between surf-shop payments, a household Lightning-wallet workflow and a growing set of paycode/map listings. The defensible read is improving payment infrastructure and usability, not yet scaled or sustained demand.
Bitcoin Berlín SV 🇸🇻
Bitcoin Ekasi
Bitcoin Sisonke
Major Adoption News
Onitsha, Nigeria — Bitcoin Anambra is pairing merchant onboarding with cash-flow controls. The initiative says it is onboarding merchants in Onitsha, where traders must cover restocking, rent, staff and apprentices in naira. Its operating rule is to convert what the business needs first, then hold no more than 10% of genuine profit in Bitcoin—not 10% of revenue or each payment. The significance is practical: Bitcoin can be accepted as a payment input without putting day-to-day business liquidity at risk. The post frames this as a merchant operating policy, not an investment pitch.
South Africa — Bitcoin Ekasi reports Bitcoin in both retail and compensation. The project highlighted a thrift store advertised as accepting 100% Bitcoin. It also says its high-school assistant coaches and teaching assistants receive part-time salaries calculated and paid in sats. Together, the posts show a local circular-economy model reaching beyond checkout into labor compensation; they do not state payment amounts, participant counts, or the rail used for the salaries.
Berlín — merchant discoverability is being made visible at the point of sale. Bitcoin Berlin SV says it installed a Bitcoin sign at Minimarket El Monarca and left the business a copy of Bitcoin para Negocios, presenting the sign as a way for customers to find places where they can pay and merchants can get paid. This is a concrete onboarding and discovery intervention, but the post reports no completed transaction or volume.
Payment Infrastructure
Location not stated — Bitcoin Babies rebuilt recurring payments after a wallet feature was deprecated. The group says it used Blink’s batch-payment feature for more than two years to pay its mothers, then faced roughly 40 manual transactions per week when the feature was deprecated. It built its own tool with the Spark SDK; outgoing payments appear instantly in the Blink app, which is viewing the same wallet. The important infrastructure signal is user-side portability: an open SDK allowed a recurring payment workflow to continue when a wallet feature disappeared. The roughly 40 figure measures the group’s weekly workload, not Lightning-wide throughput.
Online/API payments — L402 is being positioned as payment-based authorization. Lightning Enable describes an API route that sells a single request without signup, a permanent API key, or a card form: the agent receives a price, pays, retries with proof, and gets the response. A later example prices one result at 5 sats, with proof of payment serving as permission to receive it; the account also solicited an endpoint to test with a sats-funded wallet. This is a meaningful machine-to-service payment pattern, but the evidence is a sandbox and testing signal rather than production usage data.
Location not stated — School of Satoshi’s Cohort 7 produced payment-oriented prototypes. Students built Satoshi Events, an event-ticketing platform on Bitcoin and Lightning promising instant payments and low fees, and Easy Sats, an interface connecting users to Lightning for depositing sats, shopping, and paying. The post demonstrates an education-to-building pipeline, not live user adoption: it supplies no deployment, user, or transaction figures.
Regulatory Landscape
Pakistan — the virtual-asset regulator announced a licensing route after what it described as an eight-year prohibition. PVARA’s chairman announced the notification of Licensing Regulations and the opening of a licensing portal, saying the process sets requirements for providers and guarantees for consumers. Bitcoin Babies linked the change to the prior State Bank of Pakistan instruction to banks to block transactions, which it said had made merchants hesitant to accept Bitcoin; it described the new framework as providing needed legal certainty.
For Bitcoin payments, this is an institutional-access signal rather than evidence of a legal-tender change, bank rollout, or payment-volume increase. The posts establish licensing and a compliance pathway, but do not identify licensed payment providers or report settled transactions.
Usage Metrics
The current evidence is stronger on workflows and acceptance endpoints than on comparable settled-payment statistics:
| Geography or system | Reported measure | What it indicates |
|---|---|---|
| Location not stated — Bitcoin Babies | Approximately 40 manual transactions per week when Blink’s batch feature was deprecated. | Recurring-payment workload, not network throughput. |
| Online/API — L402 | A 5-sat example price for one result. | A unit-price illustration, not request volume or settled value. |
| Onitsha, Nigeria | Merchant onboarding is stated, but no merchant total or transaction count is supplied. | Supply-side adoption, not measured usage. |
| South Africa — Bitcoin Ekasi | One thrift store is described as accepting 100% Bitcoin; the salary post names assistant and teaching-assistant groups but gives no headcount or payout value. | Breadth of use cases, not scale. |
| Pakistan | Licensing regulations and a portal are announced, with no payment-adoption statistic. | Regulatory readiness, not transaction growth. |
Emerging Markets
Calabar, Nigeria — a merchant endpoint is paired with an explicit payments thesis. Bitcoin Calabar listed zerolimit@blink.sv and a BTC Map record while urging users to spend, circulate, and use Bitcoin; a reply argued that failure to find an everyday payment use case would make Bitcoin increasingly irrelevant. This is a clear local-merchant discovery and advocacy signal, but not a reported sale.
Location not stated in the posts — paycode-plus-map listings are recurring across grassroots channels. Sisonke published Ntombana@blink.sv as a merchant paycode, described it as peer-to-peer electronic cash powered by Lightning, and linked BTC Map. Bitcoin Chama similarly promoted Kemunto@blink.sv alongside a BTC Map location and an “everyday money” message. The pattern lowers the friction of finding and paying local merchants; neither post reports an amount, transaction count, or repeat-use rate.
Adoption Outlook
The period shows a layered payment ecosystem rather than measured scale. Pakistan’s licensing announcement could reduce the legal ambiguity described by merchants, while Onitsha’s model addresses the cash-flow risk of accepting Bitcoin and Bitcoin Ekasi places it in both retail and sat-denominated compensation.
At the infrastructure edge, a Spark SDK workaround preserves recurring group payments, L402 tests per-request payment authorization, and student-built applications target ticketing and consumer payments. The constraint is measurement: the clearest numbers are a group’s roughly 40 manual transactions per week and an illustrative 5-sat API price, while most other signals are merchant endpoints, onboarding claims, regulatory announcements, or prototypes rather than settlement totals.
Money⚡️Badger
Bitcoin Aves
Lightning Dev Kit
Major Adoption News
Oslo, Norway — Tax Free Norway connects checkout to direct settlement. NorthOfTheWalls reported that all “freedom money” sales at Tax Free Norway’s duty-free shop at Oslo Airport using BTCPay Server are settled directly to a non-custodial Blink account through an updated Blink–BTCPay Server plug-in. This is a live processor-to-wallet integration rather than a directory listing: it reduces the custody layer between a merchant checkout and its receiving account, although the announcement gives no sales count or value.
Witsand, Western Cape, South Africa — a reported town-scale acceptance model. Money Badger described Witsand as a tiny South African town going “all in” on everyday Bitcoin payments. The linked report describes a village of roughly 600 residents with 45 establishments accepting Bitcoin for purchases ranging from groceries to fuel; its timeline dates the 45-establishment count to April 2025, so it is best treated as a footprint baseline rather than current-period growth. The initiative began with a local programmer and restaurant owner, and the report says merchants receive guaranteed fiat exchange rates, while the community has also begun facilitating Bitcoin-denominated loans. Garden Route tourism gives participating businesses a potential visitor-spend channel beyond the local population. The combination addresses merchant volatility concerns and broadens Bitcoin’s role beyond checkout, but the source reports no transaction volume.
Ekiti, Nigeria — education was paired with actual Lightning use. Bitcoin Ekiti said its participants moved beyond theory, learning why Lightning can make everyday Bitcoin transactions fast, low-cost and easy to use, then putting that knowledge into practice. A later post promoted spending sats at a local merchant through the Blink wallet and a BTC Map listing. This is a credible education-to-payment pathway, but it remains a demonstration: no merchant name, amount or repeat-use rate is given.
Bitcoin Ekasi — rewards reached a retail checkout. In its Cohort 6 program, Bitcoin Ekasi said students earned their first weekly attendance rewards after a 100% attendance week and then spent the Bitcoin at John’s Shop through Lightning. The post supplies a concrete link between an incentive program and local retail spending, but not the number of students, sats spent or transactions.
Smaller channels continued to publish spendable endpoints: Bitcoin Aves promoted “sats for food” at Dora’s Food Joint with a Blink Lightning address and BTC Map record, while Bitcoin Karoo publicized doornkraal@blink.sv alongside a BTC Map listing. These improve merchant discoverability; neither post establishes completed payment volume.
Payment Infrastructure
BTCPay Server — security concerns are now constraining feature velocity. Nicolas Dorier said BTCPay Server must put the brakes on new feature development for a while and warned that future releases may remove features or introduce breaking changes because of attack surface created when features are combined with other exploits. This is a security-led change in product posture for a major merchant-payment stack. The announcement does not identify the affected features or prescribe an operator migration path, so compatibility and service impacts remain prospective.
Lightning node operations — AI control is moving into pre-release tooling. LDK Server remains pre-release, but ldk-server-mcp exposes every node RPC as an MCP tool for clients including Claude Code, Codex CLI and Goose; the example use case is querying which channels have low outbound liquidity. If hardened for production, this could lower the operational burden of monitoring and managing Lightning liquidity. The current signal is an operations interface, not evidence of live payment adoption or production throughput.
Regulatory Landscape
Dominican Republic — statutory recognition without a payment-law reset. Bitcoin Dominicana’s current announcement says Bitcoin has entered Dominican legislation but explicitly says this does not mean it is regulated or that the work is finished. Its linked legal analysis discloses that the author presides over the Asociación de Bitcoin Dominicana, and says the country still lacks a digital-assets law even though two laws enacted between August 2025 and June 2026 now mention cryptoassets; neither regulates the sector.
- Anti-fraud treatment: Law 74-25, effective in August 2026, contains the first statutory mention of digital assets in the Dominican Republic, in the provision on pyramid fraud. The analysis says the provision does not define cryptoassets, create licenses or assign a supervisor, and does not make buying Bitcoin, self-custody, receiving it as payment or sending it illegal.
- Tax treatment: Law 30-26, promulgated June 18, 2026, added “digital goods and cryptoassets” to the Tax Code’s definition of capital assets. The analysis says this elevates an existing tax position rather than creates a new Bitcoin tax: holding Bitcoin is not taxed, while a profitable sale is treated as a capital gain.
- Payment status and next steps: The peso remains the only legal tender, so no one is obliged to accept Bitcoin, but voluntary agreement to accept it is not illegal. Two sectoral bills had no recorded progress after the June committee activity and remain pending into the next legislative session; the country still lacks a dedicated licensing, custody, consumer-protection and prudential regime for digital-asset providers.
Usage Metrics
The period’s measurable signals describe acceptance coverage and program activity more often than settled transaction volume:
| Geography | Reported measure | What it measures—and what it does not |
|---|---|---|
| Witsand, South Africa | Roughly 600 residents and 45 Bitcoin-accepting establishments across groceries, restaurants and fuel; the article dates the count to April 2025. | Merchant footprint, not current-period sales, transaction count or repeat usage. |
| Oslo Airport, Norway | All announced “freedom money” sales at one Tax Free Norway duty-free shop route through BTCPay to a non-custodial Blink account. | Checkout coverage at one site, not sales volume or value. |
| Bitcoin Ekasi | Students reportedly reached 100% attendance, received weekly Bitcoin rewards and spent them at John’s Shop via Lightning. | An education and incentive program linked to retail use, not a transaction or merchant-growth statistic. |
No current direct-spend example in the reviewed set supplies a comparable sats amount, transaction total or repeat-use rate.
Emerging Markets
Kitui, Kenya — merchant onboarding is being funded as grassroots infrastructure. Bitcoin Kitui is soliciting support for its Bitcoin Circular Economy, accepting Lightning donations at galactic100@blink.sv and saying every donated sat helps onboard new merchants. This is a supply-side adoption signal: the project is trying to expand the acceptance base, but it reports neither funds raised nor merchants onboarded.
Livingstone, Zambia — Bitcoin is being positioned as part of a visitor economy. Bitcoin Victoria Falls invited visitors to see the natural wonder and experience how Bitcoin is becoming part of everyday life in Livingstone, explicitly framing the offer around a local Bitcoin economy. The tourism connection is commercially relevant, but the post names no participating businesses and gives no payment data, so it is a market-development signal rather than verified usage.
Adoption Outlook
The strongest signals are operational and grassroots rather than macroeconomic: a live BTCPay-to-non-custodial-wallet deployment at Oslo Airport, a reported multi-establishment footprint in Witsand, and education-linked Lightning spending in Ekiti and the Bitcoin Ekasi program.
The enabling stack is developing under constraint. BTCPay is considering feature brakes, removals and breaking changes to reduce attack-surface risk, while AI-assisted Lightning node management remains pre-release. Dominican legal developments add anti-fraud and tax recognition, but leave the peso as the only legal tender, impose no Bitcoin-acceptance mandate and do not create a comprehensive sector regime. The defensible read is wider acceptance infrastructure and more varied community use cases, while the only broad merchant count is a dated April 2025 baseline and current spending posts still lack transaction values or volumes.
₿itBiashara
Cuba Bitcoin 🇨🇺
Tando
Major Adoption News
Bitcoin Ekasi — South Africa. In an update posted during the period, Bitcoin Ekasi reported 10 Diploma students, 31 attendances and 15,500 sats distributed as learning rewards. It also said that, after the 8 August graduation, some students—among them people visiting a restaurant for the first time—paid for their meals with Bitcoin through Bolt Card. This is the period’s clearest programmatic bridge from education into a real retail payment, although the post gives no meal count or ticket value.
Cuba — travel acceptance alongside a sat-denominated community event. Cuba_BTC promoted what it called Cuba’s first Yu-Gi-Oh! tournament in which participants could win sats. The event’s sponsor post identified BitrideGo as the first motorcycle-rental agency for travel in Cuba where customers can pay with Bitcoin and listed 25,000 sats in prizes. The significance is category expansion into travel services; the sponsor description and prize pool do not establish rental-payment usage or transaction volume.
Grassroots retail — reported purchases in ordinary sectors. The Bitcoin Calabar account said a club member paid for a haircut with Bitcoin at freshbarbs@blink.sv. BitBiashara reported that a charging cable at Viwa Accessories was paid for in Bitcoin, while a separate BTC Shule post described a mother buying soap with a Fedi wallet. These are transaction-level use reports across personal services, accessories and household goods, but each is an individual example rather than a merchant-growth or repeat-use measure.
Randfontein, South Africa — a discoverable Lightning endpoint. Sisonke published Nyamboseprints@blink.sv as a merchant paycode for a local internet café, described the experience as instant and low-fee, and linked BTC Map. The linked record identifies Nyambose Prints at 2766 Nhlapo Street, Randfontein 1759, and shows Lightning acceptance. This is a concrete acceptance endpoint, not a reported payment event.
Payment Infrastructure
Dominican Republic — Bitcoin Dominicana is turning BTCPay Server into a local merchant playbook. Its current announcement says businesses can accept Bitcoin and Lightning without surrendering custody, using open, non-custodial BTCPay infrastructure, and links to a setup guide. The guide describes BTCPay as free, open-source and self-hosted, with no processing fee beyond an on-chain network fee. It also describes a browser-based point-of-sale app that runs on a phone, tablet or computer and says this is how more than 100 Dominican businesses already accept Bitcoin.
The custody qualification is material for merchants. In the standard setup, BTCPay uses an extended public key to generate receiving addresses while payments go directly to the wallet the business controls. Lightning can provide near-instant, low-fee payments for small amounts, but the guide warns that using a third-party host’s internal Lightning node sends payments to that host’s wallet; custody therefore depends on configuration, not on the BTCPay label alone.
Lightning and machine payments — an architecture signal, not live adoption. Lightning Enable framed agentic commerce as a native loop of “discover → price → pay → prove → continue” and said L402 provides that loop over Lightning, while asking who is building paid APIs, agent wallets and tooling. The post identifies a direction for automated payments, but reports no production deployment, users or settled-flow data.
The grassroots stack remains lightweight and directory-led. Current posts repeatedly pair a Blink address or paycode with a BTC Map listing: Bitcoin Chama listed meshack100@blink.sv, and Bitcoin Karoo listed Beans@blink.sv. Viwa’s BTC Map record shows Lightning acceptance and associates the business with Bitcoin Dada Nairobi, The Core, Bitcoin Nairobi and BitBiashara. This improves the visibility of spendable endpoints, but the promotion posts do not establish processor throughput, uptime or repeat transactions.
Regulatory Landscape
Dominican Republic — legislative pause, not a documented payment-law change. Bitcoin Dominicana says Bitcoin regulation has stalled in Congress while merchants, users and communities continue building, and links to coverage of the stalled projects. The post supplies no bill text, legal-tender change, tax rule or payment-compliance consequence; the defensible regulatory signal is political delay alongside continued private-sector experimentation.
Cross-border payments — advocacy rather than implementation. Tando invited PAPSS Africa to discuss what it called a serious approach to solving cross-border payments, but made the offer through direct messages rather than announcing a program or integration.
Usage Metrics
The period’s numbers are useful but not comparable as a payment-adoption series:
- Dominican Republic: the BTCPay guide claims that more than 100 Dominican businesses already accept Bitcoin. This is a local guide’s stated merchant-base figure, not an independently measured network statistic.
- Bitcoin Ekasi: 10 enrolled Diploma students, 31 attendances and 15,500 sats in learning rewards; the same update says only that “some” graduates paid restaurant meals, without giving a count or value.
- Cuba: 25,000 sats were advertised as tournament prizes. That is a community-event allocation, not transaction volume.
- Event-level payment evidence: the current posts report a haircut, a charging cable, soap and restaurant meals, but provide no aggregate count, amount or repeat-use rate.
Emerging Markets
The geographic and sector mix is broadening even though the measurements remain thin. The Caribbean combines a Dominican merchant-infrastructure push with Cuban travel acceptance and a sats-based community gaming event. African channels show Bitcoin reaching restaurants and education-linked spending in the Bitcoin Ekasi network, a barber in Calabar, an internet café in Randfontein, a Nairobi-linked accessories merchant and household-goods purchases. The practical significance is that the use cases are ordinary, low-ticket commerce rather than only education or promotional acceptance.
The cross-border angle is still prospective. Tando’s PAPSS invitation points to a possible Bitcoin payment discussion for African corridors, but the source contains no remittance flow, pilot, partner commitment or completed transaction.
Adoption Outlook
This period adds more concrete spending examples to the existing grassroots acceptance pattern: restaurant meals, a haircut, a charging cable and soap sit alongside published Lightning endpoints. At the infrastructure layer, Dominican BTCPay guidance offers merchants a browser-based point of sale and a path to self-controlled on-chain receipts, while L402 represents a still-formative route for machine-to-machine payments.
The constraint is measurement: the largest number is a guide’s claim about Dominican merchants, Ekasi’s figures measure education activity, and Cuba’s sats figure is a prize pool. The defensible conclusion is broader merchant discoverability and more varied real-world use, not yet a measured increase in live Bitcoin payment volume.
BTCPay Server
Praia Bitcoin Brazil ⚡
Bitcoin Dua
Major Adoption News
Agbozume — a promoted merchant endpoint, not confirmed new onboarding. Bitcoin Dua posted the Blink address senanustore@blink.sv and a BTC Map listing for Sena Store. The listing places the store on Amukoe Avenue and shows Lightning, Bitcoin and contactless acceptance, but also flags the location as needing a survey. BTC Map activity says BitcoinDua created and updated the listing five months ago. The business-impact signal is improved discoverability through a lightweight Lightning endpoint, not evidence of a newly onboarded merchant, a completed payment or payment volume.
El Salvador — Bitcoin-funded dental care continues and plans to expand. BitcoinSmiles says 2,971 Bitcoiners raised 1.97 BTC for dental care, and that the bitcoin is still paying for care; the initiative plans a second treatment room in Santa Ana. This is donation-funded service delivery rather than retail acceptance, but it is a concrete recurring payment use case with a stated expansion path. The source does not provide payment frequency or current-period funding figures.
Payment Infrastructure
Global machine-to-machine payments — the strongest technical signal is reproducible testing, not live usage. Lightning Enable reported 22 L402 challenge/verify tests passing, with 1,000-, 100,000- and 1-million-run tests completed and reconciled. Its isolated regtest Lightning settlement suite completed 30,000 consecutive paid flows and 42,562 total settled payments with zero failures. The project describes the target as an agentic-commerce stack combining scalable L402 authorization, scoped access and real Lightning settlement. This raises confidence in the repeatability of automated payment flows, but the regtest setting and self-reported benchmark do not establish production throughput, user demand or network-wide reliability.
Self-hosted merchant infrastructure — BTCPay Server moved closer to its next release. BTCPay released v2.4.3-rc6 and said it should be the final release candidate before the fully open-source v2.4.3 release, planned later in the week; operators were directed to update through Server Settings > Maintenance. The preceding rc4 notice characterized the branch as a security update, recommended upgrading, and flagged NFC as opt-in with the Phoenixd plugin temporarily incompatible. The current signal is therefore release hardening and operator maintenance, not a new checkout capability.
Brazil — a local Lightning node is being retired. Praia Bitcoin said it was shutting down one of Brazil’s oldest Lightning nodes while preparing the project’s “legacy,” but explicitly said it was not giving up on Bitcoin. The post supplies no replacement, capacity measure or payment-service impact, so this is best read as a local infrastructure transition rather than evidence of a national pullback.
Regulatory Landscape
No direct regulatory development affecting Bitcoin payment legality, tax treatment or legal-tender status is included from the grounded current-period items reviewed.
Usage Metrics
The period’s quantitative signals are useful but not comparable as a payment-adoption series:
- Lightning Enable: 22 protocol tests; 1,000/100,000/1-million-run reconciliations; 30,000 consecutive paid flows; 42,562 settled payments; zero failures. These are isolated engineering benchmarks, not live-network transaction volume.
- BitcoinSmiles, El Salvador: 2,971 donors and 1.97 BTC raised for care. This is a cumulative program-funding measure, not a merchant-adoption rate.
- BitBiashara: 47 Coffee Hangouts and 47 Bitcoin conversations over one year. This measures recurring community outreach, not payment count or merchant throughput.
- Sena Store, Agbozume: the current post supplies an endpoint and directory record but no transaction amount, count or repeat-use measure; the directory’s survey warning further limits its use as a verified adoption statistic.
Emerging Markets
Bali — merchant onboarding is being organized as a recurring local program. Bitcoin House Bali’s September schedule includes community meetups, a hands-on beginner workshop, a Bahasa meetup and a dedicated “Bitcoin for merchants onboarding session.” This is a clear grassroots pipeline for expanding acceptance, but it remains a planned training activity: no merchants, payment processor, transaction count or implementation result is stated.
Kibera — wallet-led education is positioned as the bridge to first use. Afribit Kibera says its sequence is “Education → Understanding → Adoption → Usage” and that it introduces first-time users to Blink and Fedi as simple wallets. The model lowers the first-use barrier in a community setting, but the post reports neither completed payments nor merchant growth.
El Salvador — local-business adoption is being addressed through practical discussion. Bitcoin Berlin SV said its Monday Meeting covered common questions about using Bitcoin and how local businesses can adopt it. A linked discussion framed the distinction as Bitcoin circulating through payment interactions rather than sitting unused in a wallet. This is demand formation and merchant education, not evidence of a quantified rollout.
Adoption Outlook
The period adds depth more than scale. Grassroots access is visible through the Agbozume Blink/BTC Map endpoint, planned merchant onboarding in Bali, and wallet- and education-led pathways in Kibera and El Salvador. In parallel, Lightning Enable’s clean isolated settlement benchmark shows that machine-payment infrastructure is being tested with more rigor than a demonstration alone.
The limiting evidence is equally concrete: the Agbozume listing needs surveying and predates the current post by five months, the largest payment count is from regtest, and the other numbers count donors or conversations rather than purchases. The defensible conclusion is expanding enablement and experimentation—not yet measured live merchant growth or geographically broad Lightning payment volume.
Bitcoin Anambra
Bitcoin Aves
BitcoinEkiti
Major Adoption News
The strongest signal is a cluster of reported everyday payments and one explicit earn-to-spend loop across community networks. The evidence is transaction-level or merchant-level, not a countrywide rollout.
South Africa — rewards tied to local spending. Bitcoin Ekasi’s TSK Rewards says children at The Surfer Kids who reach 70% or more monthly attendance earn Bitcoin sats, then can save or spend them at local Bitcoin-accepting merchants, including for groceries. The post says this allows sats to circulate within the township economy and support local businesses. The linked BTC Map record is Jabulani Shop 3 on D. Elles Street, Mossel Bay Local Municipality 6500; it lists Lightning and contactless acceptance and links the listing to the Bitcoin Ekasi community. This is a stronger circular-economy design signal than a one-off acceptance post, although the source gives no reward amount or spending count.
West Africa — completed food and service payments. In Calabar, Nigeria, Bitcoin Calabar reported paying less than 0.00001 BTC at Food and Wine Shop and said the payment was instant, with no third party, central bank or bank involved. BTC Map lists the food retailer at 35 MCC Road, Calabar 540222, with Bitcoin and Lightning acceptance icons and contactless payment. This is the clearest quantified payment event in the period, but it is not a transaction-volume measure.
In Akatsi, Ghana, Bitcoin Aves reported paying sats for a haircut at De-Palace Barbershop, supplied a Blink Lightning paycode and linked BTC Map. The linked record calls the business De Palace Haircuts, places it on Badzi Street in Akatsi, and lists Lightning acceptance. The post demonstrates a completed personal-service payment rather than merely advertising acceptance; the directory record itself is dated 26 October 2025, so it should not be counted as a newly onboarded merchant without further confirmation.
Additional acceptance endpoints. In Awka, Nigeria, Sario Eventers promoted buying a hair extension with Bitcoin, providing a Blink address and BTC Map listing. The map record lists Awka, Bitcoin and Lightning acceptance icons, and the Bitcoin Anambra community. Bitcoin Ekiti likewise promoted paying sats for everyday essentials and linked a Blink address to KJ Multipurpose Store; the captured record lists Bitcoin, Lightning and contactless acceptance but does not provide a city or street address. These are acceptance and discoverability signals, not reported completed transactions.
Nairobi-linked food spending. BitBiashara reported a customer paying in Bitcoin for a samosa at Haven food court through Haven@blink.sv. BTC Map lists Haven as a Lightning merchant and associates it with Bitcoin Dada Nairobi, The Core, Bitcoin Nairobi and BitBiashara, but provides no street address in the captured record. It is concrete food-payment evidence, while the dated verification record makes it weaker evidence of a new merchant launch.
Payment Infrastructure
The recurring operating pattern is lightweight: a Blink Lightning address as the payment endpoint, a BTC Map listing for discovery, and often the #Spedn label. The pattern appears in the Calabar food payment, the Sario Eventers promotion, the De Palace haircut and the Haven samosa payment. It gives local organizers a simple way to publish where Bitcoin can be spent, but the current evidence does not establish processor-wide throughput, fees, uptime or settlement performance.
A separate Cuba-linked enablement signal is LaIslaBTC’s planned practical on-chain workshop. The announced session covers Sparrow Wallet installation, secure seed creation, UTXOs and construction of a Bitcoin on-chain transaction. The organizers say it is being held with Cuba_BTC and VivaBitcoin at Micro 70 on 21 August. This supports self-custody and transaction literacy, but it is a scheduled training event rather than evidence of a live payment deployment.
Regulatory Landscape
United States — adjacent stablecoin policy, not a Bitcoin-payment rule. The policy signal visible in the period concerns proposed Treasury rules under the GENIUS Act for stablecoins, with a 60-day public-comment period; the post frames the proposal around strengthening the dollar and U.S. crypto policy. Because it addresses stablecoins rather than Bitcoin payment acceptance, settlement, reporting or tax treatment, it provides no direct Bitcoin-payment regulatory change for this tracker.
Usage Metrics
The usable numbers are event-level or community-level rather than network-wide:
- Calabar: less than 0.00001 BTC for a reported Food and Wine Shop payment, described as instant.
- Mossel Bay: a 70% monthly attendance threshold for children to earn sats through TSK Rewards; no reward amount or redemption count is stated.
- BitBiashara: 47 Coffee Hangouts in one year, bringing merchants, Bitcoiners and newcomers together. This is a distribution and onboarding metric, not payment volume.
Geographically, the reported acceptance and payment signals span Calabar and Awka in Nigeria, Akatsi in Ghana, Mossel Bay in South Africa, a Nairobi-linked network, and the Bitcoin Ekiti community. The merchant records also caution against turning current posts into an onboarding count: Jabulani Shop 3 is dated 19 December 2025, De Palace Haircuts 26 October 2025, KJ Multipurpose Store 22 November 2025, and Haven 23 June 2025 in their verification metadata. The defensible measure is reported use and endpoint reach, not repeat frequency, aggregate transaction volume or merchant-growth rate.
Emerging Markets
The West African pattern is practical and low-ticket: food retail in Calabar, hair extensions in Awka, haircuts in Akatsi and everyday-store spending in the Ekiti network. Southern Africa adds an incentive mechanism: Bitcoin Ekasi connects attendance rewards to local merchant spending, giving Bitcoin a stated role in a township circular economy rather than only as a payment option.
The Nairobi-linked evidence combines a food-court payment with a community network that includes merchants and Bitcoin educators. BitBiashara’s 47-session run shows sustained local onboarding infrastructure, while LaIslaBTC’s Cuba-linked workshop extends the model into hands-on self-custody and on-chain transaction education. Across these markets, the adoption mechanism is organizer-led distribution into ordinary sectors—food, personal services, retail and youth programs—rather than a documented national payments initiative.
Adoption Outlook
Bitcoin payment viability is advancing through visible use cases: small food and personal-service purchases in Nigeria, Ghana and a Nairobi-linked network, plus a South African program designed to earn and spend sats locally. The enabling layer remains simple—Blink Lightning endpoints paired with BTC Map discovery—while the main analytical constraint is measurement: several directories predate the current posts or remain verification-dependent, and the period supplies no network-level payment series. The defensible read is broader endpoint visibility and experimentation, not yet measured ecosystem growth.
Bitcoin Karoo
BTC Shule
Bitcoin Victoria Falls
Major Adoption News
Blink’s weekly brief reports a first restaurant payment in Mossel Bay: a visitor paid at Blaize & Barrel using a self-hosted BTCPay Server and a Bolt Card. The source frames it as a single-restaurant payment, making it concrete proof of use rather than evidence of transaction scale.
The clearest current pattern is community-scale endpoint use. Bitcoin Victoria Falls posted “Getting some snacks with Bitcoin” and supplied firstspringenterprise@blink.sv; the linked BTC Map page renders the merchant as First Sping Enterprise at John Hunt Way, Livingstone, shows Lightning acceptance, and offers a Verify Location action. The listing is associated with Bitcoin Victoria Falls and records creation by Bitcoin Diary 18 days ago.
A second Victoria Falls post supplied gmgeneraldealers@blink.sv; BTC Map names JM General Dealers at Dambwa Central Market, Livingstone, and displays Lightning and Bitcoin acceptance icons plus contactless payment. Its page retains a Verify Location action dated 21 March 2025, so the current post is better read as a community endpoint showcase than proof of a newly verified onboarding.
BTC Shule reported a more explicit household transaction: a mother bought flour and soap with Bitcoin sats via Fedi at yanusi7@blink.sv. The linked record names Kwa Jiyeve in Winteko, shows Lightning acceptance and BTC Shule attribution, and asks users to verify the location; its activity says the listing was created a year ago. That is direct payment-use evidence, but not a merchant-growth count.
Bitcoin Karoo’s #spedn post points to Herries, which BTC Map places at 5 Schoeman St, De Rust 6650, with Lightning and Bitcoin acceptance icons plus contactless payment. The record is attributed to Bitcoin Karoo and also carries a Verify Location action. Across the set, Blink addresses paired with directory listings form a lightweight path to local acceptance, but verification and activity metadata make endpoint reach—not newly onboarded merchants—the defensible measure.
Payment Infrastructure
The principal infrastructure risk is a BTCPay security failure. Blink’s current weekly brief says BTCPay confirmed that a critical vulnerability present in every prior version had been actively exploited, allowing an unauthenticated attacker to obtain LND macaroon credentials and move funds. It describes the issue as specific to LND deployments, says on-chain and hot wallets were unaffected, and calls for BTCPay 2.4.2 and LND 0.21.1 updates. This is an operator-security and continuity problem, not evidence that Lightning settlement as a whole failed.
The offsetting deployment signal is Blink’s BTCPay plugin v1.1.0: a merchant can connect a non-custodial Blink Lightning address without running a node or holding an API key and receive on mainnet. The tradeoff is material—receiving is receive-only, with no refunds or payouts through outbound Pull Payments, and settlement is detected by polling, usually within seconds and occasionally about a minute.
Lightning’s payment surface is also extending to machine-to-machine access. Lightning Enable says L402 can authorize a small paid API request without a new account, card on file or permanent profile, using per-request payment to reduce account friction. The post describes a payment model, not deployment or usage volume.
Continuity pressure is visible elsewhere. Cuba’s non-custodial P2P Lightning exchange lnp2pBot halted activity indefinitely after attacks and a lack of resources to keep facing AI-assisted attackers; its operators said pending payments would be resolved and losses absorbed, and the source explicitly says the shutdown was not a government ban. Wallet of Satoshi’s migration is another merchant-impacting change: new invoice creation is already disabled in the US, EU, Australia and New Zealand, the rest of the world is scheduled for the end of September, and WoS Point of Sale payments stop when each region switches. The old wallet can still send balances until 30 June 2027, while the replacement is self-custodial.
The security burden is measurable even where payment failure is not. A Bitcoin Red Team scan covered 501 projects and produced 7,958 findings, including 1,280 rated high or critical; the brief characterizes these as defensive findings rather than payment failures.
Regulatory Landscape
South Africa is the period’s clearest regulatory signal. Blink’s brief describes a National Treasury/SARB draft published on 3 August, with comments due 30 September, that would require offshore crypto payments to be declared through authorised providers and reported to SARB’s FinSurv. It would treat transfers from local providers such as Luno or VALR to an offshore network or a self-custody wallet as cross-border transactions within existing R2 million Single Discretionary and R10 million Foreign Capital ceilings. The proposal is explicitly a draft, covers crypto broadly rather than Bitcoin specifically, and describes purely domestic transfers between local providers as non-reportable.
For payment viability, this is potential compliance friction rather than an enacted Bitcoin rule. MoneyBadger’s CEO called the restrictions “disproportionate and poorly justified” and warned they could push legitimate cross-border crypto payments back toward conventional banking; that is an interested party’s assessment, not a regulatory finding.
Usage Metrics
The current evidence supplies two explicit spending reports—snacks in Livingstone and flour and soap bought through Fedi—and two additional merchant-endpoint posts for JM General Dealers and Herries. The posts provide no sat value, transaction count, repeat-use frequency or aggregate merchant-adoption rate, so they support event-level usage and geographic reach rather than a growth series.
The available numeric signal is instead infrastructural: the 501-project, 7,958-finding security scan. It should not be repurposed as a payment-usage metric.
Emerging Markets
The emerging-market pattern is community-led distribution rather than a documented national rollout: local organizers pair Blink Lightning addresses, BTC Map discovery and practical goods or restaurant payments. The Livingstone endpoints, the BTC Shule household purchase in Winteko and the Bitcoin Karoo listing in De Rust show the same basic model while differing in verification status and evidence of actual use.
MOTIV Perú announced “Bitcoin City Adoption in Huanchaco” after saying this year’s Copa Bitcoin Surfing Edition would not take place; it also previewed a volleyball edition. The Huanchaco initiative is a relevant city-level adoption signal, but the post gives no merchants, payment processor or implementation timetable, so its business impact remains unquantified.
Adoption Outlook
The payment-access layer is advancing at the edge: merchants and households are using Blink-linked Lightning endpoints, a non-custodial BTCPay receiving path lowers infrastructure requirements, and L402 proposes per-request machine payments.
The limiting signal is equally concrete. BTCPay’s exploited vulnerability, lnp2pBot’s indefinite shutdown, Wallet of Satoshi’s regional POS migration and the unverified or aged directory records show that custody, patching and data quality remain part of payment viability. The defensible conclusion is expanding access and experimentation—not yet measured ecosystem growth.
Bitcoin Sisonke
Calabar Bitcoin Club
₿itBiashara
Major Adoption News
The clearest current signal is ordinary food spending through community merchant networks, rather than a country-level rollout. The period contains posts describing dinner in Calabar, a family-food purchase at Grandsmatt, and fruit purchases in the Bitcoin Sisonke network.
At Chef Green Signature Local Cuisine Hub, Atekong Junction, Calabar, Bitcoin Calabar describes paying sats for dinner as a “daily norm” and supplies the Blink handle chefgreensignature@blink.sv. The linked BTC Map record displays Lightning and Bitcoin acceptance indicators, lists evening opening hours, and retains a “Verify Location” prompt. This is the strongest repeat-use signal in the set—an account’s characterization of routine spending, not a reported transaction series.
In a Nairobi-linked community network, BitBiashara posted Shakillah buying food for her family at Grandsmatt, using the #spedn tag and Dachar@blink.sv. The attached record displays Lightning acceptance and connects Grandsmatt to Bitcoin Dada Nairobi, The Core, Bitcoin Nairobi and Bitbiashara. It shows a location-verification prompt and community links but no street address in the displayed details. The post is therefore a concrete household-spending use case, but not proof of a newly onboarded or precisely located merchant.
Bitcoin Sisonke framed fruit purchases at a community merchant in Randwest 1759 as “Bitcoin as everyday money,” enabled by Lightning and the Blink address Mucambe@blink.sv. The linked BTC Map record calls the merchant “Mkambi,” lists Folly Ledwaba Street, Randwest 1759, shows Lightning acceptance, and attributes the listing to Proof of Bitcoin and Bitcoin Sisonke. The Mucambe/Mkambi spelling mismatch and the record’s verification prompt mean the merchant identity should be checked before using it in an adoption count.
Payment Infrastructure
The period’s infrastructure signal is deployment at the edge: #SPEDN-tagged posts repeatedly pair Blink-linked payment handles with BTC Map merchant discovery. The examples are chefgreensignature@blink.sv in Calabar, Dachar@blink.sv at Grandsmatt, and Mucambe@blink.sv in the Sisonke post; the latter explicitly attributes everyday community spending to Lightning. This combination gives local merchants a human-readable endpoint and a discoverable listing, but the current evidence does not provide processor-wide volume, fee, speed or reliability measurements.
Regulatory Landscape
No qualifying payment-regulatory item surfaced in the reviewed material. The actionable evidence was instead merchant-level acceptance and use—dinner in Calabar, family food at Grandsmatt and fruit purchases in the Sisonke network—rather than a legal-tender, licensing, tax or transaction-rule announcement.
Usage Metrics
The available metrics are event-level. The three posts report a family-food purchase, a stated daily dinner norm and community fruit buying, but give no sat or fiat amount, transaction count, merchant-adoption rate or growth series.
The linked directory records also caution against treating these as new-merchant counts. Grandsmatt is dated 24 November 2025 and marked for location verification, with its activity shown as nine months ago. Chef Green’s record is dated 7 May, is also marked for verification, and shows creation a year ago and an update three months ago. Mkambi is dated 21 November 2025, marked for verification, and shows activity nine months ago. The defensible measurement is therefore reach and reported use, not merchant growth or payment volume.
Emerging Markets
The strongest geographic pattern is community-led distribution across Calabar, Nairobi-linked groups and Randwest, with food and produce serving as the practical use cases. The merchant posts combine local organizers, Blink-linked payment addresses, Lightning and directory visibility rather than relying on a national payments program.
An adjacent onboarding signal comes from Bitcoin Ekiti Cohort 2, whose current recap says the session examined everyday Bitcoin use and the self-custody principle “not your keys, not your coins.” It supports education as part of the distribution model, but reports no merchant, payment or usage count.
Adoption Outlook
The current momentum is visible as repeated small, ordinary purchases—food, dinner and fruit—using the same lightweight Lightning/Blink and merchant-directory pattern across community networks. The limiting signal is equally concrete: the posts provide no aggregate volume, directory records are old or still unverified, and one merchant name does not match between the post and the listing. The period supports expanding payment access and claimed recurring use, not yet measured ecosystem growth.