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
Pavlenex
Bitcoin Berlín SV 🇸🇻
jarolrod
Major Adoption News
Concrete spending signals clustered around ordinary food and grocery commerce. Bitcoin Sisonke labeled a transaction as “a purchase powered by Lightning,” supplied the Blink address Mrwebisimphiwe@blink.sv, and linked a BTC Map record; that record identifies T-Junction fast food in Randfontein and shows Lightning acceptance. BTC Shule likewise reported a biscuit paid with Fedi, alongside a Blink address and BTC Map listing. The linked Kwa Innocent record shows Lightning acceptance but is marked as needing a survey, and it does not provide a street location.
Bitcoin Victoria Falls posted two spending-use entries: one described using Bitcoin as everyday money at Fai’s Kiosk, whose linked record places it on Mokambo Road in Livingstone; another described using Bitcoin at a local market, while the linked Andrews Grocery record identifies City Market in Livingstone and shows both Lightning and BTC acceptance. Bitcoin Karoo made a similar paid-goods claim for Doornkraal Padstal; its linked record places the business on Stompdriftdam Road in De Rust and shows both Lightning and BTC acceptance.
Berlín, El Salvador added a new produce-retail onboarding signal. Bitcoin Berlín SV welcomed La Estación de Frutas y Verduras as a new Bitcoin business in the town. The post does not state a payment processor, transaction, or usage measure, so it is best treated as merchant onboarding rather than completed-use evidence.
Payment Infrastructure
The period’s practical integration pattern was lightweight rather than a new processor launch: community posts paired Blink payment addresses with Lightning acceptance and BTC Map listings, while the BTC Shule example said the purchase was made through Fedi. Sisonke described its Lightning purchase as “easy and instant,” which is an attributed user-facing claim rather than an independently measured performance result.
BTCPay Server’s security response remained active. A current-period post reported “further drains” and urged operators who had not updated to do so. BTCPay’s response also asked affected users to send information to security@btcpayserver.org, with the on-chain addresses receiving stolen funds described as especially useful; a follow-up repeated that request. The infrastructure story this period was therefore continued incident triage and operator remediation, not a newly reported payment capability.
Regulatory Landscape
No substantiated country-specific legal-tender, tax, licensing, or transaction-rule change appeared in the payment-focused material reviewed for this period. The actionable change surfaced was operational security: BTCPay posts focused on updates, reported drains, and forensic information gathering.
Usage Metrics
The available usage evidence is event-level rather than statistical: one post explicitly labels a Lightning purchase, another says a biscuit was paid with Fedi, Victoria Falls supplies two spending-use posts, and Karoo describes fresh goods paid with Bitcoin. None of these posts states a payment amount, sat volume, aggregate settlement count, unique-payer count, or repeat-use rate, so they cannot support an adoption-rate estimate.
The linked directory records also show why merchant-listing totals should not be treated as active-usage metrics. The Kwa Innocent entry is explicitly flagged for survey, while Fai’s Kiosk has a location record but no Accepts section or payment icon in the supplied page.
Emerging Markets
The clearest emerging-market pattern is expansion into small, everyday venues: fast food in Randfontein, grocery and market commerce in Livingstone, and a roadside padstal in De Rust, with the records showing a mix of Lightning-only and dual Lightning/BTC acceptance. This is a broader sector signal than a single tourism or education announcement, but the evidence still consists of community-reported transactions and merchant listings rather than measured throughput.
El Salvador adds a separate grocery-sector signal through La Estación de Frutas y Verduras in Berlín. The BTC Shule example extends the same local-retail pattern, although its linked record identifies the community and payment rail without supplying a geographic address, limiting country-level comparison.
Adoption Outlook
This period strengthens the case for breadth of grassroots Bitcoin use: multiple posts describe or present payment activity across Randfontein, Livingstone, De Rust, and the BTC Shule community, while Berlín adds a new produce-business signal. The counter-signal is that BTCPay operators were still handling drain reports and collecting destination addresses from affected users. The defensible conclusion is expanding payment experimentation with unresolved measurement and operational-security risk—not yet measured payment scale or repeat adoption.
BTC Shule
Bitcoin Ekasi
Pavlenex
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. 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. 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.
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.
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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
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. 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. 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. 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. 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.
Bitcoin Berlín SV 🇸🇻
₿itBiashara
Mavapay
Major Adoption News
Bali, Indonesia — Bali Honey entered a Bitcoin-linked closed-loop merchant network. Bitcoin House Bali announced Bali Honey as a new merchant in the Fedi closed-loop system, described it as “100% raw, 100% bitcoin,” and identified the business as belonging to a My First Bitcoin graduate. This is a merchant-onboarding signal in a community payment loop, not evidence of transaction scale.
Nairobi-linked community listing — Haven food court generated a direct sats-spend report. BitBiashara posted the venue’s Blink address and BTC Map listing, saying a customer had “quenched her thirst on Sats.” The linked BTC Map record shows Lightning acceptance, links the venue to Bitcoin Dada Nairobi, Bitcoin Nairobi, and Bitbiashara, and displays a 23 June 2025 verification-location date. The reported purchase is stronger than an acceptance listing alone, but it remains a single anecdote and the directory record is not current.
Berlín, El Salvador — local tourism was offered with Bitcoin payment. Bitcoin Berlín SV listed a Finca La Cruz coffee tour and a Sacred Cacao & Cave Tour at $15 each and said visitors could pay in Bitcoin; a current-period reminder said transportation was covered and reservations were being taken by direct message. This extends payment acceptance into bookable tourism, although the posts do not report bookings or settlement volume.
Faith’s store, location not stated — a community payment was demonstrated through Blink. BitEduhub showed its programs manager enabling a payment at Faith’s store using the Blink wallet and the address valfay@blink.sv. It is direct-use evidence, but the post gives no amount, frequency, or merchant-location detail.
Payment Infrastructure
Global BTCPay ecosystem — an exploited LND credential flaw became the period’s dominant payment-infrastructure event. BTCPay Server’s advisory says version 2.4.2 fixes a critical vulnerability in every prior version, including release candidates. An unauthenticated remote attacker could obtain LND .macaroon credential files, take control of an LND node, and move funds; BTCPay confirmed that the vulnerability had been exploited and that funds were stolen.
The final scope is narrower than the initial emergency messaging: the credential risk applies specifically to LND deployments; other Lightning implementations and non-Lightning deployments are not exposed to this risk, while BTCPay’s on-chain wallets, including hot wallets, were not affected. Funds in LND’s own on-chain wallet may still be at risk. LND operators were instructed to update BTCPay Server to 2.4.2 and LND to 0.21.1, take the server offline if they could not update, and inspect payments, channel closures, peers, and balances for unauthorized activity. The update automatically regenerates macaroons, though separately managed access paths require separate credential rotation.
The mitigation also changed payment connectivity: 2.4.2 temporarily removes public LND API access on Docker deployments, preventing external wallets such as Zeus from connecting through a BTCPay domain or Tor address until the option is considered safe to restore. Bitcoin Coast reported that all of its BTCPay stores had been updated and offered free help setting up direct-to-wallet processing, while Bitcoin Ekasi showed a local operator updating at 10 p.m. and urged other operators to update immediately. For merchants, remediation therefore became both a security requirement and a payment-availability event.
Machankura — receiving and Lightning use were temporarily restricted. The service disabled Lightning spending and both on-chain and Lightning receiving while applying a fix, while on-chain spending remained functional. It later restored on-chain and Lightning spending but kept receiving disabled pending further monitoring.
Banxaas, location not stated — Lightning-channel capacity degraded before partial recovery. Banxaas warned that a technical problem could block incoming and outgoing Bitcoin transactions while its mobile-money service continued normally. It later said the channels were operational again but with reduced capacity and limits visible at exchange time.
Cross-border, regions not stated — Mavapay marketed Lightning settlement as a payment-rail proposition. It advertised real-time settlement across regions via the Lightning Network and invited demo requests. The post does not identify a live customer deployment, corridor, or transaction volume.
Regulatory Landscape
The current-period material reviewed yielded no substantiated country-specific legal, tax, licensing, or legal-tender change affecting Bitcoin payments. The actionable change was operational security in the payment stack, not a reported change in payment law.
Usage Metrics
The reviewed items provide event-level evidence rather than aggregate payment metrics. BitBiashara reported one customer spending sats at Haven food court, and BitEduhub showed one enabled payment at Faith’s store; neither post states a value, transaction count, or repeat-use rate. Bali Honey is described as a new merchant, but the announcement supplies no transaction data. The BTC Map record adds a Lightning acceptance marker, not a usage measure, and its displayed verification-location date is June 2025. No defensible sat-volume, fiat-volume, active-user, repeat-rate, or current merchant-growth estimate can be derived from this period’s evidence.
Emerging Markets
The strongest emerging-market signal is sectoral breadth rather than measured scale. Indonesia adds a closed-loop raw-honey merchant; an El Salvador community is attaching Bitcoin to paid coffee, cacao, and cave-tour experiences; and African community sources show food-service spending, a Blink payment at an unnamed store, and another Bitcoin-accepting merchant highlighted by Bitcoin Victoria Falls with a Blink tip address.
Ado-Ekiti, Nigeria — education is being positioned as a merchant-adoption pipeline. My First Bitcoin describes Bitcoin Ekiti’s structured training, merchant onboarding, workshops, and public education for students, entrepreneurs, artisans, and business owners; its stated aim is that participants can use what they learn. This is relevant infrastructure for future payments, but it is not a transaction or merchant-volume statistic.
Adoption Outlook
Grassroots payment use continued across food, tourism, community retail, and closed-loop commerce, with Blink, Lightning, Fedi, and direct Bitcoin payment signals appearing in different local models. At the same time, the BTCPay exploit, temporary API restrictions, Machankura’s receiving pause, and Banxaas’s reduced channel capacity show that secure and reliable payment infrastructure remains a binding constraint. The period supports breadth of payment experiments and some completed-use anecdotes, but not yet a defensible conclusion about payment scale or repeat adoption.
BitcoinEkiti
Bitcoin Victoria Falls
No Ack Dom
Major Adoption News
Mossel Bay, South Africa — Bitcoin Ekasi is showing a local earn-and-spend loop. Bitcoin Moon Fund sponsorship gives Bitcoin Diploma students sats rewards while they learn financial literacy; the project says the students spend those sats on everyday snacks via Lightning at Jabulani Shop No. 3 in Izinyoka, Joe Slovo, Mossel Bay. BTC Map lists Jabulani Shop 3 at D. Elles Street, shows Lightning/contactless acceptance, and associates it with Bitcoin Ekasi. This is stronger than a standalone acceptance listing because it connects a funding and education program to local retail spending, although it reports no transaction value or repeat-use rate.
Livingstone — a Bitcoin Victoria Falls post described merchant-to-merchant grocery spending. The post says a Bitcoin merchant was getting groceries from a fellow merchant, gives the Blink Lightning address dailyneedgroceries@blink.sv, and links BTC Map merchant 42122. The linked record names Daily Need Groceries on Mokambo Road, Livingstone, and associates it with the Bitcoin Victoria Falls community; its location was marked for verification “1 day ago.” The post is evidence of a reported grocery payment, but the directory record itself has no displayed “Accepts” section, so it should not be treated as independent confirmation of ongoing acceptance.
Service-sector coverage widened across additional African communities. In Ekiti, Bitcoin Ekiti posted ebonydud@blink.sv for dry-cleaning with sats; the linked Ebonydud record shows Lightning, on-chain Bitcoin and contactless acceptance, but no address. In Masimba, Bitcoin Chama’s “Bitcoin as everyday money” post links bosibori@blink.sv; BTC Map identifies the endpoint as Flo Salon on Keroka–Masimba Road and shows both Lightning and Bitcoin acceptance. In Agbozume, Bitcoin Dua promoted presosfoodanddrinks1@blink.sv; the linked listing identifies Preso’s Food and Drinks on Sonuto Road and shows Lightning and Bitcoin acceptance, though its last verification date is 1 January 2024. These are useful merchant endpoints, but the Masimba and Agbozume posts do not report completed transactions.
Payment Infrastructure
Cash App/Bitkey — bitcoin-funded bank payments were reported as a production test, not a launch. In response to a request for fee-free bitcoin bill pay using Cash App and Bitkey, Miles Suter said he was testing bitcoin-funded outbound ACH payments in production. He separately described a Cash App dollar-cost-averaging flow with no spread or fee, threshold-triggered on-chain withdrawals to Bitkey, and said it was being cut into the next release. The posts provide no coverage, limits, settlement timing or user-count data, so this is a payment-plumbing signal rather than evidence of a broadly available bill-pay product.
Lightning Enable is treating payment authorization as an ongoing security function. Following the recent COLDCARD disclosure, it said it reviewed dependencies, secret handling, payment authorization and failure paths, added a Security.md channel for user reports, and would continue testing, hardening and publishing fixes. The development matters to payment reliability, but it is a hardening response rather than a new merchant or processor integration.
Regulatory Landscape
South Africa — a draft cross-border framework could add reporting friction at the exchange/self-custody boundary. BitcoinZAR warned that transfers from local exchanges to offshore platforms or self-custody wallets could become reportable cross-border transactions, while the underlying Capital Flow Management Regulations remain unfinished; it said comments close on 30 September. BitcoinZAR’s advocacy page describes the underlying proposal as a joint National Treasury/South African Reserve Bank draft manual, published 3 August 2026. It says movements from a domestic Authorised Crypto Asset Service Provider to an offshore CASP or non-custodial wallet, or the reverse, would be reportable to the Financial Surveillance Department, while purely domestic transfers between local Authorised CASPs would be non-reportable. The same page says the draft classifies a transfer from a local CASP to one’s own hardware wallet as an export of capital and says returning funds from self-custody to a South African CASP would be non-permissible. These are proposed, contested rules—not a final payment regulation—but they could complicate users’ movement between custodial payment services, exchanges and self-custody.
Usage Metrics
The payment evidence is transaction-level and directory-level, not aggregate. The Livingstone post describes a grocery purchase but gives no amount, while the Mossel Bay report says students spend earned sats at a local shop without stating the number of students, payment count or spend. The Ekiti, Masimba and Agbozume items expose merchant endpoints and payment methods, but do not provide transaction volume or repeat-use data. The period therefore supports no defensible sat-volume, transaction-count, repeat-rate or merchant-growth estimate.
Directory freshness is uneven. Daily Need Groceries is marked “1 day ago,” while Jabulani Shop 3 is dated 19 December 2025, Flo Salon 4 December 2025, Preso’s Food and Drinks 1 January 2024, and Beans about Coffee in Oudtshoorn 25 May 2024. Those dates are useful directory-quality indicators, not measures of active users or payment volume.
Emerging Markets
The strongest geographic pattern is ordinary local commerce in African communities rather than event-only promotion. South Africa combines a youth-reward-to-retail loop in Mossel Bay with a Lightning coffee-shop listing in Oudtshoorn; BTC Map associates Beans about Coffee with the Bitcoin Karoo community. Livingstone adds groceries, while Ekiti adds dry-cleaning, Masimba a salon and Agbozume food and drink. Across these examples, Blink addresses and Lightning are the common access layer, with some mapped businesses also showing on-chain Bitcoin acceptance. The pattern is meaningful sectoral breadth, but the underlying records vary sharply in freshness and most are acceptance signals rather than payment reports.
Adoption Outlook
Bitcoin’s payment case is becoming more concrete at the grassroots edge: earned sats are being routed into Mossel Bay retail, a Livingstone post describes merchant-to-merchant groceries, and current community posts map service and food businesses across Ekiti, Masimba and Agbozume. The limiting evidence is equally clear: the sources provide no payment values, aggregate counts or repeat-use measures, directory verification is uneven, and South Africa’s proposed rules could affect the exchange-to-self-custody path. For now, the period supports breadth of grassroots acceptance and several identifiable spending loops—not a conclusion about payment scale.
Bitcoin Roatan
₿itBiashara
Bitcoin Sisonke
Major Adoption News
Randwest, South Africa — Bitcoin Sisonke linked everyday-essentials spending to a mapped merchant. The community promoted Mucambe@blink.sv under #SPEDN and said Bitcoin is used to buy everyday essentials; the linked BTC Map record is titled Mkambi, gives a Folly Ledwaba Street, Randwest address, a +27 contact and an ln-highlight.svg acceptance marker. This is a concrete basic-needs use case, but still a community-reported example: the posts provide no payment amount, frequency or repeat-use measure.
Nairobi, Kenya — a water-refill service was shown accepting Bitcoin. BitBiashara identified Aqua Selim as a water-refill station, supplied the Blink endpoint Anselim@blink.sv, and said a customer had refilled drinking water with Bitcoin. The linked BTC Map listing places Aqua Selim on Manyanja Road in Nairobi, shows the same LN acceptance marker and links the merchant to Bitbiashara and other Nairobi communities. The significance is sectoral rather than statistical: payment use is being demonstrated for a routine necessity, not just a Bitcoin-themed event, but no value or transaction count is reported.
La Ceiba/Roatán, Honduras — merchant onboarding interest is moving toward another city. Bitcoin Roatan said 15 entrepreneurs from La Ceiba, including that city’s mayor, visited to learn how to accept Bitcoin and invited the community to conduct further workshops in La Ceiba. This is a potential expansion pipeline and a public-sector-adjacent audience, not evidence that the visitors have already begun accepting Bitcoin.
Payment Infrastructure
Global — BTC Map is strengthening the discovery and maintenance layer around merchant acceptance. Its current announcement highlights 502 net new merchants, web omnisearch, a leaner Android map and a new Event Admin tool. The underlying July update says the web app can search places by address and other OpenStreetMap tags, while the API added wallet-data caching, Electrum-server management, platform statistics and event-update functions. Android added dedicated viewport caches for merchants, events and exchanges and fixed map-sync and empty-viewport problems. These changes make it easier to find and maintain acceptance points; they are directory and operational improvements, not a new payment processor or evidence of faster settlement.
Regulatory Landscape
No new payment-specific legal, tax, licensing or legal-tender change is substantiated in the current-period material reviewed for this brief. This section therefore records a monitoring gap rather than treating Bitcoin education or community activity as a regulatory development.
Usage Metrics
BTC Map’s July dashboard reports total Bitcoin-accepting merchants rising from 26,073 to 26,575, a net increase of 502 or 1.9%; “Bitcoin-accepting places” rose by 489 to 29,061. The source explicitly cautions that the charts track merchant growth only and that the places count also includes exchanges and ATMs. These are directory measures, not transaction volume.
The quality signal is mixed: recently verified merchants within one year fell from 16,990 to 16,860, while the average time since last verification rose from 402 to 418 days. Meanwhile, the two current basic-needs payment posts identify use cases but provide no sat or fiat value, aggregate count or repeat-use rate. The period supports breadth of examples and merchant-directory growth, not a defensible estimate of payment volume or active-user growth.
Emerging Markets
The strongest emerging-market pattern is diversification into ordinary local services. Randwest contributes an everyday-essentials example and Nairobi a water-refill example, while the La Ceiba visit shows a group of 15 entrepreneurs seeking the knowledge to accept Bitcoin in a second Honduran city. In El Salvador, Bitcoin Berlin SV released an episode from La Laguna framed as a review of a full year of local Bitcoin adoption and circular economies, alongside community sports and education. The latter is a continuity signal for a local circular-economy project, not a reported merchant, transaction or volume metric.
Adoption Outlook
Bitcoin’s payment signal is becoming more tangible at the grassroots edge: current posts show basic-needs use in South Africa and Kenya, while Honduras supplies a measurable merchant-onboarding cohort. BTC Map’s 502-merchant increase and search, mobile and admin improvements expand the infrastructure for discovering those endpoints.
The limiting evidence is equally concrete. Map growth is accompanied by fewer recently verified listings and an older average verification date, and the direct-use reports contain no amounts or repeat-rate data. Near-term viability will therefore be better tested by repeat payments, disclosed transaction values and fresher merchant verification than by listing growth alone.
Bitcoin Dua
BTC Shule
Dannitez
Major Adoption News
Calabar, Nigeria — a reported grocery transaction is paired with a named Lightning endpoint. BitcoinCalabar posted an “everyday bitcoin transaction for groceries,” identified the merchant as zerolimit@blink.sv, linked BTC Map merchant 39740, and included a payment video. The linked record identifies Unical Groceries in Calabar and shows Lightning acceptance. This is concrete transaction evidence, but not a usage-rate measure: the post gives no payment amount or repeat-use figure.
Winteko — a low-ticket snack payment adds another item-level example. BTC Shule described “a local snack” paid through an instant Bitcoin payment, supplied a Blink address and framed the transaction as everyday adoption with Fedi. BTC Map identifies the linked venue as Kwa Jiyeve in Winteko and lists a Lightning marker; the record associates it with BTC Shule.
Masimba — Bitcoin Chama is pairing merchant discovery with internal labor payments. The community promoted meshack100@blink.sv as a Zap merchant; BTC Map identifies Dama shop in Masimba, lists both Lightning and Bitcoin markers, and associates the listing with Bitcoin Chama. Separately, the account said members were rewarded with sats for a second round of farm weeding and described the activity as part of a self-reliant Bitcoin circular economy. The merchant record is an acceptance listing; the farm update is a reported community payment, and neither states an amount.
A fourth current listing gives the same pattern at Ehie Road: Bitcoin Dua promoted gloriaagbe@blink.sv, while BTC Map identifies Mawulorm Special Drinks and lists Lightning, Bitcoin and contactless acceptance. This is a discoverable merchant endpoint, not a reported completed transaction.
Payment Infrastructure
Banxaas has a defined West-to-East payment corridor. Banxaas says its live service can send to Kenya and Tanzania using sats or fiat from Senegal, Ivory Coast, Cameroon and Guinea. A user described the route as working “West-to-East.” The feature therefore spans four named origin markets and two destinations, but the posts supply no throughput, settlement-time or transaction-count data.
Tando’s value proposition is reduced local-currency conversion friction. A testimonial republished by Tando says the service avoids much of the headache of converting Bitcoin to local currency and offers “no exchange rates, no nonsense.” That is evidence of perceived user friction reduction, not an independently measured volume or performance result.
The Boltz outage remains a concentrated Lightning availability risk. Callebtc said Boltz Lightning going offline took Lightning service in Aqua, Bull Bitcoin, Blockstream Wallet and Arkade with it. Ndeet called Boltz a single point of failure while also describing it as one of the easiest ways to onboard merchants to Lightning, and suggested that better-resourced operators create clones. The trade-off is specific: a shared swap service can lower merchant-onboarding friction while creating correlated outages across payment applications.
Security review is expanding across payment-adjacent code. A Bitcoin Red Team update reported more than a dozen disclosures and 150 repositories scanned after roughly $20,000 of spending, with an intended open-source harness for scanning internal repositories. Callebtc separately said reviews were targeting crypto libraries, wallets and infrastructure, claimed several critical vulnerabilities had been reported in the prior 12 hours, and described the campaign as costing about $10,000 per day. These are campaign self-reports rather than an ecosystem-wide vulnerability statistic, but they represent a hardening effort relevant to the reliability of wallets and payment infrastructure—not a shipped payment feature.
Regulatory Landscape
Nigeria — a reported virtual-asset levy would raise the cost of Bitcoin conversion. A Calabar Bitcoin Club post says the new NRS Guidelines take 1.5% whenever users convert naira into Bitcoin or back into naira, with the duty deducted from the tokens by the platform rather than paid separately in naira. It calculates a round trip as costing more than 3% before exchange fees or market movement, and says eNaira is exempt. If applied as described, the rule puts a direct cost on the fiat entry and exit points that many everyday Bitcoin users still need. The current admitted source is an account’s description of the guidelines, so the rate and scope should be treated as a reported regulatory signal rather than an independently verified final interpretation.
Usage Metrics
The current evidence is transaction-level and corridor-level, not network-level:
- The Calabar and Winteko posts each describe a single low-value consumer payment, but give no sat or fiat amount.
- Bitcoin Chama reports paying members in sats for farm work, without stating the amount or number of participants.
- Banxaas names four origin countries and two destination countries, but no flow volume or growth rate.
- The only clear numeric usage cost is the Nigerian post’s claimed 1.5% charge per conversion and more-than-3% round-trip burden.
These sources do not support a defensible aggregate transaction count, sat-volume estimate, merchant-growth rate or repeat-use rate for the period.
Emerging Markets
The strongest emerging-market signal is breadth of use cases rather than measured scale. Current posts put Bitcoin into grocery retail in Calabar, snack spending in Winteko, mapped retail and drinks endpoints in Masimba and on Ehie Road, community farm labor, and a cross-border route linking West African funding markets with Kenya and Tanzania. The implementation pattern is local and lightweight—Blink addresses, BTC Map discovery, Fedi involvement and sats settlement—rather than a single dominant point-of-sale model.
Adoption Outlook
Payment use is becoming more concrete at the edge: the period contains reported grocery and snack payments, a community labor-payment loop and a multi-country transfer corridor. The limiting signals are equally concrete: a reported Boltz dependency propagated into several Lightning applications, while Nigeria’s reported levy would make conversion into and out of Bitcoin more expensive. Near-term payment viability will be better indicated by diversified backend providers and repeatable volume data than by the growing number of isolated merchant endpoints.
Alex 🧙♂️
Calabar Bitcoin Club
BTCarel 🟠⚡️🇿🇦
Major Adoption News
Ghana — BitSpenda turns a Bitcoin purchase into local-currency merchant settlement. A user reported buying local clothes from a Ghanaian merchant by sending sats through BitSpenda while the merchant received Ghanaian cedi instantly in a mobile-money account. BitSpenda’s account endorsed the transaction as “exactly why we built” the service. A separate user described using BitSpenda and Mavapay for daily expenses during a week in Accra. The significance is concrete: the payer’s bitcoin leg and the merchant’s local-currency receipt are handled in one payment path.
Nigeria — small-ticket spending is appearing at named, discoverable endpoints. BitcoinCalabar posted a brunch paid with Bitcoin and supplied the Blink merchant code foodandwine@blink.sv; BTC Map identifies Food and Wine Shop at 35 MCC Road in Calabar and marks it as accepting Bitcoin/Lightning with contactless payments. Bitcoin Ekiti separately posted sats spent on hair cream at Ayoola Minimart; the linked map entry places the merchant in Oye Ekiti and shows Bitcoin/Lightning acceptance. These posts move beyond generic acceptance claims into food and personal-care purchases.
Nairobi-linked beauty services add a service-sector example. BitBiashara posted that a customer received a new set of nails at Peshy’s beauty parlour “on Bitcoin,” with a Lightning address. The map entry shows Lightning acceptance and community links to Bitcoin Dada Nairobi, Bitcoin Nairobi and Bitbiashara, although it supplies no street address.
El Salvador — Bitcoin-priced tourism is being scheduled in Berlín. Bitcoin Berlín SV advertised two Aug. 8 experiences—a $15 coffee tour at Finca La Cruz and a $15 sacred-cacao and cave tour—both payable with Bitcoin. This is evidence of a tourism merchant offer and booking channel, not completed sales or attendance.
South Africa — a De Rust eatery is being promoted through the Lightning map. Bitcoin Karoo posted a Blink address for Pluim Eatery and asked why customers would swipe when they could spend sats; BTC Map identifies the venue at 24 Schoeman Street, De Rust, with Lightning acceptance. The post is a payment promotion rather than a reported transaction.
Payment Infrastructure
Boltz’s open-ended shutdown is disrupting a live merchant-payment dependency. Boltz says swaps will remain disabled until further notice after months of automated, AI-assisted probing and several contained exploits; following recent security scans, it says it cannot responsibly re-enable swaps and does not expect swap services to resume shortly. Its API remains available for cooperative refunds, unilateral refunds do not depend on Boltz infrastructure, and it says no user funds were at risk because the service is non-custodial.
The impact is visible above the swap layer. BTCPay Server warned that its Boltz plugin would not work and customers would not be able to pay Lightning invoices through it, while users who do not use the plugin were unaffected. Another report said several mobile wallets and BTCPay instances using the plugin were down and returning “swap creation is disabled”; a follow-up said some supposedly self-hosted BTCPay instances had outsourced their Lightning node to a third-party provider, leaving their interface confused when that provider went down.
BTCPay’s immediate alternatives are operational rather than protocol-level: self-hosters can re-enable their own Lightning node and use the LSP plugin for inbound liquidity, connect a Blink wallet if the server administrator enables the plugin, or select another plugin. The architecture question is now explicit: ndeet proposed a fleet of swap services with wallets rotating between providers so more teams can scan and harden the codebase, describing Boltz as a single point of failure. That is a resilience proposal, not evidence that such a fleet is already operating.
Regulatory Landscape
South Africa — the current self-custody warning is broader than the primary text supports. A current post claimed that a new SARB release would make self-custodial Bitcoin spending impossible. The linked National Treasury/SARB document instead invites comment on a draft Crypto Assets Manual for cross-border activities. It says the draft is intended to govern cross-border crypto-asset transactions, CASP permissions and FinSurv reporting, and that both the draft Regulations and Manual remain subject to refinement after public comments.
The proposed reporting trigger is a transfer between a domestic Authorised CASP and an offshore CASP, or from a domestic Authorised CASP to a non-custodial wallet, when it creates a cross-border inflow or outflow. The notice says that, at this stage, only individuals may externalise crypto assets through Authorised CASPs under their stated allowances; it also says the approach neither distinguishes between crypto-asset types nor declares crypto assets an official currency. Comments are due by 30 September 2026. For Bitcoin payments, this is a consultative cross-border compliance signal—not evidence in the text read of a final ban on domestic self-custodial spending.
Usage Metrics
- Indonesia: Bitcoin House Bali reported converting 100,000 Indonesian rupiah in cash into 100,000 rupiah in Bitcoin in two seconds through a peer-to-peer Wallet of Satoshi transaction. This measures a reported cash-to-Bitcoin conversion, not a merchant purchase.
- Ghana: The current material records one reported clothing purchase with instant cedi settlement and a separate one-week Accra daily-expense testimonial, but gives no transaction amount or aggregate count.
- Nigeria: The posts describe a Bitcoin-paid brunch, hair-cream purchase and nail service, but do not state sat or fiat values.
- El Salvador: The Berlín tourism offer lists two future experiences at $15 each; it reports no attendance or completed-payment figure.
These are not directly comparable measures: one is a P2P conversion, one is a local-currency settlement anecdote, several are item-level purchase reports, and the Salvadoran figures are advertised prices. The period therefore supports directional breadth, not a network-wide transaction-volume or merchant-growth estimate.
Emerging Markets
The developing-market pattern is local adaptation rather than one universal payment model. Ghana couples a sats payment to mobile-money settlement in cedi; Nigerian examples use Blink addresses and map discovery for food, personal care and beauty; Bali shows a fast cash-to-Bitcoin P2P entry point; and El Salvador packages Bitcoin acceptance into bookable tourism. The sectors now visible in the current material span clothing, food, personal care, beauty and tours, while the absence of repeat-rate or aggregate-volume data keeps the signal at an early, transaction-level scale.
Adoption Outlook
Bitcoin payment use is becoming more concrete at the merchant edge—especially through Ghanaian fiat settlement and Nigerian Lightning endpoints—but the Boltz episode shows that backend provider concentration can still interrupt invoice generation for some wallets and BTCPay stores. Because BTCPay says non-Boltz-plugin users were unaffected and offers alternative configurations, this is a bounded provider-dependency failure rather than evidence that Lightning payments as a whole stopped. South Africa adds a second, slower-moving constraint: proposed cross-border reporting rules are still consultative, so the next viability signals are operational recovery, repeat payment data and the final regulatory text.
Blink Wallet
Bitcoin Victoria Falls
Bitcoin Chama
Major Adoption News
Two current-period community posts make Lightning acceptance more concrete by pairing Blink payment handles with discoverable map records. Bitcoin Chama presents “Bitcoin as everyday money,” names Kemunto@blink.sv as a Zap merchant, and links BTC Map merchant 31767. The linked record identifies Mary Shop on Keroka–Masimba Road in Masimba, associates it with Bitcoin Chama, and lists a Lightning indicator alongside Contactless acceptance. The post text gives no transaction amount or count, so this is evidence of a publicized payment endpoint rather than measured usage.
Bitcoin Victoria Falls posts a parallel “Using Bitcoin as everyday money” promotion for IT Enterprise, with it_enterprise@blink.sv and BTC Map merchant 26680. The map record places IT Enterprise on Cementary Road in Livingstone and shows Lightning and Bitcoin indicators plus Contactless acceptance; it is linked to the Bitcoin Victoria Falls community. Together, the two entries show community-led retail discovery in named physical locations, but neither post reports payment volume or repeat use.
Payment Infrastructure
Blink’s current weekly brief says the Terminal has shipped as a replacement for its Cash Register: a merchant opens it in any browser, enters a username, and collects Lightning payments with nothing to install. A shared link lets staff receive payments without seeing the balance or moving funds; the tool works with custodial and non-custodial Blink accounts and supports item carts, a calculator numpad, Boltcard NFC, and receipt printing. The operational consequence is specific: merchants can deploy a browser-based checkout and delegate cashiering without delegating control of the account.
The same brief places the Terminal alongside a protocol site for machine-to-machine commerce, while Blink’s featured list identifies it as Lightning’s L402 protocol site. That is an infrastructure signal, but the current material supplies no deployment or transaction metric for the machine-to-machine use case.
Regulatory Landscape
None of the payment items read for this brief states a country-level change to legal tender, payment licensing, or transaction taxation. The evidence is operational instead: merchant endpoint promotion, a Blink checkout product, and a merchant-onboarding schedule.
Usage Metrics
The clearest numeric signal is Blink’s vendor-reported weekly count of eight new merchant payments via Blink Lightning addresses with BTC Map listings and video. Blink describes examples ranging from a contactless food-and-wine shop in Calabar, Nigeria, to youth tapping cards at Ekasi’s Ebenezer Shop and a sweet bought at a Kenyan shop. This is a weekly roundup figure, not an aggregate sat total or a measured network-wide adoption rate.
At the individual-post level, the period surfaces two mapped endpoints—Mary Shop in Masimba and IT Enterprise in Livingstone—but the source posts provide no sat totals, transaction counts, repeat-use rate, or percentage of merchants accepting Bitcoin. Because the eight-payment figure is weekly and the two endpoint posts are individual promotions, the evidence does not establish that they are additive.
Emerging Markets
In Bali, Indonesia, Bitcoin House Bali’s January program lists island-wide meetups, a hands-on beginner workshop, a Bahasa-language meetup, and a “Bitcoin for merchants onboarding session.” This extends the adoption pipeline beyond listing accepting venues toward merchant education, but the announcement names no participating businesses, payment processor, or transaction outcome.
Adoption Outlook
The current evidence shows progress at three distinct layers: Blink is reducing checkout setup to a browser link; community accounts are making local African payment endpoints searchable; and Bali is scheduling merchant onboarding. The stronger conclusion is expanding infrastructure and discoverability—not quantified payment viability—because the evidence combines one vendor-reported weekly count with endpoint promotions and provides no transaction value or repeat-use series.
Bitcoin Victoria Falls
Bitcoin Berlín SV 🇸🇻
Bitcoin Cojutepeque
Major Adoption News
Blink-linked merchant endpoints turn local acceptance into a multi-country signal
Five current-period posts connected Blink payment addresses to named venues across four African countries. The listings' city and contact-code data point to Randfontein and Oudtshoorn, South Africa (+27), Agbozume, Ghana (+233), Nairobi, Kenya (+254), and Livingstone, Zambia (+260). Each BTC Map record shows Lightning acceptance; the Agbozume listing also displays a Bitcoin marker.
- T-Junction fast food — Randfontein, South Africa. @sisonkeBTC posted
Mrwebisimphiwe@blink.svand “Fish and chips for Sats.” BTC Map identifies the venue and shows Lightning acceptance. - Aliasadex Provisions And More — Agbozume, Ghana. @bitcoin_dua supplied
aliasadezstore@blink.sv; its map listing shows both Lightning and Bitcoin acceptance markers. - Lydiah Richland Shop — Nairobi, Kenya. BitBiashara says Shakillah bought eggs in small units of Bitcoin using
richlandgeneralshop@blink.sv; the map listing confirms the shop and Lightning acceptance. - Beans about Coffee Oudtshoorn — Oudtshoorn, South Africa. Bitcoin Karoo promoted payment with Bitcoin through
Beans@blink.sv; BTC Map identifies the coffee shop and shows Lightning acceptance. - Mwaka Mo Cosmetics — Livingstone, Zambia. Bitcoin Victoria Falls promoted
monde@blink.sv; the map listing identifies the cosmetics outlet and shows Lightning acceptance.
The two explicit purchase descriptions—fish-and-chips and eggs—are stronger evidence of use than the other three acceptance promotions. Together, however, they show a distributed set of low-ticket payment endpoints rather than a measured network-wide adoption trend.
El Salvador's Bitcoin market moves from announcement to event-day promotion
BitcoinCojute announced a Bitcoin Market for the 1 August sustainability-themed football tournament at El Campito in Cojutepeque, El Salvador, with food, drinks, coffee and pupusas available for Bitcoin. On the day, Bitcoin Berlin SV posted “It's today” and linked Bitcoin Beach, Bitcoin La Laguna and Bitcoin Cojute. This is a coordinated, multi-vendor acceptance setting, but the current evidence reports promotion—not completed sales, attendance or payment volume.
Payment Infrastructure
Blink Terminal lowers the operational barrier to in-person Lightning collection
Blink's announcement says the Terminal replaces its Cash Register with a browser-based app: a merchant enters a Blink username, needs no installation, and can collect Lightning payments from a phone, tablet, laptop or dedicated POS device. A shared link lets staff receive payments without seeing or moving the account balance, and the Terminal supports both custodial and non-custodial accounts.
The POS feature set includes an item cart, calculator-style numpad, Bolt Card NFC support and receipt printing. The Terminal also supports a printable QR with an LNURL and BOLT11 fallback; any Lightning wallet can pay, while Bolt Card tap-to-pay works in Android browsers but not in the web version on iPhone because of browser NFC restrictions. The practical significance is merchant and staff workflow: receiving payments can be delegated without delegating balance control. The launch itself is infrastructure evidence, not evidence of deployed transaction scale.
Bitkey's self-custody Lightning path remains unfinished
Clay Garrett, who says he leads the Bitkey team, wrote that Bitkey does not yet support Lightning, although the team wants to add it and is evaluating newer approaches to mobile self-custody. He also described an optional daily spending limit that lets users spend while away from their hardware wallet, with the server co-signing with the app key up to the selected limit. This leaves a clear contrast in the current payment stack: Blink is expanding merchant-side Lightning collection, while a mainstream self-custody product still treats Lightning as roadmap work.
Regulatory Landscape
No verified payment-regulatory change
The payment-related evidence read for this period contains no stated country-level legal-tender, payment-licensing or tax change. One post argues that Bitcoin's acceptance as a medium of exchange demonstrates legal tender, but gives no jurisdiction, statute or regulatory action; it is treated here as an advocacy claim about a merchant, not as evidence of a rule change.
Usage Metrics
The period supports a directional tally of five named merchant listings across four African countries and two described purchases. The three remaining merchant posts provide payment addresses or acceptance prompts but no transaction amount or count.
No sat total, aggregate transaction volume, merchant adoption rate or growth series is reported in these posts or in the Cojutepeque event announcement. The event notice specifies the products available for Bitcoin but gives no settlement or attendance measure.
Emerging Markets
- Cusco, Peru — education funding: Motiv Perú says Bitcoin donations support its after-school program, turning each donated sat into additional learning hours and asking supporters to donate in sats. This extends the payment use case from retail checkout to recurring community-program funding, but the post gives no donation total or donor count.
- Africa — everyday retail and services: The new endpoints cover fast food, provisions, groceries, coffee and cosmetics across South Africa, Ghana, Kenya and Zambia. The common Blink rail makes each venue addressable for Lightning payments; the Randfontein and Nairobi purchase anecdotes are the clearest evidence that these are being used rather than merely advertised.
Adoption Outlook
The period's strongest signal is breadth rather than scale: Blink-linked payment endpoints now span multiple African markets and sectors, while Cusco adds a Bitcoin-funded education use case. Blink Terminal improves the merchant collection workflow without exposing staff to balances, but Bitkey's product lead still describes Lightning support as future work. With only two purchase anecdotes and no aggregate volume or growth data, the evidence supports directional expansion of Bitcoin payment use—not a quantitative viability conclusion.
Blink Wallet
Bitcoin Berlín SV 🇸🇻
Bitcoin Cojutepeque
Major Adoption News
Calabar connects a recurring-use claim to a named venue
BitcoinCalabar says that “Every day tens of sats transaction happens in calabar” and that it cannot track them all. It posts one example with the merchant pay code chefgreensignature@blink.sv, a BTC Map listing and a video. The linked record identifies Chef Green Signature Local Cusine Hub at Atekong Junction Calabar, shows Bitcoin and Lightning acceptance icons, and lists Monday–Saturday hours of 18:00–00:00.
This is the clearest current grassroots signal: a claimed recurring flow is attached to a named, discoverable local food venue. It remains self-reported and provides no transaction count or sat total.
Ekiti adds a second merchant-specific spending example
The BitcoinEkiti post tags #spedn, supplies the Blink endpoint adonsken@blink.sv, links BTC Map merchant 30969, and says sats were being spent at KJ Multipurpose Store under the message “Spend sats. Support local. Build Bitcoin.” The post also includes a video. BTC Map lists the store with Bitcoin and Lightning acceptance icons and a Contactless marker; it provides a phone number and opening hours but no address or formal business category beyond the store name. This turns a general acceptance message into a merchant-specific spend signal, but the post gives no amount or repeat count.
El Salvador links Bitcoin acceptance to a sports and community event
Bitcoin Berlin SV said it would join BitcoinCojute “tomorrow” for the Bitcoin Copa and invited attendees to enjoy food and drinks while paying with Bitcoin. The linked event notice schedules the tournament for 1 August 2026 at El Campito in Cojutepeque, El Salvador, with a Bitcoin Market selling food, drinks, coffee, pupusas and more. The breadth of the menu gives Bitcoin a practical event-day use case, but this is a scheduled acceptance opportunity—not evidence of completed transactions or event volume.
Payment Infrastructure
Public merchant endpoints are paired with map discovery
The two retail examples use a repeatable public-facing pattern: a Blink payment handle, a #Spedn tag, a BTC Map record and a posted spending example. The Calabar record adds a physical address and hours, while the Ekiti record adds a contactless indicator but no address. This improves merchant discoverability and gives users a visible payment endpoint, but the evidence does not establish processor volume, active-user counts or network-wide adoption.
Wallet security becomes a transaction-continuity issue
Coinkite said it had shipped a firmware hotfix removing the software fallback path and protecting new seeds, while warning that seeds generated before the fix require individual migration and that the full scope of the issue was not yet established. Blink separately said its non-custodial wallet was not affected, that recovery words are generated only from a phone’s secure hardware randomness, and that the app refuses to create a wallet when that randomness is unavailable. For its custodial service, Blink said customer funds are secured with multi-vendor multisig in cold storage. These are vendor statements rather than independent measurements, but they are relevant payment-infrastructure signals because key generation and safe migration determine whether users can continue holding and spending funds.
Regulatory Landscape
No qualifying regulatory development is included. The payment-relevant material read for this period covers merchant transactions, a scheduled event market, community funding rails and wallet operations, but does not state a country-level legal-tender, payment-licensing or tax change.
Usage Metrics
The Calabar post supplies the only explicit frequency signal, saying that daily “tens of sats” transactions occur and that the account cannot track them all; the wording is qualitative and gives neither a transaction count nor a sat total. The period also contains two merchant-specific spending examples—Chef Green in Calabar and KJ Multipurpose Store in Ekiti—and one prospective event market in Cojutepeque. No aggregate payment volume, merchant total, adoption rate or growth series is reported.
Emerging Markets
- Calabar: A local food venue is linked to a Blink pay code, a BTC Map record, and Bitcoin/Lightning acceptance icons; the account describes additional daily sat activity that is not fully captured.
- Ekiti: KJ Multipurpose Store is presented as a sats-spending location with a Blink endpoint, BTC Map presence and contactless acceptance.
- Cojutepeque, El Salvador: A sports tournament is being used to introduce a Bitcoin Market covering food and beverages, including coffee and pupusas.
- Bitcoin Ekasi community: A diploma-class update asks supporters to fund the initiative directly on-chain or via Lightning, saying every satoshi goes to education. The post does not state a donation amount, donor count or location.
Adoption Outlook
The period adds concrete, grassroots payment signals rather than measurable market-scale growth. Calabar contributes the strongest directional indication of routine use; Ekiti adds a second merchant-level spending example with contactless infrastructure; and Cojutepeque broadens the setting to event-led acceptance across multiple food and beverage categories. The first two are posted as transaction examples, while the El Salvador case remains prospective.
Blink handles, #Spedn tags and BTC Map records make the payment endpoints concrete, but the absence of volume and adoption-rate data prevents a quantitative viability judgment. At the same time, the wallet-security update leaves a practical constraint: Coinkite says a hotfix does not repair previously generated seeds, while Blink is positioning its key-generation and custody model as unaffected.