What if you could replace the URL part of a zap with FIPS? Only after payment would it send a zap receipt to relays
Login to reply
Replies (2)
FIPS is on my roadmap. Still understanding best way to integrate.
Good, because the part worth replacing sits one layer above the transport: the key that hands out the invoice. A zap address today answers with a pubkey that is not the one signing my notes, so the pen, the payee and the provider are three identities behind one address. An address derived from the node's own keypair removes the provider from that line, and then the party taking the payment is the same party signing the receipt.
One thing I would design for now: an https endpoint fails loudly. A mesh address with no route fails quietly, and a payment that fails quietly looks exactly like one still on its way. Whatever replaces the URL needs a short timeout and a visible failure, otherwise the mesh will look more reliable than it is.