#@Brendan | WhisperNode FYI, I pushed up

1 messages · Page 1 of 1 (latest)

chrome fog
#

What do I input here:

Which account would you like to recover?

It's returning invalid string

hollow stirrup
#

should be the alias you originally entered in the account - it looks up that key under secret_keys.

#

so it would be the same value as --alias in the CLI

hollow stirrup
#

I have private key from wallet.toml decryption working! I will clean things up and update my branch shortly

hollow stirrup
#

Ok, it's working very well now. On the add-wallet-import branch, just do a git pull and cargo run! The value after Recovered secret is what you can import into the extension (do this in a test browser - validation will fail if you try to import an existing address). This tool also outputs the public key and address so you can verify quickly

hollow stirrup
#

Also figured out how to get the hex private key from a Namada CLI key export - exporting from the Namada wallet saves a binary file, but you can get the hex representation of the key like this (assuming export file is key_tester, and you have xxd installed):

xxd -l 34 -c 34 -p key_tester

That's the same key my util outputs

#

@chrome fog one last thing: I made a copy of the wallet you shared with this alias: whispernodeđŸ€ - I was able to enter that in as the account alias 🙂 So, it should work just pasting that in when prompted!

chrome fog
#

Ok awesome going to try in an hour or so! Thank you so so much for all this help. If this works you’re a legend
I’ve been so scared about losing this wallet for some time now and no one has had answers!

hollow stirrup
#

It’s no problem! Let me know how it goes. I’d still like to figure out the derivation from mnemonic issue at some point too, if I come up with any bright ideas I might ping you to try!

chrome fog
#

Having an issue with the stupid alias. In termius it pastes as "whispernode ^= ^p"

#

Unable to load data from `wallet.toml`: TOML parse error at line 8, column 150

#

invalid basic string

hollow stirrup
#

Ah. Ok, we can work around that. Open the wallet toml and just change the key to simply “whispernode” or anything, under “secret_keys”, and use that key instead when prompted, then it shouldn’t be a problem. I was using the Kitty terminal with no issue, but yeah just change the key name!

hollow stirrup
#

quick note: I did verify that the encryption/decryption algorithms used on Namada as of Feb 2023 (around v0.14.0) do match this util, so it should work on current and old wallets. At worst I imagine there might be minor changes I would need to make to the util to match the serialization of old wallet TOML, but I imagine it's close if not already correct. LMK if there are any issues!

#

reason I checked is because they changed a password KDF function to use a different value, so on ancient wallets, the same password wouldn't work on new wallets. Turns out that only matters if your wallet was made on or before Namada v0.7.1, so should be good as is!

chrome fog
hollow stirrup
#

Awesome!!! Glad to hear it. namadaw or namada wallet has an import sub-command that expects a file, though I think it might expect the format exported by the CLI, which is binary. It may be as simply as copying all of the relevent sections from the old wallet file to the new one. Since the encryption is the same, it should work just fine to do that!

#

Actually, namada wallet might handle unencrypted just fine too, the only difference is it expects a prefix of 00, it's a weird artifact of serialization. And also not sure if importing an unencrypted private key will encrypt it in the new wallet. Might be easiest to copy all of the related lines (e.g., secret_keys, public_keys, pkh, addresses, path) from the old wallet (basically anywhere that has whispernode... copy to to the relevant section in the new wallet.toml)

chrome fog