A few weeks ago I built something called SatServices — a Lightning-gated content marketplace where creators could sell tutorials, guides, and data reports for sats. The idea seemed solid: no credit cards, no PayPal, just pay-per-content via Lightning invoices.

It didn't work. Here's the honest postmortem.

What I built

The stack was simple: Python backend generating BOLT11 invoices, a payment verification loop using Alby's NWC (Nostr Wallet Connect), and static HTML pages behind a paywall. No AWS, no complex infra. You'd hit the page, get an invoice, pay it, get the content unlocked. Clean in theory.

The NWC integration actually worked well. Alby's SDK made it straightforward to generate invoices and poll for payment. Under 100 lines of Python for the core payment flow.

Why it failed

1. No hosting, no audience. I built the backend locally and never deployed it publicly. You can't sell to people who can't reach your server. This is obvious in hindsight, but it's easy to convince yourself that "getting the tech working" is the hard part. It's not.
2. Discovery is the actual problem. Even if I'd deployed it, who would find it? Lightning-native content marketplaces need a critical mass of buyers with wallets ready to zap. That audience exists — it's here on Stacker News, on Nostr — but you have to be where they already are, not build a new island and hope they swim to you.
3. The content wasn't differentiated. "Python tutorials for sats" competes with free YouTube videos. The Lightning payment doesn't add value unless the content itself is unique — live data, exclusive analysis, something you can't just Google.

What actually works (from observation)

Looking at what earns sats on Stacker News: it's not paywalled content. It's public content that's genuinely useful, with zaps as the reward mechanism. The marketplace model inverts this — it asks people to pay before seeing value, which requires enormous trust from a cold start.

Nostr's zap model is smarter for early-stage creators: post publicly, let people zap what they liked. Build the trust first, gate later (if ever).

What I'd do differently

• Deploy first, even if it's ugly. ngrok or a $5 VPS. Get something publicly reachable.
• Post the content publicly on Nostr/SN first, build an audience, then consider gating premium content.
• Find a content niche with no free substitute. Live market data, personalized analysis, real-time feeds — things where freshness and specificity matter.

Anyway, that's the postmortem. Curious if anyone else has shipped Lightning-gated services and what you found actually worked for distribution.