# Grassroots Bitcoin Spending Expands While the Payment Stack Hardens Under Attack

*By Bitcoin Payment Adoption Tracker • August 9, 2026*

The period pairs completed Bitcoin purchases and new community merchant endpoints with continuing BTCPay fallout, AI-led security work, and a live L402 usage signal.

## Major Adoption News

**Community use produced several concrete point-of-sale payments rather than acceptance claims alone.** Bitcoin Ekasi described a first visit to Blaize & Barrel where the visitor paid with Bitcoin using a self-hosted BTCPay Server and a Bolt Card; the post gives no amount, location, or repeat-use measure. [^1] BTC Shule reported that a mother bought soap with Bitcoin through Fedi, linking the merchant’s Blink address and BTC Map record; the linked record identifies Kwa Jiyeve in Winteko, shows a Lightning acceptance icon, and associates the listing with BTC Shule. [^2][^3] In Calabar, a community post reported lunch paid over Lightning; the linked record identifies Chef Green Signature Local Cusine Hub at Atekong Junction and shows both Lightning and Bitcoin acceptance. [^4][^5]

These reports are stronger evidence of payment viability than directory listings or educational claims, but they remain isolated anecdotes: none states transaction value, frequency, or repeat use. [^1][^2][^4]

**New merchant onboarding continued in everyday food and retail.** Bitcoin Babies announced Bobo’s Chicken Bites as a new Bitcoin merchant in Kenya and supplied a Lightning address; its BTC Map record shows Lightning acceptance. [^6][^7] Bitcoin Dua’s post supplied a merchant Blink address for Agbozume; the linked record identifies Antitor Provision Store opposite Agbozume Market, shows both Bitcoin and Lightning acceptance, and ties the listing to the Bitcoin Dua community. [^8][^9] These are useful payment endpoints, but the announcements do not report completed transactions.

## Payment Infrastructure

**The BTCPay incident continued to create availability and remediation costs for operators.** A follow-up post reported that LunaNode had disabled access to all BTCPay instances it hosted until users upgraded, while another follow-up published two addresses linked to exploits of vulnerable BTCPay instances. [^10][^11] BTCPay’s advisory says the exploited path involved exposed LND `.macaroon` credentials; the risk applied specifically to LND deployments, while BTCPay’s on-chain and hot wallets were not affected. [^12] Version 2.4.2 also temporarily removed public LND API access on Docker deployments, preventing an external wallet such as Zeus from connecting through a BTCPay domain or Tor address. [^12] For merchants, patching therefore affects both custody risk and payment connectivity.

**Security work broadened from one emergency patch into ecosystem-wide hardening.** Blink’s weekly brief said AI-assisted attacks forced Boltz offline, briefly took Satora down, and prompted BTCPay’s emergency patch; it also listed AI red-team scans across 150 repositories. [^13][^14] A related Bitcoin Red Team update said 25 developers had worked for 108 hours, scanning 501 projects and producing 7,958 findings, including 1,280 rated high or critical; 29.4% of findings had been reported to projects. [^15][^16][^17] These figures measure defensive activity, not payment adoption, but they make software assurance a direct operating concern for self-hosted merchants and Lightning services.

## Regulatory Landscape

No substantiated country-specific legal-tender, tax, licensing, or transaction-rule change was surfaced in the reviewed current-period material. The practical constraint this period was infrastructure security and service availability rather than a reported change in payment law.

## Usage Metrics

Lightning Enable reported that, over the previous 30 days, its protected routes served **18,947 payment challenges across 147 resources**, describing L402 as running in production rather than as a demo. [^18] This is a meaningful payment-gate activity signal, but it is not a disclosed count of settled Bitcoin transactions, sat volume, or active payers.

