|
Sounds like there is an incorrect signature in your transaction... what is the history behind this transaction?
Are you attempting to send a BCH transaction on the BTC network? or perhaps a BTC transaction on the BCH network?
|
|
|
|
|
It sounds like you might have some weird permissions error...
Also, does you windows "username" use "non latin" characters? ie special characters with accents like õ ÿ û, cyrillic, or asian characters etc?... It's possible that the app is struggling to find the Electrum data directory in your "C:\Users\YOURUSERNAME\AppData\Roaming\Electrum" folder if "YOURUSERNAME" has "non latin" characters...
|
|
|
|
This thread is CLOSED.
Pretty sure it isn't...  PROTIP: you probably want to click the "lock thread" link at the bottom of the page, just above the "quick reply" box... #justSaying... |
|
|
|
That 0.34 is your "change"... you spend an old input worth 0.84... but you were only spending 0.5... so you got "change". refer: https://en.bitcoin.it/wiki/Change for more info on Bitcoin and "change". In other news, your transaction got confirmed! YAY!  |
|
|
|
You problem is two-fold... 1st issue: It would seem that your 0.045 btc is made up of a LOT of inputs... how many individual inputs do you see if you click on the "Coins" tab ("View -> Show Coins", if you can't see the "Coins" tab)... I'm going to guess you have upwards of 10-15 inputs... Each input you have, will be adding something like 148 bytes to any transaction you're attempting to create. 10 inputs will mean a transaction size of around 1500 bytes... as fees are determined on a sats/byte or btc/kB basis, it follows that the larger the transaction data size in bytes... the larger your fee is going to be. 2nd issue. Due to the current network congestion, 150,000+ unconfirmed transactions etc... network fees have risen to simply INSANE levels... fees have been upwards of 1500 sats/byte... even now the recommended fees are like 1000 sats/byte... now... lets do the math... say you only have 10 inputs -> 1500 byte transaction... fee of 1000 sats/byte... -> fee = 1500 * 1000 = 1,500,000 sats = 0.015 BTC!!?!  If you set up your transaction, and click the "preview" button, it should show the size of the transaction in bytes... if it is as I suspect (ie. > 1500-2000 bytes), it would appear your 0.045 BTC is made up of a lot of dust sized inputs  Your solutions are either use a "manual" fee and put in a tiny fee and wait about 4 or 5 days for your transaction to confirm because it will get stuck with such a "tiny" fee... or wait until the network is not as congested and fees return to a more reasonable level |
|
|
|
You sent a transaction that was 2551 bytes!!?! That's about 10x the "average" transaction size of around 226 bytes (1 input + 2 outputs)... Given that fees are just insanely high right now... transaction fees are at an all time high... upwards of 1000 sats/byte... you paid a fee of ~15mBTC/kB... or around 1500 sats/byte your transaction was 2.5kB... ergo you paid 2.5 (kb) * 15 (mBTC)... or ~38 mBTC... it's basic maths. |
|
|
|
|
Restore the wallet... select "Wallet with two-factor authentication" and put in your 2FA seed, when it asks if you want to "keep or disable" select "Keep".
It should ask for your Google Auth code, select the "I have lost my Google Authenticator", re-enter your 2FA seed when prompted and it should then give you the 2FA secret and QR code for setting up your Google Authenticator again.
|
|
|
|
|
Load up a "proper" file explorer app... there are about a billion on the Play Store... as your phone doesn't have an external SDCard, you will probably be wanting to look on the "internal storage" and it should be relatively easy to locate the "Download" folder...
What Make/Model of phone do you have? What version of Android is it running?
|
|
|
|
You should post your log files using www.pastebin.comIt has a much larger max size and it really helps keep the thread nice and neat... copy/paste your log file into pastebin, "create" the paste and then post the unique URL that pastebin generates for your "paste" here... |
|
|
|
A couple of questions... What version of Armory are you using? (given your mention of contacting "Bitcoin Armory", I'm going to assume you used an old version from the old website). The latest versions are available here: https://github.com/goatpig/BitcoinArmory/releases I recommend using v0.96.4 RC1 (aka v0.96.3.99) Do you have Bitcoin installed? If so, what version of Bitcoin Core are you using and is it fully synced? NOTE: DO NOT use: https://www.bitcoinarmory.com/ it is old and outdated and no longer the official website... go here: https://btcarmory.com/ |
|
|
|
|
If you have the wallet file... there is no reason NOT to give btcrecover a try to try and find your wallet password... it can't hurt.
As for whether or not your password is 100% correct, it's difficult to know if you have the wrong password, or the file is corrupted. Although, generally if it is corrupted, it will still decrypt the file OK, but just give you rubbish data... so my bet is that the password you have is wrong.
|
|
|
|
You don't need to do anything. There are a LOT of (opensource) applications and tools that support BIP39 seeds. If you're concerned, I'd suggest downloading and keeping a copy of the current version of Electrum as that definitely support BIP39. At worst, if Electrum suddenly decided not to support it any longer, you could fire up the old version, import your seed and dump out the private keys... Alternatively, create an offline copy of Ian Coleman's brilliant BIP39 tool ( https://iancoleman.io/bip39/) It requires no internet connection to work (and you should run it offline anyway)... It is able to convert BIP39 seeds to the addresses/public/private keys using whatever Derviation Path you require (m/0' and m/1' for MultiBitHD)... |
|
|
|
If you have a "vague" idea... you might be able to use btcrecover ( https://github.com/gurnec/btcrecover) It requires you to be able to install and use Python... although the instructions are relatively easy to follow. The hardest part is creating the correct "token" file that the script uses to generate the passwords guesses. NOTE: I think btcrecover requires you to have the wallet file... not the encrypted private keys. If you only have the encrypted private keys... you'd probably need to use hashcat or some other app that can try and bruteforce passwords on AES256 encrypted files |
|
|
|
|
No. BCH network uses full 2-way replay protection... a BCH transaction is NOT valid on BTC network... and BTC transaction is NOT valid on BCH network.
All you're at danger of is a BCH wallet potentially stealing/exposing your seed/private keys which would put your BTC at risk. Having said that, I'm not aware of anyone who used the "OFFICIAL" Electron Cash client having their wallet, seed or private keys compromised.
|
|
|
|
What tool are you using for generating your addresses online? Are you using Ian Coleman's BIP39 tool ( https://iancoleman.io/bip39/)?If so, it sounds like the Derivation Path you are using is only showing "External" (aka "receive" addresses)... |
|
|
|
|
Did you come from MultiBit CLASSIC or MultiBit HD? It's important to know what information you used to get your BTC into Electrum...
Did you use private keys... or a MultiBit seed?
|
|
|
|
... When I imported the key address into my wallet on blockchain it shows the value of .1 BTC. I peeled the hologram off the coin and it has the private key on the back but when i type in the private key to try and send that value to my wallet it says the private key doesn't match the coin's address. Am I doing something wrong or am I screwed here? Any help is appreciated.
I assume you mean you have a blockchain.info wallet... b.info seems to have a lot of issues with imported keys and compressed/uncompressed addresses. It is possible that the key you have is correct, but b.info is generating the incorrect address for it... To fix this (and double check that the private key you have matches the public address you have), try the following: 1. Create an offline copy of https://www.bitaddress.org (basically, click the "zip" link at the bottom of the page and then extract it)... 2. Run your "offline" copy while your computer is not connected to any network... 3. Click the "wallet details" tab 4. Enter your private key in the textbox and click "view details". You will see two addresses: "Bitcoin Address" and a "Bitcoin Address Compressed", below that you will see two private keys: "Private Key WIF" and "Private Key WIF Compressed"... match the right private key with the public address that has the 0.1 BTC... that should be the private key you want to import... If that doesn't work, try importing the OTHER private key and see if that works! (Yes, that's how broken b.info is!!?!  ) |
|
|
|
|
Show Posts
