When sending assets, the gas fee automatically obtained by the LND node is too small, resulting in miners never packing. What about this?

[fanshome1001]

When sending assets, the gas fee automatically obtained by the LND node is too small, resulting in miners never packing. What about this?
txid : ce3c997a2d055fe1e6e342a65f01c12052a80b5047acf6636e05c05227c268d6

https://mempool.space/zh/address/bc1pzy57gk7h3zx7tn0sxmxkrnws4f2ffv70ucr7j0vjcal3u6qxqr6qpc2spe

[guggero]

What chain backend are you using for lnd? Bitcoin Core or btcd or Neutrino?
You can avoid this if you include a fee rate in the tapcli assets mint finalize call, for example tapcli assets mint finalize --fee_rate=xxx where xxx is in satoshi per kWU (satoshi_per_vbyte * 250), so for example if you want to use 9 sat/vByte, you'd use 2250.
In the upcoming v0.4.0-alpha release this will be easier and the new --sat_per_vbyte flag directly.

[fanshome1001]

I used Neutrino。
What should I do about this deal? Is it possible to withdraw the deal?

[guggero]

What fee URL did you configure? Neutrino doesn't have its own estimation so it relies on an URL to tell you the current fee. It sounds like it gave you a bad fee estimation.
You can accelerate the transaction by attaching more fees to it in a so called "child" transaction. You basically spend the change output of the transaction shown above with a transaction that pays more in fees.
You can use lncli wallet bumpfee ce3c997a2d055fe1e6e342a65f01c12052a80b5047acf6636e05c05227c268d6:2 --sat_per_vbyte XXX, (choose XXX by looking at mempool.space and choosing a high enough value) which when successful will give you a response like {}. But you can then watch the transaction above on mempool.space and see that it'll eventually have its third output being spent and hopefully confirmed.

[jharveyb]

For transfers, the flag to set a manual feerate is --sat_per_vbyte.

[fanshome1001]

When is version v0.4.0-alpha expected to come online?

[guggero]

Soon. A first RC is already available, though I wouldn't recommend updating any production or mainnet infrastructure to it yet.

[jharveyb]

v0.4.1 is now released.