Getting closer! At least it is running and attempting to output data

The issue seems to be that PyWallet is not able to create an output file, so that it can begin to output any found keys etc. I suspect this is either a "permissions" issue (the script does not have write permission to that folder)... or that the folder "C:\Users\Catherine\Downloads\Pywallet" doesn't exist.

You need to make sure that folder exists... or you will need to change the "--recov_outputdir" value of the command you entered to a folder that does exist.

It looks like your pywallet.py file is in "C:\Users\Catherine\Downloads"... so either:

- Create a folder called "Pywallet" in the "Downloads" folder and run Pywallet again with exactly the same command that you used previously.
OR
- Run PyWallet again but set the  --recov_outputdir to C:\Users\Catherine\Downloads

You guys are NOT reading the OP correctly... it isn't anything to do with "change"... he is wanting to know why his transaction which sent ~0.01 BTC (and had 0.058 change) is showing as -0.08


So the math doesn't add up properly:
0.01048515 sent + 0.05854722 change + 0.00030263 fee = 0.069335 TOTAL... but the wallet shows -0.08012278... In any case, it should ONLY be showing 0.01048515 sent + 0.00030263 fee = -0.01078778

Interestingly, if we take 0.069335 and ADD another 0.01048515 (sent amount) + 0.00030263 (fee amount)... we get the 0.08012278 BTC showing as being deducted! So, it seems that Electrum has calculated something screwy and is showing as (2x sent amount + 2x fee + 1x change amount) has been deducted from the wallet??!?

Like I said... I'd recommend the OP restore a new copy of the wallet from seed and see if it fixes it...

Pretty much... you'd need to the same for Electrum words as well


Yes... if you moved the coins to addresses generated by Electrum wallet, they are then backed up with new words.


The whole point of the seed mnemonics... aka "word phrases"... is that you can simply write those down, and store them safely and securely OFFLINE. You entire wallet and ALL of it's addresses (old and new) and transaction history can be restored by using those words.

It completely eliminates the need for digital backups of HDD's and/or wallet files... and even allows you to recover from lost wallet passwords (NOT lost BIP39 passphrases tho)... as when you restore from seed you can simply choose a new password

But, there is no reason you can't do HDD and/or wallet file backups if you want... it just isn't strictly necessary.

You've got yourself a little confused here... You seem to be confusing "legacy" and "segwit" transactions with uncompressed/compressed addresses

In "legacy" transactions... the input size is either ~180 bytes OR it is ~148 bytes depending on if you are using uncompressed or compressed addresses respectively... It is technically possible to use both compressed address and uncompressed address inputs in the same transaction, which gives us the following:

A standard (legacy) transaction using uncompressed address inputs only has the following size:
(count of inputs * 180) + (count of output * 34) + 10 (+/- 2 bytes per input)

A standard (legacy) transaction using compressed address inputs only has the following size:
(count of inputs * 148) + (count of output * 34) + 10 (+/- 2 bytes per input)

No... I didn't... you'll notice I said to sweep the BTC and then sweep the other coins... once you sweep, the BTC is gone from that private key. That is why sweeping is recommended over importing.


I never said it would... It won't "capture" BCH either... Which is why I said:

Man... that is some weird stuff there... not sure why it thinks 0.08 was taken when:

1. The transaction only has a TOTAL input of 0.069335 BTC
2. 0.05854722 BTC went into a change address

Must be some weird little Electrum glitch. Have you tried closing and re-opening Electrum?

What happens if you restore a new wallet with the same seed?

Plaintext just means that your wallet file is not encrypted. However, an Electrum wallet can have THREE states:

1. Unencrypted file, unencrypted data - EVERYTHING is in plain text (including private keys/seed)
2. Unencrypted file, private keys/seed encrypted - File is in plain text, but important data like private keys/seed is encrypted using wallet password
3. Encrypted file, encrypted data - Entire file AND important data contained with in are both encrypted using wallet password.


If you have a wallet password set, then the private keys (and seed) WILL be encrypted... the file itself is only encrypted if you tick the "encrypt file" box when setting a password.


Yes, if you have 12 words, you have an "HD" wallet... these are designed to generate an "infinite" number of private keys from the seed that is able to be restored from your 12 words... The same 12 words will always generate the same list of private keys.

It is technically seeded... just not with a native Electrum seed. It is using a "generic" BIP39 seed... and the seed mnemonic (the "12 words") are not stored in the wallet... so there is no way to export them if you lose your current copy of the words!

To answer you question, Yes, of course you can send the Bitcoins from your current imported wallet a new "seeded" Electrum wallet. This will require that you send an on chain transaction which will of course require a transaction fee.

It doesn't matter what wallet you use... you have a ton of tiny "dust" inputs... your transaction "data" size is going to be large... fees are in sats PER BYTE or btc PER KILOBYTE.

So, the larger the transaction, the higher the total fee.

You options are:

1. Stop receiving tiny amounts, so when you try to transfer, you don't need a large number of inputs, which makes the transaction data size smaller... which makes the total fee smaller.

2. Export your Exodus seed and import into a wallet that allows you to specify the fee you want and send all your dust with a lower fee rate... transaction is likely to get stuck if you send with a low rate.

3. Continue getting tiny dust payments and pay large fees to move your bitcoins around.



