Skip to content
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

HELP. Funds stuck in node after channel open RBF #7795

Open
themikemoniker opened this issue Nov 7, 2024 · 2 comments
Open

HELP. Funds stuck in node after channel open RBF #7795

themikemoniker opened this issue Nov 7, 2024 · 2 comments

Comments

@themikemoniker
Copy link

themikemoniker commented Nov 7, 2024

Issue and Steps to Reproduce

I am having some issues recovering some funds from a channel open that i erroneously RBF-ed. I am trying to construct and sign a PSBT to get my funds back. When I try to sign my psbt I get this error

{
   "code": -1,
   "message": "No wallet inputs to sign"
}

Any suggestions? Is it safe to do dev-forget-channel? I think my channel (that points to the old txid, which will never confirm) may be conflicting with the output I am trying to spend.

the channel point (2-of-2 multisig output) does not appear in listfunds but the change output appears and is not reserved.

admin@<REDACTED>:~ ₿ cl listfunds
{
   "outputs": [
      {
         "txid": "<REDACTED>",
         "output": 1,
         "amount_msat": <REDACTED>,
         "scriptpubkey": "<REDACTED>",
         "address": "<REDACTED>",
         "status": "confirmed",
         "blockheight": <REDACTED>,
         "reserved": false
      }
   ],
   "channels": [
      {
         "peer_id": "<REDACTED>",
         "connected": true,
         "state": "CHANNELD_AWAITING_LOCKIN",
         "channel_id": "<REDACTED>",
         "our_amount_msat": <REDACTED>,
         "amount_msat": <REDACTED>,
         "funding_txid": "<REDACTED>",
         "funding_output": 0
      }
   ]
}
### `getinfo` output
{
   "id": "<REDACTED>",
   "alias": "<REDACTED>",
   "color": "<REDACTED>",
   "num_peers": 1,
   "num_pending_channels": 1,
   "num_active_channels": 0,
   "num_inactive_channels": 0,
   "address": [
      {
         "type": "torv3",
         "address": "<REDACTED>",
         "port": 9736
      }
   ],
   "binding": [
      {
         "type": "ipv4",
         "address": "127.0.0.1",
         "port": 9736
      }
   ],
   "version": "v24.08.1-modded",
   "blockheight": 869205,
   "network": "bitcoin",
   "fees_collected_msat": 0,
   "lightning-dir": "/home/bitcoin/.lightning/bitcoin",
   "our_features": {
      "init": "08a0800a8a59a1",
      "node": "88a0800a8a59a1",
      "channel": "",
      "invoice": "02000002024100"
   }
}
@vincenzopalazzo
Copy link
Contributor

Hey do not worry,

Let's see if we can help you in some way.

Can you specify what command did you run, and what is the status of the tx?

If you do not feel comfortable with sharing this information in public, please consider to send an email (by using my gpg that you find in github) there are a lot of scammers out there

@chrisguida
Copy link
Contributor

This has been resolved btw

Ended up hacking hsmtool to extract the channel keys chrisguida@b02bcb6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants