See 2 & 3 here. If this doesn't help then do let us know how many words in your seed and whether all the words are in the dictionary linked on that page in number 3. |
|
|
|
|
install electrum on your server, create a watch only version of your wallet and then have your app interact with electrum over json rpc.
|
|
|
|
|
The risk with pirated windows is that it may be backdoored and you may get robbed because of that. Win 10 ISO is available for free download from the MS website. You don't even have to activate it to start with. Another alternative is to use linux.
|
|
|
|
|
there's a backup wallet option in the file menu of bitcoin qt. then you simply place the backup file in a directory of it's own on the other PC and when you run bitcoin qt for the first time there it'll ask you to set the location of the data dir so you point it to that directory. then wait for it to download and verify the blockchain.
|
|
|
|
edit: no that looks like a permissions issue. i'm not familiar with windows but you may need to install electrum as an administrator. alternatively there's the standalone exe download that just works: https://electrum.org/#download |
|
|
|
you need something written in C and coded to take advantage of GPUs because those tend to be faster at this than CPUs. try hashcat: https://hashcat.net/hashcat/ |
|
|
|
|
The correct way to backup your bitcoin core wallet is to use the backup wallet option in the file menu. Storing copies of private keys may not suffice since your coins will frequently move to new private keys whenever you spend. Storing a copy of the master private key is also not foolproof since it doesn't contain other information about your wallet like the derivation path that was used. So best to use the option provided in the file menu.
|
|
|
|
there is no risk of bitcoin not supporting spending your coins so you don't have to do this. but if you want to do it anyway download and install electrum from electrum.org, create a new wallet making sure to select segwit in step 4 in order to get bech32 addresses and then sweep your private key. |
|
|
|
Private keys are supposed to stay private. If anyone is sharing their private keys with you then they are not your friend and are likely trying to scam you. The correct way to use electrum is to download it from electrum.org and verify the signature of the maintainer. Then you install it and create a new wallet. To receive bitcoin use the receive tab and to send bitcoin use the send tab. Note there are many fake electrum sites that try to fool you into installing malware. If you use those your coins will get stolen. Only download from electrum.org |
|
|
|
Old wallet.dat from electrum is not encrypted unlike now and Electrum right now doesn't have wallet.dat it is a plain wallet file.
Try to open the wallet.dat with notepad it must show your private keys.
This is not true. Even in pre 2.0 versions of electrum you could encrypt the wallet's secrets by setting a password. @OP you should make an issue about your problem on the btcrecover git repo. What's happened is that electrum has upped the wallet version while btcrecover hasn't kept pace. It's not a big problem and I'm sure the btc recover author will issue a quick fix for it. "Quick" obviously being relative to open source development speed. |
|
|
|
|
why do you keep making the same mistake over and over again? Why don't you write down your entire seed?
regarding issue 2 retail is there in the bip39 wordlist so try that instead.
|
|
|
|
note there is no standard for signing messages with bc1 addresses so if you use electrum to generate the signature the challenger also has to use electrum to verify it.
If I remove or change any symbol in the message it gets signed correctly with no problem. But the original message still has an issue.
Can you tell us what version of the electrum you currently use? This is an old issue of old electrum version lower than 3.3.4 if you can use the latest version of Electrum I tried the message you are trying to sign and verify. It's all fine to me so maybe you are using old version of Electrum that is why you are having an issue with verifying a signed message. Yes this is probably it: https://github.com/spesmilo/electrum/pull/5210 |
|
|
|
|
When you tried the xpub thing did the other addresses in that list show up?
|
|
|
|
|
login to your bc.i wallet and go to settings (top right) > wallets and addresses. does the address in question show up under imported addresses? if yes then does it say non-spendable next to it?
|
|
|
|
|
That's the beauty of the blockchain. It's all transparent and no one can deny what happened.
|
|
|
|
|
does the backup key consist of 12 random english words?
|
|
|
|
|
is the file under file > recently open in electrum?
|
|
|
|
|
There's already a way to split the backups between multiple locations, people and/or devices. It's called a multisig wallet and electrum has supported it for years but few users take advantage of it. In some ways it's safer than using SSS because you don't have to reconstitute all the keys on the same device at any point in time. They can remain on different devices and you simply pass around partially signed transactions for signing.
The downside of multisig over SSS is that it costs more in transaction fees than SSS since multisig transactions tend to be larger than single sig ones.
|
|
|
|
|
If the seed is being detected as an electrum seed then that's what it is. The seed he has is not for the wallet with the coins. The OP simply did not backup the seed for his p2pkh address wallet.
It's unlikely that he has a bip39 seed that also validates as an electrum seed. There's also no benefit in creating a bip39 based p2pkh wallet using an electrum seed.
|
|
|
|
a non-airgapped computer is a networked computer and how can using the features of electrum result in seed compromise? what you said doesn't make sense.
If there is a plugin which either asks for you to type in your seed or takes your seed from your Electrum wallet, and splits it in to 3 or 5 or whatever parts, and then displays those parts as text or creates a number of files, all while being non-airgapped (i.e. connected to the internet), then you are at risk of losing your seed to malware which could copy or transmit your "secrets" via the internet. This is the exact same reason why we tell people never to generate a paper wallet on an internet enabled device. My point was that generating your secrets on an internet-connected device is not a smart idea, and I feel an Electrum plugin would encourage that. Electrum itself generates your seed and electrum plugins have access to everything electrum does. Plugins are included with electrum and they are coded by the same developers that make electrum. You don't download them from third parties. So IDK see what the problem is. @OP you could make a feature request on github. there are some similar requests there: https://github.com/spesmilo/electrum/issues/5419 & https://github.com/spesmilo/electrum/issues/5418 |
|
|
|
|
Show Posts
