pull down to refresh

Does anything speak against decoding the invoice and checking whether the payee public key is the same as the public key of the own node and then just not doing a payment through LND, but instead just moving around some numbers in the internal database?
And to prevent anyone else from paying the invoice afterwards, you can use the CancelInvoice RPC call: https://api.lightning.community/api/lnd/invoices/cancel-invoice/index.html
but instead just moving around some numbers in the internal database?
That's probably how we're going to do it. It would just be nice if we wouldn't need a workaround for this as others have mentioned in the issue.
reply