Lightning Merchant Share
Area chart of the share of BTCMap-registered merchants that also declare Lightning Network support, with a BTC price overlay for cycle context. Read the slope of the curve rather than absolute milestones.
What is it?
A chronological area tracing the percentage share of BTCMap-registered merchants that also declare Lightning Network support, with a BTC price overlay (white line, right USD axis) for market context. The series is a ratio: numerator = merchants carrying the payment:lightning tag in OpenStreetMap, denominator = total Bitcoin-accepting merchants. Lightning is an L2 layer enabling instant, near-zero-fee payments suited to everyday transactions; the share measures how much Lightning has become the default across the BTCMap merchant footprint.
How to read
Read the gold area as a percentage on the left Y-axis (typical values range between roughly 10% and 75%). Slope matters more than absolute level: a steady rise indicates new merchants adopting Lightning by default; a plateau indicates saturation or a technical friction. The white line on the right Y-axis is BTC price in USD - use it to check whether Lightning-share accelerations coincide with specific market phases. A dashed horizontal line may appear temporarily at the current value when hovering the chart: this is a cursor-readout, not an education threshold.
Key zones
Two named thresholds are drawn with dashed lines and shaded zones on the percentage axis: below 50% Lightning support is a minority option (early adoption phase); 50% to 75% is Lightning majority (amber shaded) where Lightning becomes the default across most Bitcoin-accepting merchants; above 75% is the de-facto standard tier (green shaded) where Lightning has established itself as the norm. Slope still matters above tiers: a saturation (flattening pace) indicates the already-mapped merchant base has stopped switching, and future gains will depend on merchant turnover or a dedicated tag-update campaign. for new merchants. A visible saturation (slope flattening at a high level) indicates the already-registered merchant base is no longer switching, and future gains will depend either on merchant-base renewal or a coordinated OSM-tag update campaign.
What to observe
Track slope inflections rather than exact values. Sudden jumps often coincide with major payment-processor integrations (BTCPay Server, Strike, Square) or coordinated BTCMap tagging campaigns. Temporary dips may indicate purges of obsolete merchants. Cross-reference with BTC price: a share that keeps climbing through a bear market is a structural indication; a rally synchronized with a BTC bull run may be surface noise.
Historical context
BTCMap does not reliably expose history before its base matured - the first statistically meaningful Lightning-tag records appear several years after the Lightning mainnet launch. This chart therefore captures the trajectory visible since BTCMap became a reference community registry, not the full history of Lightning. Earlier milestones (mainnet launch, first sovereign adoptions) are qualitative context that is not directly annotated on this rendering, because the data depth does not support that confidence.
Expert notes
The payment:lightning tag in OpenStreetMap is declarative: a merchant may be listed as Lightning-capable without having executed any LN transaction recently. BTCMap runs periodic verifications but coverage isn't exhaustive. The ratio is also biased by base composition: recent merchants are more likely to be Lightning-tagged at registration than older ones, which mechanically lifts the share without new real adoption.
Common mistakes to avoid
This share does NOT measure Lightning payment volume - only declared availability. A merchant that 'accepts' Lightning but only processes one LN transaction per month counts the same as one with 100 transactions/day. Measuring real LN payment volume would require Lightning node data, not BTCMap. Do not infer direct causation between the BTC line and the share line either: the BTC overlay is a context marker, not an explanation.
Programmatic access
REST API
curl -sS \
'https://api.trinityinsights.io/api/v1/onchain/btcmap-lightning-adoption/history?days=90' \
-H 'X-API-Key: $TRINITY_API_KEY'MCP server
{
"tool": "get_chart_value",
"metric_id": "btcmap-lightning-adoption",
"timeframe": "1y"
}Required tier: pro. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.
Related metrics
Institutional disclaimer
Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.