-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue] Anchor output reserve - can't open channels #5866
Comments
Yep, the wallet should not indicate that those coins are available, when in reality they are reserved. There should be a clear distinction between available and reserved coins. This also do break many scripts, wallets and interfaces, so I don’t think it is an issue, but a clear bug. |
This should be fixed by: #5665 The fix is in master, and will be a part of the 0.14 release. The reserve check wasn't taking into account change outputs. So if you have a single UTXO, then it would prevent you from opening a channel. A short term work around is to ensure you have multiple UTXOs before opening a channel. |
Ok, as I mentioned in edit part, I sent to another UTXO 100k (that is supposedly the higher limit to have as reserve). You said to have multiple UTXOs. But how will be decided, next time when I will open another channel? What is are used all of them? |
After the transaction has been crafted, so if it ends up combining that UTXO, then it'll run into the same condition on anything before master or 0.14.
Read my message again, it's a bug that's been fixed. You do in fact have coin selection if you use PSBT to fund the transaction or any one of the manual means.
That's the correct option, but once you've opened a single anchor channel, then system will ensure you have UTXO reserved since if you empty the wallet, fee bumping would require manual intervention. Closing the issue as it's been resolved. |
Now I have many examples of nodes that are fucked up because of this anchor bug. More cases here |
The fix of this issue deserve a new version. Lot's of our users have issues caused because of this. |
@Darth-Coin are you able to repro w/ lnd 0.14? |
Thanks for asking. Not yet. I am waiting for Umbrel devs to update the backend to v0.14. What should be the behavior now? Questions:
|
Hello, I'm getting |
Adding |
Anchor channels allow your node to increase the fee of a published commitment transaction. In order to do that, your node needs to maintain a certain amount of funds on-chain. If you ensure you have at least a single 100k satoshi output on-chain, then you'll be able to use everything as normal.
Adding that doesn't disable this check. The check is still executed as long as any anchor channels are open. Creating new channels will increase the amount of reserved funds up to 100k sats total. Note that anchor channels are safer than non-anchor, as they actually allow the commitment fee to be increased in a high fee rate environment. Otherwise, it's possible that you aren't able to publish your commitment transaction (to enter the mempool), meaning it can't be mined. |
Thank you for your explanation. I understand it now. |
Yes, today I could test it. Had 5 UTXOs with various amounts and 1 UTXO with 100k sats. Total was like 665000 sats |
Just wanted to add as Darth said above that I had exactly the same experience on v0.14.1, today. Would be good to have a small addition to the error to know that you can rerun the open at a reduced size, |
I wonder if all these genuine questions are solved with the latest version... Im experiencing the same when trying to open a channel with a single utxo in my wallet atm... |
Background
Tried to open a channel, peer is online, I have enough funds in onchain, like 2.7M sats in 1 UTXO.
I always get an error that doesn't say too much:
reserved wallet balance invalidated
Your environment
Steps to reproduce
I used RTL, Thunderhub, Umbrel dashboard, lncli, Zap mobile/desktop, Zeus to try to open a channel of 2 or 2.5M sats
Error in RTL: reserved wallet balance invalidated
Error in Thunderhub: failed to open channel
Umbrel: reserved wallet balance invalidated
Zap, Zeus: reserved wallet balance invalidated
lncli: rpc error: code = Unknown desc = reserved wallet balance invalidated
Whatever amount I put, is the same message, that doesn't say too much, what should I do or how to fix it.
I looked for more documentation and I found that is due to new feature release of anchor output reserve, but there is no place to explain how to deal with this "reserve", there's no specific amount that user can know to keep or use in "reserve", nothing.
I tried also disabling this feature editing the lnd.conf file with
[protocol]
protocol.no-anchors=true
restart lnd, tried again, same error
Expected behaviour
Actual behaviour
Can't open channels and also I don't know or calculate how much I should have in "reserve".
Right now is just confusing, how much is in "reserve" and how much is available to spend. nobody knows that, none of wallet apps is showing that.
This will just create more issues and chaos with so many noobs running nodes.
Please advise how to deal with this. Make a specific documentation for users, it is very confusing.
Additional references
https://bitcoinops.org/en/topics/anchor-outputs/
#5599
#5648
I also posted some requests / fixes to these apps, to see if more people come up with a nice solution:
Ride-The-Lightning/RTL#833
apotdevin/thunderhub#352
getumbrel/umbrel-lightning#29
EDIT
additional test:
I sent 100k sats to a new UTXO to the node wallet.
Still doesn't let me to open a channel with the 2.7M sats, whatever amount I try to use.
This is getting ridiculous.
Another question: when I open a channel how do I know that is not taking from this "reserve" UTXO, how do I make coin control when I open a channel in TH, RTL, Zeus, Zap etc...
The text was updated successfully, but these errors were encountered: