You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After introducing some modifications to this tool I was able to make it print my set of xprv keys. I was however not able to easily build the output descriptors as the checksums don't match.
These are the output descriptor (templates?) I've got:
This was one idea I had, but I could not make that work, the checksum at the end just wouldn't match. I also tried removing the fingerprints altogether, also to no avail.
Conclusion
I feel like I must have not only all the data I need to reconstruct my wallet, but also clear information about the procedure.
The recovery tool tries to go above and beyond what it should do. It tries to actually move the funds, but that just adds more complications since you now introduce an external dependency in the form of an electrum servers that could fail, leaving you stranded.
This leads to users feeling uneasy and posting things like these:
I don't blame them. Interoperability is super important. And the lack of interoperability of Muun could at least be addressed if there was a way to access the raw private key material.
I propose a modification to this recovery tool that allows it to just spit out nicely formatted output descriptors that you could just save as a text file and then import into bitcoin core or any wallet that supports output descriptors.
The text was updated successfully, but these errors were encountered:
After introducing some modifications to this tool I was able to make it print my set of
xprv
keys. I was however not able to easily build the output descriptors as the checksums don't match.These are the output descriptor (templates?) I've got:
Now what are
58c6e799
&88511559
? I suppose those are the BIP32 fingerprints of the extended privat keys, but I wasn't able to replicate themAlso how am I supposed to turn these templates into actual output descriptors?
This was one idea I had, but I could not make that work, the checksum at the end just wouldn't match. I also tried removing the fingerprints altogether, also to no avail.
Conclusion
I feel like I must have not only all the data I need to reconstruct my wallet, but also clear information about the procedure.
The recovery tool tries to go above and beyond what it should do. It tries to actually move the funds, but that just adds more complications since you now introduce an external dependency in the form of an electrum servers that could fail, leaving you stranded.
This leads to users feeling uneasy and posting things like these:
https://twitter.com/josebitcoiner/status/1570408779694366721
https://twitter.com/BtcAndres/status/1573532712677302274
I don't blame them. Interoperability is super important. And the lack of interoperability of Muun could at least be addressed if there was a way to access the raw private key material.
I propose a modification to this recovery tool that allows it to just spit out nicely formatted output descriptors that you could just save as a text file and then import into bitcoin core or any wallet that supports output descriptors.
The text was updated successfully, but these errors were encountered: