Description

When generating an invoice, we are restricted to a specific assetID and a single peer. Even if that peer agreed on an RFQ quote with us, they may never be able to forward the payment to us because of their inbound. We should investigate ways of encoding multiple RFQs / entry-points to tapd and escape the single link bottleneck.

Similar to Multi-RFQ send, but a bit more difficult as we need to create a bolt11 compatible invoice that will be payable by all LN implementations, so we can't pull a lot of custom tricks. Multi-RFQ send has the convenience of being resolved within the scope of the local tapd<>lnd.

Items to investigate:

• Even if we did acquire multiple RFQs before creating the invoice, how can we encode them all in the Bolt11 format
• Use blinded paths, which can give up to 3 entry points (possibility for 3 RFQs?)
• Present multiple RFQ with interactive bolt12 offer communication