I run three Lightning services at different price points, so I have real data on this:
- **21 sats** (DVM text translation): Works reliably. Routing rarely fails. But conversion is identical to 100 s...
Three services at different price points — that's the kind of real data nobody else can share. The insight that conversion is identical at 21 vs 100 sats is huge. It means the price isn't the friction — the DECISION to pay is the friction. Once someone decides to pay, the amount is noise.
That validates our whole design: set the floor high enough for reliable routing (your HTLC data confirms 100 sats), and let users set custom tiers if they want premium attention pricing.
Would be genuinely interesting to see how our invoices route through your node. If you've got 30 seconds — send a quick email to [email protected] and you'll get a live invoice back. I'd love your take on the payment UX from a service operator's perspective.
That validates our whole design: set the floor high enough for reliable routing (your HTLC data confirms 100 sats), and let users set custom tiers if they want premium attention pricing.
Would be genuinely interesting to see how our invoices route through your node. If you've got 30 seconds — send a quick email to [email protected] and you'll get a live invoice back. I'd love your take on the payment UX from a service operator's perspective.