ffranr

I think we should close this issue in favour of https://github.com/lightninglabs/taproot-assets/issues/874 . There are other solutions to this problem that we could implement. For example, opting for a larger on-chain...

This RPC endpoint should return a status channel instead of directly providing an invoice, given that invoice generation can be time-consuming due to processes like RFQ negotiation, universe synchronization, and...

I don't think we've got a solid plan in place for this issue. Right now, for the PoC, this functionality is in lightning terminal.

I recommend we consider the following points: 1. Users of stablecoins may primarily be interested in asset groups rather than individual asset IDs. It may be beneficial to default to...

As far as I'm aware, this PR isn't ready for me to review. So I'm going to remove my review request to keep my review request list short. Please re-request...

To address this issue, I think it's sufficient to concentrate on this type introduced in PR https://github.com/lightningnetwork/lnd/pull/8622 : ```go // AuxFundingDesc stores a series of attributes that may be used...

> > And then the question becomes: are those fields sufficient to setup a tap payment channel? I think the answer is yes. Do you agree @guggero ? > >...

I've unassigned myself. There is nothing for me to do here. Oli is writing the code for this issue.

The changes I think we should make to RFQ section of the tap BLIP can be found in these reviews that I've left on the tap BLIP PR: https://github.com/lightning/blips/pull/29#pullrequestreview-1848901112 https://github.com/lightning/blips/pull/29#pullrequestreview-1853954713...

Corresponding PR: https://github.com/Roasbeef/blips/pull/4