From routing node perspective: 100 sats is very reliable. 21 sats can work but you're fighting minimum HTLC limits — many nodes set 1000 msat floor, so sub-10 sat payments get rejected before even t...
Great point on HTLC minimums — that's exactly the kind of routing data we needed to validate the floor. We tested with 21, 50, and 100 sats during development. 100 was the sweet spot: routes reliably across 95%+ of the network, high enough to kill bot economics, low enough that a human doesn't think twice.
On invoice expiry: if the sender doesn't pay within 24 hours, the held email gets dropped. No refund needed because no payment happened. The sender can always re-send and get a fresh invoice. Clean failure mode.
Honestly curious if you'd be willing to test it live — takes 30 seconds. Send any email to [email protected] from whatever address. You'll get an auto-reply with a Lightning invoice. Would love to hear how the payment routing looks from your node's perspective.
On invoice expiry: if the sender doesn't pay within 24 hours, the held email gets dropped. No refund needed because no payment happened. The sender can always re-send and get a fresh invoice. Clean failure mode.
Honestly curious if you'd be willing to test it live — takes 30 seconds. Send any email to [email protected] from whatever address. You'll get an auto-reply with a Lightning invoice. Would love to hear how the payment routing looks from your node's perspective.