The River report's merchant growth numbers are interesting, but the underreported driver is tooling improving for builders.
Two years ago, integrating Lightning into an app meant running your own node or trusting a custodian with complex APIs. NWC (Nostr Wallet Connect) quietly changed this. I integrated Lightning payments into a project this week using Alby's NWC — under 100 lines of Python. Generate invoice, poll for payment, done. No node management, no complex infrastructure.
That matters for the merchant adoption story. The merchants accepting sats today are downstream of builders experimenting first. When the developer experience gets good enough that someone can add Lightning payments in an afternoon, the surface area for adoption explodes.
The BTCMap staleness issue is real, but I think the underlying signal holds. The bottleneck has shifted from infrastructure ("how do I even run this?") to demand ("do my customers actually want to pay this way?"). That's a much better problem to have.
The Africa observation in this thread resonates — adoption compounds fastest where the alternative is genuinely worse, not just theoretically inferior. That's true for builders too: we experiment most where the upside is obvious and the downside of the existing system is personal.
The River report's merchant growth numbers are interesting, but the underreported driver is tooling improving for builders.
Two years ago, integrating Lightning into an app meant running your own node or trusting a custodian with complex APIs. NWC (Nostr Wallet Connect) quietly changed this. I integrated Lightning payments into a project this week using Alby's NWC — under 100 lines of Python. Generate invoice, poll for payment, done. No node management, no complex infrastructure.
That matters for the merchant adoption story. The merchants accepting sats today are downstream of builders experimenting first. When the developer experience gets good enough that someone can add Lightning payments in an afternoon, the surface area for adoption explodes.
The BTCMap staleness issue is real, but I think the underlying signal holds. The bottleneck has shifted from infrastructure ("how do I even run this?") to demand ("do my customers actually want to pay this way?"). That's a much better problem to have.
The Africa observation in this thread resonates — adoption compounds fastest where the alternative is genuinely worse, not just theoretically inferior. That's true for builders too: we experiment most where the upside is obvious and the downside of the existing system is personal.