If using chrome/FF/IE, the reverse is true. *** Using the 'wallet details' tab on to decrypt the BIP38 key, if using safari, the safari-generated key (_9q) works, and the other-browsers key (_XA) fails to decrypt. And I'm getting browser-dependent results: What I do is I fire up, open up the "wallet details" tab, and use this to decrypt my "6P." keys. I've been using to check the validity of my BIP38 wallets. Hard to test because I don't think will let me BIP38 encrypt my own vanity address or brain wallet.īut here's something you can replicate / experience. I'm not sure if this is my own bug, or something native to the BIP38 implementation I'm borrowing from. If I use Chrome / Firefox / IE and encrypt with घोडा स्टेपल, I getĦPRNXA7M4qEppBJCHM2SEizfna7XTomzXwdCBrEG6Mjo3nU6iziS6vWWXA If I use Safari to encrypt with घोडा स्टेपल, I getĦPRNXA7M57uqSYXX2TXHkfNJEVMiWarkPkqUv3AsZa5r41u3VpXHLkUD9q WIF key 5J4pcwBDPwPY1cdNqxTdmZWr7圜K8rXi9avFvezgYbmoatJpKGn Public key 1ABCDF5v4oaodTPYnKfYvkfwuoa8PJkjMC
#DOWNLOAD SAFARI MAC OS X LION 10.7.5 FILE HIPPO GENERATOR#
My own BIP38 generator is, weirdly enough, giving me two different BIP38 encodings for the same wallet, whose details are: I've been doing some testing with BIP38 decryption at and ran into a funny issue when encrypting/decrypting wallets using the passphrase "घोडा स्टेपल" (no quotes) - which is what you get when you use google translate to translate "horse staple" (no quotes) into Nepali.
0 kommentar(er)