For the record, you CAN import your Exodus seed into Electrum (select BIP39 from the "options"... and leave the derivation path at default of m/44'/0'/0')

Should be fairly easy I would think.

1. Open ElectronCash
2. File -> New\Restore -> MultiSig Wallet
3. Set "From 3 cosigners", "requires 2 signatures"
4. "Use public or private keys"
5. Paste in the "X1" xprv from your disabled 2FA wallet
6. When prompted for co-signer 2, "Enter Co-signer key"
7. Paste in the "X2" xprv from your disabled 2FA wallet
8. When prompted for co-singer 3, "Enter Co-singer key"
9. Paste in the "X3" xpub from your disabled 2FA wallet.

This should theoretically recreate the 2-of-3 MultiSig that is identical to your Electrum disabled 2FA wallet. You should be able to see the same addresses generated, your pre-fork history and BCH coins. And because it contains 2 of the 3 private keys... should allow you to sign and broadcast transactions.

For reference: https://www.youtube.com/watch?v=umsIy1ks8vg

The video is using LTC and BTC, but should theoretically work the same...

And some of us work 12 hour shifts... So some patience would be appreciated.

Which folder did the search say pywallet.py was in?

Don't worry so much about the number of transactions... But the fees they pay.

If you look at  https://btc.com/stats/unconfirmed-tx

You'll see that the vast majority... Like 99% of them are under 40 sats/byte... This isn't always the case, but is generally true.

If there are 100,000 unconfirmed transactions and the majority are all really low... You'll get a transaction through pretty easily with a fee around 100 sats/byte... However if there are only 5000 transactions but all paying 300 says/byte... You're going to have to pay more than that if you want next block confirmation.

It's the way the forks work... BCH forked on 1 August... So any BTC you had on a private key at that time means you get BCH on that private key (regardless on what you do with the BTC after 1 august)... It's a completely separate blockchain... So BCH and BTC transactions do not affect each other, they operate independently.

Go here and type in one of your old BTC addresses (NOT a private key!!): https://blockdozer.com

You'll see that you also have BCH. You can use a BCH (aka Bitcoin Cash) wallet to get access to these coins... I'd recommend using ElectronCash (https://electroncash.org/) and importing all your old private keys now that the BTC has been moved off the private keys.

But check the wallets here: https://www.bitcoincash.org/#wallets

It's definitely worth investigating... BCH is currently worth around 0.14 BTC... And relatively easy to send to an exchange to "dump"... Basically an instant 14% payout on the amount of BTC you had.


BTG aka Bitcoin Gold isn't worth quite as much... But their fork was around Oct 24th.. again independent of both BTC and BCH... And more #freeeMoney

Bitcoin Gold here: https://bitcoingold.org

There is no such thing as Electrum Bitcoin CASH.

There is "Electrum"... which is a Bitcoin wallet... Download here: https://electrum.org/#download
There is "ElectronCash"... which is a Bitcoin Cash wallet... Download here: https://electroncash.org/#download

Note that they are developed by different people. Which one did you download? and where did you download it from?

That is kind of the whole point of forks... different blockchains... and replay protection.

After the fork (with replay protection implemented, of course)... Transactions on one chain, are not valid on the other chain. So, there was no history on the BCH chain AFTER the fork block, unless you have specifically made a BCH transaction.

Without replay protection, it could potentially be a different story if someone was replaying transactions on both chains...

Suggest you might like to read this entry regarding "change": https://en.bitcoin.it/wiki/Change

and also this one, it explains why change happens... and why you can't just send "exact" amounts of BTC in a transaction: https://en.bitcoin.it/wiki/Coin_analogy

No... you don't pay a fee for every "re-allocation"... you pay a fee "per transacion". Because you're sending the transaction anyway, the overhead for including the "change" output is only 34 bytes... which doesn't really alter the transaction fee by that much in the grand scheme of things.

Worst case is moving from a 192 byte transaction (1 input + 1 output) to a 226 byte (1 input + 2 output) transaction... that would increase the fee by around 18%... but if you have any more inputs or outputs, and that percentage drops pretty quickly.

If a "chain split" has been detected... it is possible that the server in question is using a s2x (or other fork code) node or something? I'm fairly sure if it is just lagging, it should explicitly tell you this... 

What apps do you have installed? I can usually have 5 Apps installed... Currently (because I've been mucking around testing stuff) I have Bitcoin, Dash, Dogecoin, Ethereum and Litecoin... I did have Bitcoin, Bitcoin Cash, Bitcoin Gold, Dogecoin and Litecoin installed...

Also, it really isn't THAT much of a bother to fire up the manager, uninstall an app and install the app you are missing... unless you are trying to use more than 5 currencies at once, multiple times a day

That's how time work...

...
10am
11am
12pm
1pm
2pm
...

I don't see what the issue is? Did the "01" confuse you into thinking it meant 0100 hrs or 1am?  the PM at end indicates that it is 1pm or 1300hrs...

If you want to change it... goto "Profile" -> "Look and Layout Preferences"... and change the "Time Format"

ViaBTC won't accept it because the fee is below 10 sats/byte... and you transaction is over 400 bytes, so ConfirmTX.com want $4 to accelerate it.

So, I've gone ahead and pushed this for you via AntPool... hopefully they will mine a block shortly and it'll get included