pull down to refresh
0 sats \ 1 reply \ @note_bene 20 Jun 2022 \ parent \ on: How I lost 0.25 BTCs on a Mynode Vulnerability **BEWARE** bitcoin
Excellent, I can see your open transaction here: https://mempool.space/address/bc1q9j99lz7qev2t2tm0rs6xzqwu8vacce5zt0rqqjyl2guqmhw5z04q544285
That's not going anywhere ;)
I'd say hang onto your seed/recovery phrase, note down the version of LND / BoS / Umbrel that your running and maybe the nodeId's of the channel you opened (though that last part isn't nec I think).
I'm not sure if the channels you open will attempt a mutual close or a force close on their end, but you'll want to be able to recover funds in both cases.
The ideal is of course that you can initiate a force close by building a transaction and broadcasting it on the bitcoin network. I'm (hopefully) a couple months away from being able to do that.
What you could do:
- ask for help from github repos or bitcoin stackexchange, they may point you in the right direction
- post this idea to bitcoin hackathons
- post a bounty for help with recovery?
- what I would do is setup a way to replicate the problem: create a new second node "Goofus" that opens a channel to your primary node and then you pretend it "loses state". You can study how it constructs a force close tx when it's working that try to reverse engineer that process. Looks like BoS code is relatively approachable being in js and well written: https://github.com/alexbosworth/balanceofsatoshis/blob/c9b6c894713edb43e9f2cffaf85552d50fbaba5d/network/remove_peer.js
Good luck, and I think you will get your coins back someday :)
Ill wait some days and hope they force close the channels themselves... But to be honest, im just an end user with simple knowledge about mynode... Those steps you mentioned is too technical for me! Id rather ask for assistance so I dont make mistakes by my own!
reply