Blink’s weekly brief listed BTC Map at **26,575 merchants**. The post provides no methodology or active-status definition, so the figure is best treated as a directory snapshot rather than a measure of transacting merchants. [^14] The period’s direct-use evidence remains event-level: one restaurant payment, one soap purchase, and one lunch payment, with no amounts or aggregate transaction counts reported. [^1][^2][^4]

## Emerging Markets

**Local food, household retail, and community education are the clearest expansion pattern.** Kenya adds a chicken takeaway with a Lightning endpoint; Agbozume adds a provision store accepting both Bitcoin and Lightning; Winteko adds a BTC Shule-linked household purchase and Lightning merchant listing; and Calabar adds food-service use with both rails listed. [^6][^7][^9][^2][^3][^4][^5] The pattern shows payment access being attached to ordinary local commerce, but not yet measured scale.

**De Rust / Bitcoin Karoo is building an adoption pipeline around a venue.** De Rust Tennisklub was presented as the hub for a Bitcoin Karoo Education Block, combining a bitcoin-only tennis club, a children’s tennis and Bitcoin academy, entrepreneurial education, and a bitcoin-only coffee shop. [^19] This links education, a local merchant setting, and community infrastructure; it is a pipeline for future usage rather than evidence of current payment volume.

## Adoption Outlook

The period supports a stronger grassroots-use signal: Bitcoin was reported in completed restaurant, household, and lunch purchases, while new food and retail endpoints appeared in Kenya, Agbozume, Winteko, and Calabar. [^1][^2][^4][^6][^9] At the same time, BTCPay access restrictions, temporary API changes, and AI-linked security incidents show that reliability and operator security remain binding constraints on self-hosted payment infrastructure. [^10][^12][^13] The defensible conclusion is broadening experimentation with several instances of real use—not scaled or repeat adoption, for which the corpus still provides no aggregate volume or retention measure. [^18][^14][^1][^2][^4]

---

### Sources

[^1]: [𝕏 post by @BitcoinEkasi](https://x.com/BitcoinEkasi/status/2086028038920122746)
[^2]: [𝕏 post by @btcshule](https://x.com/btcshule/status/2086050178230866362)
[^3]: [Kwa Jiyeve - BTC Map](http://btcmap.org/merchant/26332)
[^4]: [𝕏 post by @BitcoinCalabar](https://x.com/BitcoinCalabar/status/2086172253205524786)
[^5]: [Chef Green Signature Local Cusine Hub - BTC Map](https://btcmap.org/merchant/25058)
[^6]: [𝕏 post by @BtcBabies](https://x.com/BtcBabies/status/2086071248111452460)
[^7]: [Bobo's Chicken Bites - BTC Map](https://btcmap.org/merchant/41957)
[^8]: [𝕏 post by @bitcoin_dua](https://x.com/bitcoin_dua/status/2086080748868477267)
[^9]: [Antitor Provision Store - BTC Map](http://btcmap.org/merchant/36107)
[^10]: [𝕏 post by @pavlenex](https://x.com/pavlenex/status/2085959835653161329)
[^11]: [𝕏 post by @pavlenex](https://x.com/pavlenex/status/2086012989262401863)
[^12]: [𝕏 article by @BtcpayServer](https://x.com/i/article/2085838133782888449)
[^13]: [𝕏 post by @blinkbtc](https://x.com/blinkbtc/status/2086106996181262766)
[^14]: [𝕏 post by @blinkbtc](https://x.com/blinkbtc/status/2086107045149679694)
[^15]: [𝕏 post by @callebtc](https://x.com/callebtc/status/2086220411084103707)
[^16]: [𝕏 post by @callebtc](https://x.com/callebtc/status/2086220415207141829)
[^17]: [𝕏 post by @callebtc](https://x.com/callebtc/status/2086220430860255269)
[^18]: [𝕏 post by @lightningenable](https://x.com/lightningenable/status/2086292688647684381)
[^19]: [𝕏 post by @BitcoinKaroo](https://x.com/BitcoinKaroo/status/2085974593928388875)