The service you posted its link has proven to be a scam. Op dont waste your time with them.
Do you have a source for this?? I was under the impression that Dave and wallet recovery services were fairly legit... |
|
|
|
|
Check the network settings... ElectronCash (and Electrum) needs to download and sync the block headers to verify the transactions... It'll show unverified of it isn't synced right.
If you look at the network settings and the number of blocks isn't equal to the current height of the appropriate blockchain, then the transactions won't show up properly.
If the number is correct, then the headers file might be corrupt, so you may also need to shutdown the app and then delete the block_headers file from the ElectronCash/Electrum data directory. Then reopen the app and let it rebuild...
Again, open the network settings and watch the block count increase until it gets back up to the current Blockchain height 483,000+... It's about 40megs of data so should only take a few minutes on a halfway decent internet connection.
Finally make sure the server you're connected to is appropriate for the Blockchain (BTC or BCH etc)
As for the balance being different, any BTC received after 1 Aug won't reflect in BCH... Also do you have multiple "accounts" in mycelium?
|
|
|
|
Not sure where you're looking on bitcoinaverage... but when I click that link I see: Today's Open $4,942.17 Today's High $4,984.50Today's Low $4,589.02 USD Index $4,719.87 24h Average $4,849.92 Global Vol ฿ 113223.61 Sure looks like it made it over $4969.38.   Just checked right now and the app says $4779... bitcoinaverage website says $4729... seems pretty close... I'm assuming that the app doesn't update in real time like the website. Welcome to the wonderful world of volatile crypto currency values   |
|
|
|
These days you should be able to import your Mycelium seed directly into ElectronCash and/or Electrum (using v2.9.0 or higher). Just make sure to click the "Options" button during seed entry and select "BIP39” seed. You should then be prompted for the derivation path... Which should be set to m/44'/0'/0' If using ElectronCash, it should recreate the BCH addresses and you should then be able to send the BCH wherever you want (same as sweeping). If using Electrum, you should see your BTC wallet, addresses and transactions and be able to export private keys for the addresses you want. If you want a specific private key, then you can either import the seed into Electrum/ElectronCash and then export the private key for the address you want... Or you can use the BIP39 mnemonic code converter ( https://iancoleman.github.io/bip39/) as I mentioned earlier, as that will display addresses AND matching private keys |
|
|
|
|
Does your seed restore your normal 2FA wallet in Electrum ok? If it does, then you should be able to restore it in Electrum and select the "Disable" option. You should then be able to open the "disabled" wallet file in ElectronCash and get access to your BCH.
I've tested this.. it works
|
|
|
|
Like I said, blockchain.info does stupid things when you export private keys. Each private key can be represented by an uncompressed WIF (Wallet Import Format) key and a compressed WIF key. The uncompressed WIF will convert to an uncompressed address, and the compressed WIF will convert to the compressed address. Blockchain.info shows you the compressed address (ie. 1Acq) in your wallet... But for some dumb reason (b.info Devs are idiots?) They give you the uncompressed WIF when you export. The result being that if you import this uncompressed WIF, it converts to the uncompressed address (ie. 1GXe)... If you goto https://www.bitaddress.org/ (create an offline copy, by saving the page and and running it without internet connection) Goto the "wallet details" tab... Put your private key WIF that you exported from Blockchain.info into the box and click "view details" You should see both the 1AcQ and 1GXe addresses shown with their matching private key WIFs. Copy the WIF underneath the 1AcQ address and import that into Electrum. (Note: WIFs start with a "5", "K" or "L") |
|
|
|
|
So if you restore using your seed and making it 2FA, it has BCH, but if you restore and disable 2FA it doesn't? That doesn't seem right
|
|
|
|
|
As I said... Each address in your 2FA wallet is actually created from a combination of 3 private keys... You need 2 of those 3 keys to spend.
TrustedCoin has 1. Your seed controls the other 2. The 2FA wallet only contains 1 unless you restore from seed and disable the 2FA functionality.
You either need your 2FA seed or the GAuth token for TrustedCoin... Unless you have one of those things, your coins are locked in that wallet.
|
|
|
|
The seed is the starting point... The whole point is that it will recreate the same wallet every time you restore with the same addresses and same transactions etc. I don't understand what you mean by "wallet on your PC (2FA) has BCC"... What other wallet have you generated that has 0 BCC? |
|
|
|
If your transactions are not showing up, then you filled in the wrong seed phrase. Check the addresses in the address tab (you may need to use "view -> show addresses") if the addresses are different there from your old wallet, then you've definitely got the wrong seed. Was this originally a seed from another wallet? Did you extend the seed with extra words? Have you got another wallet file that this seed actually belongs to and the wallet you lost had a completely different seed? I've seen a couple of users who have got confused when they have multiple wallets created in Electrum. This is why it's a good idea to make sure you can restore a wallet using the seed BEFORE you need to and find you've written it down wrong or are restoring the wrong wallet...  |
|
|
|
A 2FA Electrum wallet is just a fancy MultiSig 2of3 wallet. The only way to get the coins out is by having the 2 of the 3 private keys required to be able to sign a transaction to move the coins... 1 set of private keys is owned/controlled by TrustedCoin, but they'll only sign it if you have the GAuth token... Which apparently you've lost. The other 2 sets of private keys are generated from your seed... By default, it only stores 1 set of private keys in your wallet (and you send to TrustedCoin to use their set to countersign) When you restore from seed, you get the option to "disable" 2FA which restores both sets of private keys into your wallet, so then you don't need to send to TrustedCoin. The only way to recover a 2FA wallet is with the seed... So if you have no seed and/or no GAuth then your coins are effectively locked in. |
|
|
|
You'll need to move or delete the wallet file that it is attempting to open, and that will then force it into the "wallet creation" wizard... Which will let you restore from your seed On Windows 10, your wallet file will be in: C:\Users\YOURUSERNAME\AppData\Roaming\Electrum\wallets If you can't see "AppData" you'll need to " show hidden files and folders" |
|
|
|
|
Blockchain.info likes to export compressed private keys but is actually using uncompressed keys/addresses (or the other way round, I can never remember)
Anyway, what you need to do is create an offline copy of bitaddress.org, put the exported private key into the wallet details tab and click "view details".…
You'll see both the compressed and uncompressed addresses and matching WIF format private keys... Get the WIF that is on the same side as the 1AcQ address and import that to Electrum. It should then show as 1AcQ in Electrum as well.
I'm confused as to how your BCH moved from 1AcQ to 1MFP??!? Did you transfer BCH using a different wallet already?
|
|
|
|
|
Currently, It's all about size, which is mostly related to number of inputs and, to a lesser extent, number of outputs...
Inputs are generally around 148 bytes each (for compressed addresses, 180 for older uncompressed ones)... Whereas outputs are 34 bytes each...
Fees are generally calculated on a sats/byte basis, as block size is limited so the space in a block is the "in demand" item that is the basis for the supply/demand system that causes fees to go up and down...
When we don't have many transactions, you can pay less... When tens (hundreds?) Of thousands of transactions, fees go up as more and more people are competing for the limited block size...
It isn't more difficult to mine a larger transaction... It just takes up more room, so if the fee is low... It is reducing the space for higher fee transactions which means the miner gets less income...
A lot of this may change now that SegWit has activated... New address types, the possibility of larger blocks and offchain transactions etc... Interesting times ahead!
|
|
|
|
Ok... so I think I've found a way to work around the "Please wait" issue  Short Version: Use Electrum to create your "disabled" 2FA wallet, then open that wallet in ElectronCash
Long Version (with pictures): Requirements:-Electron Cash v2.9.3 that can be downloaded here: http://electroncash.org/-Electrum v2.9.3 that can be downloaded here: https://electrum.org/#download-Your TrustedCoin 2FA wallet 12 word recovery seed. If you don't have this, you cannot recover the funds under any circumstances1. Open Electrum. Do NOT open ElectronCash just yet. 2. "File" -> "New\Restore", Type a wallet name. I'd suggest using something easy to remember. Click "Next":  3. Select the second option "Wallet with two-factor authentication" and click "Next":  4. You will see the TrustedCoin disclaimer. Click Next. 5. Select the second option: "I already have a seed" and click Next:  6. Type your 12 word recovery seed (you should see a message appear next to the "Options" button that says "Seed Type: 2FA"). Click Next 7. Select the second option: "Disable" (This is VERY important) and click Next:  9. You will then be prompted to create a password for the wallet. This is optional, but recommended. After a few seconds, Electrum will recover your wallet using your seed and then you'll see this window:  10. Click "File" again and then click "Save copy". Now in the next window, it will give you the option of saving a backup of the wallet. Pick an easy to find location like the Desktop as you will need to find this wallet again soon. Also, use an easy to remember name and click "Save". You will see a message box confirming the location where you saved the wallet backup. Click "OK" and then close Electrum. 11. Now, open up ElectronCash12. "File" -> "Open". Look for the wallet backup file you just saved in step #10. (Note: If you used a password for the wallet at step #9, you will be prompted to enter the password.) 13. You should now have your "disabled" 2FA wallet open in ElectronCash, ready for spending your BCH 
Credits: Method suggested by DarkLord_GMS in this post on the ElectronCash GitHub issues list. |
|
|
|
It would be circumvented by getting malware onto the mobile device (which is the most likely attack vector)... which can then read the data off the storage and send it out. This would of course require that the user was tricked into installing the malware and giving it the correct permissions, and/or that the malware was exploiting some unknown or unpatched vulnerability in the mobile OS that allowed it to use the network. Given the news about the massive mobile botnet that got set up recently... getting a user to install malware is probably the easiest route |
|
|
|
Your value being used as the input is: "output_value": 110000000 => 1.1000000 BTC You are attempting to send "1" (tx.addOutput(b_address, 1))... with no change address/output specified... which means the remainder is used for fees: "fees": 109999999 => 1.09999999 BTC as a fee!!?!  It would appear that you have not realised that the output value is in satoshis... not BTC... so you're trying to send 1 satoshi, not 1 BTC... If you want to send 1 BTC as a test... use: tx.addOutput(b_address, 100000000) even then, you'll end up using a fee of 0.1 BTC (1.1 - 1 = 0.1)... which is still quite high You should probably include a change address/output! {
"addresses": [
"mob5JF2RPXHKGhgQx7hha2yw65aTM1jF79",
"muBfaVAj6JNzouYznzrXAErtFdezErui3V"
],
"block_height": -1,
"block_index": -1,
"confirmations": 0,
"double_spend": false,
"fees": 109999999,
"hash": "d80630f985542f7d1714340ce382e6e78d4f09d8a7f030e2334b09cfbe498048",
"inputs": [
{
"addresses": [
"mob5JF2RPXHKGhgQx7hha2yw65aTM1jF79"
],
"age": 0,
"output_index": 0,
"output_value": 110000000,
"prev_hash": "2d4b63d602f2c10394f1ea3ab294bfea54eb8c97e729156bbd568ddd6c2a4f06",
"script": "473044022078626375cd3c69d9044e650954f42c60c31f2b173026e031c9baa5b16173e8a102201 b49b7dda678ed9b6f6ff3f4e34ea64a8f7e3852eb5dfd373baae51df8658938012103887c5a740b 7ac673791553c0fa9ccd4f30d01745c6c8c8547419d1ce0d15af36",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967295
}
],
"outputs": [
{
"addresses": [
"muBfaVAj6JNzouYznzrXAErtFdezErui3V"
],
"script": "76a91495ebe73faf808abafd5775717f99da37f14b4c2388ac",
"script_type": "pay-to-pubkey-hash",
"value": 1
}
],
"preference": "high",
"received": "2017-08-31T02:03:36.386103156Z",
"relayed_by": "54.81.129.30",
"size": 191,
"total": 1,
"ver": 1,
"vin_sz": 1,
"vout_sz": 1
} |
|
|
|
But based off that transaction I am still unsure about the satoshi per byte I thought the one I just sent was more than 10 satoshi per byte could you explain how many satoshi per byte was in that transaction? I do see now on blockchain the transaction was 1.66 per byte. but still lost
You've created a transaction that has only ~1 sat/byte fee... it could take a while for that to be picked up. However, the mempool is relatively empty at the moment (less than 10K transactions) so you might get lucky The transaction has been marked as RBF... so if it gets stuck for a lengthy period, you might want to consider bumping the fee up to 10 sats/byte (0.0001 BTC/kB in Electrum)... then you can try and use the ViaBTC TX AcceleratorElectrum uses BTC/kB as opposed to sats/byte... in Bitcoin world a kB = 1000 bytes... so: 10 sats/byte = 0.00010000 BTC/kB If you REALLY want to avoid such issues in the future... you're better off trying to consolidate the payments BEFORE you receive them... ie. use a service that lets you specify a minimum payment threshold and set that to like 0.001 or higher... 0.005 would be OK, 0.01 would be better |
|
|
|
|
How old is the wallet.dat? Was it from a recent version of Bitcoin Core or an older version? If it is from a new version... you may find that pywallet doesn't handle it very well... it would appear that the devs added a number of new data fields into wallet.dat and pywallet will likely complain loudly about unknown records.
|
|
|
|
|
Show Posts
