ONCHAIN: 1 outputs unresolved: waiting confirmation that we spent DELAYED_OUTPUT_TO_US using OUR_DELAYED_RETURN_TO_WALLET #7460
Milestone
Comments
|
I've been trying to broadcast the transaction by increasing my bitcoind mempool size. Now I do not get the transaction rejected because of low fee but because of locktime. At this point I don't understand, locktime was 288 which is long ago. Anything I am missing here? This is the extract of listtrasactions of what I understand is the sweep transaction: |
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Aug 13, 2024
Our hash tables allow duplicate keys, and we use that in a few places. However, the get() function only returns the first, so it's not a good idea with such hash tables. Another patch fixes this at a deeper level (using different hash table types depending on whether this table can have duplicates), but this is the minimal fix for existing code. This may be the cause behind us occasionally missing onchain events: Fixes: ElementsProject#7460 Fixes: ElementsProject#7377 Fixes: ElementsProject#7118 Fixes: ElementsProject#6951 This fixes them in future: fixing them now will require something else. Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: lightningd: occasionally we could miss transaction outputs (not telling gossipd, or even onchaind)
ShahanaFarooqui
pushed a commit
that referenced
this issue
Aug 13, 2024
Our hash tables allow duplicate keys, and we use that in a few places. However, the get() function only returns the first, so it's not a good idea with such hash tables. Another patch fixes this at a deeper level (using different hash table types depending on whether this table can have duplicates), but this is the minimal fix for existing code. This may be the cause behind us occasionally missing onchain events: Fixes: #7460 Fixes: #7377 Fixes: #7118 Fixes: #6951 This fixes them in future: fixing them now will require something else. Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: lightningd: occasionally we could miss transaction outputs (not telling gossipd, or even onchaind)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue and Steps to Reproduce
I have had some funds in limbo since a couple of months and today I am finally filling an issue.
Long story short, somebody took my liquidity offer and after a few minutes they sent an error and force closed. The problem for me has been that I can't move my utxo because it is stuck with a fee of 122 sats.
I have tried to sendrawtransaction (as it appears in listtransactions) but it is below the lower limit. I have also tried to withdraw using the tx:vout that holds the coins, but the wallet does not accept it as input. Any suggestion on how to recover it?
This happened running v24.02.2 but now I am running v24.05.
Other issues maybe related: #7377, #7118, #7206, #6951
Some outputs.
The text was updated successfully, but these errors were encountered: