You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different from #360; We need to verify if an invoice for the wrong network has been provided, and return an error if that is the case. We'll also need tests, and the necessary upstream functionality.
Hi @cryptoquick and @josediegorobles , we can make solve it, if add optional parameter in invoice called network. This maintain compatibility with other wallets and prevents the problem use invoices in wrong network. Does make sense?
I see. You're right, we may need to add an optional parameter to the invoice then. I'll also tag @dr-orlovsky and @fedsten on this issue so they're aware of the issue.
Activity
oacdutra commentedon Nov 2, 2023
Hi @cryptoquick and @josediegorobles , we can make solve it, if add optional parameter in invoice called network. This maintain compatibility with other wallets and prevents the problem use invoices in wrong network. Does make sense?
cryptoquick commentedon Nov 2, 2023
This should already be on the RGB invoice struct
oacdutra commentedon Nov 2, 2023
Yes, but it is only used in case you know the beneficiary (see here).
cryptoquick commentedon Nov 2, 2023
So, that would be an invoice that includes a blinded UTXO? That's fine I think.
oacdutra commentedon Nov 2, 2023
No, RgbInvoice parse the chain only when beneficiary is a bitcoin address, not when a blind UTXO
cryptoquick commentedon Nov 2, 2023
I see. You're right, we may need to add an optional parameter to the invoice then. I'll also tag @dr-orlovsky and @fedsten on this issue so they're aware of the issue.