|
Edit your first post, add "[solved]" to the "subject"... Then, after you have saved that edit, there should be a "lock thread" link, right at the bottom on the left hand side, just above the "quick reply" box...
Click that to close the thread so no more posts can be made
|
|
|
|
I have the Public Address, Private Key (Encrypted), Checksum stored off-line. And the password I know off by heart.
Ahhhh.... Right. I think I get it now... You have the paper backup from strong coin, correct? Something like this:  If that's the case, then the ONLY way to decrypt this is by using Strongcoin's service... If it says the password is incorrect, then you have the password wrong... Perhaps you typed it incorrectly when you first created the wallet? |
|
|
|
Then the private key you are trying to sweep is not for address: 1Hefr1NLzABVZhK9Kh7XSB55xRFtK5ex6e Just confirm that your private key starts with a "5" or a "K" or an "L"??... DO NOT post your private key here!  It's possible that this might be a compressed/uncompressed key issue... Very unlikely, but you never know... I'd suggest that you try using an offline copy of www.bitaddress.org and on the "details" tab, pasting in your private key and seeing what addresses it actually generates. If you see the "1Hefr" address shown, then double check that the associated private key in WIF format is the one you're actually trying to sweep |
|
|
|
Theoretically, if you copied across the ".wallet" files, you should be able to open those up and wait for them to sync up. It might take a while... I'm not even sure if it's possible any more due to MultiBit dropping support... As I'm not sure if the apps connect to general Bitcoin peers or MultiBit specific servers??!? Anyway, regardless of whether or not it's synced, you should still be able to use "Tools - export private keys" to get your private keys out... These can turn be imported into another lightweight wallet like Electrum. MultiBit made a video about it: https://www.youtube.com/watch?v=LaijbTcxsv8The trick is to NOT password protect the output file! That way it's in plain text and can be opened with a text editor so you can copy paste the keys to the new wallet |
|
|
|
If you store coins or tokens in a hardware wallet, they are stored in the hardware wallet and not in the device you use to access it.
The coins are not even stored in the hardware wallet... They're stored in the blockchain. In a lot of cases, not even the private keys are stored on the hardware wallet... It is the SEED which is used to generate the private keys which is stored on the hardware wallet. This seed is then used to recreate private keys etc when you unlock the hardware wallet for use. Your backup for your hardware wallet is your 24 words that you've carefully written down and stored safely... Which you did... right? |
|
|
|
When you say you have the "paper wallet's Public Address, Private Key (Encrypted), Checksum and password I used to encrypt my account" do you mean you have all this information written down? Or just that you think you know what the password is? BIP38 encrypted Paper Wallets can be tricky... And I remember there was a bug ( https://github.com/pointbiz/bitaddress.org/issues/56) where depending on what browser you used, you could only decrypt in that same specific browser!  Do you remember how you created the paperwallet in the first place? |
|
|
|
Yep, you're right... I got myself confused with all the TrustedCoin entries I had in GAuth!  After I put the "I've lost my GAuth" code in, it was generating different OTP codes to the existing ones... But have now realised they were for other test wallets! DOH! I've tested this with what I know is the same seed and regardless of whether you just enter the original or select "I've lost my Google Authenticator" and get a "new" key... It generates identical OTPs... So yes, if someone has your old wallet+old phone, they could theoretically spend your coins! |
|
|
|
No, that is incorrect... The offline wallet will still be able to sign the transaction, regardless of whether or not it has "generated" the address. I've tested this. I've sent a bunch of transactions and generated over 10 change addresses in my "watching only" wallet. Offline wallet only has the initial 6 change addresses. Using coin control, on the online watching wallet, I have selected an UTXO sitting in a change address that is NOT showing in the offline wallet. I created an unsigned transaction spending that UTXO, transferred the transaction to the offline wallet and then signed it without any error... Then transferred the signed transaction back to the online wallet and broadcast or without any problems. The address list in offline wallet still only shows the initial 20 receive addresses and 6 change addresses. For good measure, I then spent the resulting change from that transaction as well... And then the next one I believe that when you create the unsigned transaction, it is including info that allows the offline wallet to derive the correct private key that it needs to sign the transaction with. Honestly, you really shouldn't need to mess with the gap limit, unless you are restoring your wallet and you have "missing transactions" due to having generated and used extra addresses manually prior to restoring the wallet, or you want to create an address pool larger than the default of 20 receive. And you certainly wouldn't need to update the gap limit everyday... As addresses are used and the transactions become confirmed, the wallet will generate new addresses to keep the address pool stocked. |
|
|
|
A noble idea... But good luck with that. Go read the "beginners and help" section of you want to get an idea of the "lowest common denominator" when dealing with crypto.  All the information is freely available, but it's the same things over and over... And people who simply cannot grasp that the fees are NOT charged/collected by the wallet... But required to get miner's to include your transaction in a block. The number of "which wallet has the lowest fees?" threads is proof that people just don't "get it". Too many folks just don't want to take 5 minutes out of their life to read and educate themselves... But will then spend hours whining about how Bitcoin is isn't ready for the mainstream and is too complicated and "technical" when they screw something up and lose coins or transactions get stuck. |
|
|
|
I'm kind of at a loss here... If you have imported the private key (not seed) and it shows that exact address, then it should show the 0.5 BTC balance!!?!  Time for another stupid question... You have checked the ENTIRE address for correctness... Every single character? I know I'm bad and usually only check the first 4 or 5 characters and the last 4 or 5. Can you tell I'm grasping at straws here? Maybe see if you can create a sweep transaction? In Electrum, goto "wallet -> private keys -> sweep"... Input your private key (and a receive address if you want to send to a different wallet) and see if it says "no inputs found" or it comes up with a "send" dialog... Other than that, I'm not sure what else to try? |
|
|
|
OK. But how the online wallet(W2) knows whether the new address is produced by the offline one(W1). I could use the online wallet to send transactions even the address and private key are produced by another wallet, for example, BitCore-Qt wallet. Is there any calculation or algorithm behind the checking?
No, you couldn't use an address and private key from another wallet... Electrum HD wallets DO NOT allow you to import private keys. They can only ever hold the keys/addresses generated from your seed. So, both the online and offline wallet use the same identical Master Public Key. This is the "starting point" for address generation, so both wallets will generate identical lists of addresses... Forever! Since the new addresses is produced after the Wallet is created, and the gap limit is 20 by default. If I recover from the seed, I think only 20 addresses are produced by default. If you are correct, is that possible the new address is not in the 'address' list by default ? I have to create new addresses and wish it shows up.
The "gap limit" is simply how many consecutive "empty" addresses need to occur before the wallet stops looking for more used addresses after the wallet is restored. So, if you have used say 14 addresses, and then wipe your computer and restore your wallet... During the restore, it'll find the first 14 addresses have been used... Then it will find 20 empty ones and that triggers the "gap limit" functionally, so it'll stop generating and checking addresses... And you wallet will now have a total of 34 addresses in it. Also, each time you use an address, Electrum will automatically generate a new address out to the gap limit to maintain a pool of unused addresses. You should not need to modify the gap limit unless you're constantly generating an enormous amount of addresses and receiving payments to them "out of order"... More likely in an ecommerce setup as opposed to a cold storage scenario |
|
|
|
|
Most likely the config file getting corrupted during a crash and Electrum recreating it and your options going back to default.
Otherwise, no options are ever modified without being done so by the user. Not even during install of an updated version.
So, you might want to just double check that ALL your Electrum settings are correct!
|
|
|
|
|
You have setup a 2FA wallet. It probably says on the title bar of the Electrum window [2fa]...
When you type your seed in, before you click next, does it say "seed type: 2fa"??
To set this wallet up you would have had to create a Google Authenticator entry using the 2FA key from TrustedCoin, you cannot complete the wallet setup/creation without entering a valid 2FA Google Authenticator code!
To get around the issue, try and restore your wallet, choose "Wallet with two factor authentication"... choose "I already have a seed""... Andwhen it asks if you want to "keep" or "disable" 2FA functionality, select "DISABLE".
If you're still getting "please wait", that's most likely a directory permissions error... Try running the app as Administrator and/or using the Windows Full Installer instead of standalone.
I would also recommend that after you get your "disabled" wallet restored... That you create a new "standard" wallet with a new (standard) seed and send all you coins to the new wallet to prevent any issues in the future
|
|
|
|
Proof of work? Electrum is a light weight SPV wallet... It doesn't do block validation etc. It leaves all the "heavy lifting" to Electrum servers (which generally rely on Bitcoin Core to download and verify the blockchain) The is some block header validation of that's what you mean: https://github.com/spesmilo/electrum/blob/master/lib/blockchain.py |
|
|
|
Can you confirm that you actually have "use dynamic fees" checked in "Tools -> Preferences -> Fees"? I find it hard to believe that Electrum selected a fee of 50 sats/byte for max dynamic fee!!?! Especially given recommended fees have been as high as 300+ the last couple of days! Have you unchecked the box and do you have "max static fee" set to 0.0005 btc? |
|
|
|
|
Sorry, is this MultiBit "Classic" or MultiBit HD?
Given you were shifting files around rather than restoring using wallet words, I'm guessing it was MultiBit Classic?
It's possible that your wallet file is just unable to sync up due to MultiBit Classic being very old, outdated and no longer supported...
Which files did you copy over? Was it the multibit.wallet file? Did you copy over anything else?
|
|
|
|
"How long is a piece of string?" No one can answer your question except you... However I would say that "right now" is not a good time to be moving bitcoins as the network is REALLY busy... The fees are likely to be really high due to the large number of unconfirmed transactions https://blockchain.info/charts/mempool-counthttps://btc.com/stats/unconfirmed-txhttps://bitcoinfees.21.coEspecially from a wallet like Jaxx that doesn't give you "true" custom fees The number of unconfirmed transactions does seem to be dropping (still above 30K though)... So keep an eye on the mempool count and recommended fees and send when the network is less busy! |
|
|
|
For example, you should NEVER install both Bitcoin Core and Bitcoin ABC (Bitcoin Cash) in the same computer. Those are coded with the same path to the data directory.
Minor correction: they're both coded with the same DEFAULT install and data directory paths. Both of which are easily customisable. You can safely run Bitcoin Core and Bitcoin ABC on the same PC. I currently do this and as long as you set them up properly, and don't just blindly click "next" during install and setup, they'll happily run side by side without interfering with each other |
|
|
|
|
The 2FA key has nothing to do with decoding the wallet... The 2FA key is simply the key generated by TrustedCoin and given to you, so you can create the necessary Google Authenticator app entry... And start generating time based OTPs (one time passwords)
When you restore your 2FA wallet, and select to "Keep" the 2FA functionality, it'll ask you to confirm your current code from Google Authenticator app (to prove you still have it)... Or you can reset it ( "I don't have my Google Authenticator code" option)
If you enter the current GAuth code, you can just continue using it... However, If you reset it, then you'll be given a new 2FA secret key which you must enter and sync up with Google Authenticator App and use for all future transactions... The old one will no longer work, as TrustedCoin will have changed the matching key on their end. - WRONG... You get the same GAuth code regardless
|
|
|
|
|
Show Posts
