Hmm... for me, all I need to do is set the variable to 0 and it lets me choose any fee...

did you try using 1.9.8?

If by ages you mean 100 blocks x 10 minutes = 1000 minutes = 16.66 hours, then yes... it takes 16 hours 40 minutes. (on average)

The coinbase aging requirement has always been there, if you don't like it you can join a different pool, but in the end they just end up paying you funds like 2 days later anyways, so waiting for 100 confirms is faster.

You can also create your own version of bitcoin if you want. One that doesn't have the coinbase aging requirement... but removing the coinbase aging requirement can cause some gnasty problems imo.

The servers are run by volunteers using open source software. Depending on the person, they may pose limits such as, we will not search for spent transactions before a specific block etc. also, depending on what kind of system they run on there could be a plethora of problems causing synching errors.

The green light just says "you are connected to Bob's server" but it's up to Bob to ensure the server is running properly.

If you see wonky behavior with synching etc. try picking another server. The port settings are fine as default.

Open your wallet file and find the 'seed' object and 'imported_keys' object if you have any.

Copy them all separately into a new txt file for easy access (separate with line breaks for ease of understanding)

Start up a python console

Use base64.b64decode() on each value you copied from your wallet, then copy those outputs somewhere.

Use python's built in Hash() function (NOT hashlib) on your wallet password and copy the hash that is created by your password.

Download aes, or pull the folder from the electrum installation.

Use the decryptData() function with the first arg being the hash of your password, and the second arg being the b64decoded value for one of the things u want to decrypt.

The output will be your unencrypted seed or imported private key.

Try the "Portable Version" on the Download page. All files will be stored in the same folder as the executable. You can place everything on a USB etc.

Anyone who tells you something is 100% safe is lying.

You might be 99% safe, 93% safe or 60% safe, no one knows... but I would garner a guess that safekeys would keep you MORE safe than you are NOT using it.

The most important thing is to scan your system regularly with malware bytes and run something like Microsoft Security Essentials... Also, Disable Javascript in your browser, and whenever you come to a legit site (like youtube etc) you can click "add to exceptions" and it will let you view that page with javascript. If a sketchy site requires javascript. Do NOT activate it.


I recommend safe paper wallets made offline if you're not too good with computers.

You're welcome, I originally wrote that in Japanese for my friends here in Japan, and I translated into English so I'm sorry if it's hard to understand.

If you have any questions about the process feel free to ask.

Let me say this: Electrum is a free piece of software that is open source. You should only trust it as much as you trust a collective group of people on the internet (everyone using Electrum and vouching for it), OR your ability to understand python code.

I personally trust my ability to read/code in python, so I don't need to trust Thomas or anyone telling me "this is a good program." I can verify this by myself.


As for this incident. I hate to say it, but your computer was compromised, and currently there is no piece of software for wallet that can protect you from a computer with a trojan.

If you deleted all the files from the report, I would say "maybe" you're safe. A good hacker could make a new form of trojan not traceable by malware detection, and then put in a second "dumb" trojan so that you will scan for it, find it, delete it, then continue on normal feeling safe... but you're not.

The best thing to do is ALWAYS ASSUME YOUR COMPUTER IS COMPROMISED.

If you want to keep your coins safe, buy a USB memory stick with over 8 GB and install Ubuntu on it, and boot your Electrum from there.

http://pastebin.com/YhUj6fzt

If you sent to the same wallet with the same seed, then the balance should only go down by the cost of your fee on your transaction.

Also, sometimes the server you're connected to doesn't update correctly and you need to manually select a server to connect to until you find one that updates your balance.

Electrum servers are run by volunteers running open source software, so sometimes you can get a dud...

Just go into network menu uncheck autoconnect and then pick some servers, wait a few seconds and see if the transactions show. Repeat.

Yea, it's the same process except instead of using the seed you have to do it once for each encrypted key and the output is one unencrypted private key each... Its time consuming.
'imported_keys' is where you want to look, and each encrypted private key is surrounded in single quotes separated by commas.

Then you can just re-import the private keys to your new wallet using the normal interface.

Edit:

I just verified with my electrum, I didn't have imported addresses, but I made three on Bitaddress and put them in just to see how it looks in a test wallet. The imported keys should look like this.


So the format is:


So you want to do the steps I explained above and then repeat Step #7 where the first value is the encrypted private key for the address of your choice and the 2nd value is the wallet password. (all imported keys and the seed are protected by the same password.)
(Note: after doing #5 and #6 once, as long as you don't close Electrum, you don't need to do them again)

When it says synched, it means addresses, transactions, amount of bitcoins, etc.

Labels, contacts, and other things not related to your wallet's addresses will not be synched.

To test the synching functionality, send some bitcoin from one address in your wallet to another wallet on your tablet etc.

Once the transaction has been broadcasted, load up electrum on another device with the same seed... it should show that transaction from your tablet on your other device as well.

NOTE* : The file I am talking about in step 1# is commonly something like "electrum.dat" or "default_wallet" would be the name of the file. It can usually be found in %APPDATA%/Roaming/Electrum/wallets/ if you're on Windows.

1. open the file using a text editor

2. look for an area (maybe use find function) that says
3. take the string of letters and numbers between the '  ' single quotations. and copy it somewhere readily available. (don't worry, those letters are encrypted, so you won't be too compromised)

4. open Electrum 1.9.8 and click on the console tab.

5. in the console type then hit Enter.

6. type in console then hit Enter

7. Let's say your encryped seed was abcdefg== and your password was d0gecoin
Then, type in
8. if the password is correct, the next line will give you a string of 32 HEX characters (0-9, A-F) between single quotes. THIS IS YOUR UNENCRYPTED SEED! BE CAREFUL WITH THIS INFORMATION, IT WILL RESTORE YOUR WALLET FOR ANYONE WHO SEES IT!

Note for 8: If the password is wrong, it will say "Exception Invalid Password"... pressing up arrow key will re-insert the last command so you won't have to re-type too much besides the password. Also, the console won't hide your password and you will be typing it in plaintext onto the console. Be sure to do this in private.

9. Now you have your HEX based seed. Click "New Wallet" in File menu, then choose second option "Restore from seed", then in the seed box paste your 32 characters HEX seed with NO QUOTATIONS. and hit next.

10. You have now restored your bitcoins.

1QCjHCCaifSFDMqR4KWDAfowZJiiqi7m7U

Here's a tip address if this helped.

Edit: btw if it was me, after doing all this stuff I might just make a NEW wallet and send all my bitcoins there and make a different password for the new wallet... your unencrypted seed was just all over your monitor and stuff, so it might be safer to make a new wallet.

This is because the first time you opened it, it created a wallet in your data-folder.

The data-folder is not deleted when Electrum is uninstalled, and because of this, it detects the wallet you created before (the one that was unsuccessful) and automatically loads it.

What are you trying to restore your wallet from? Are you restoring your wallet from seed? or are you trying to restore a wallet file?

Also, why must you use 1.9.1? I suggest 1.9.8, as it will restore your seed just fine and you'll get better support.

Yes, all transactions will be synched.

1. You shouldn't make any serious new wallets in a public place with security cameras.

2. If you have a virus capturing screens, you've probably got bigger things to worry about like someone taking out a $5M debt in your name.

3. Don't type your seed. Copy and Paste it from one window to the next. write it down on paper with a pen.

The safest way to use anything bitcoin related is to do it offline. The next safest thing is to keep your computer safe, don't run around screaming your BTC balance and don't do anything with a huge fat wallet in front of security cameras.

I can't think of any...

I would be interested to see what people come up with... but if you want advantages I could list some.

I am completely in for any beta testing.

I assume once it's presentable you will have the source be open, correct?

Also, I noticed that when clicking on a received transaction on the history screen, it said "From: <txid>" whereas the sent transaction when clicked says "To: <btc address>"

Two things I liked a LOT:

1. NFC!!!!!!!!!!!!!!!!! YESSSSSSSSSSSSSSSSSSSSS!!!!!!

2. The create wallet UI. (I like the color blue, so maybe that's why)

Things I wished for / wondered about:

1. Multi-sig? I wonder how that would look UI wise... (that's probably a whole can of worms... maybe later?)
2. Encrypt a short message and embed it into a URI with the public key used to encrypt. When sent to the holder of the pubkey via mail app or something, they click the URI, and if they have the privkey, input their pin and the message comes up, etc... (again, not a core functionality for a wallet... but I'd find it awesome. Another fantasy of mine.)


But aside from my wishful thinking, this looks amazing. Good job! Let us know if you need any testers. I have a few old Androids to test older versions of Android.

Try this:

Run Electrum through the Python command console

Recreate the error.

Read the traces (the last few lines of code before the error.)

Open the file in the trace before the error, find the line of code a few lines above where you hit the error.

Paste in the following code:


Recreate the error again, this time the python console will stop the program inbetween whatever lines you're in.

In the console, type in major variables that are being used in the function.

See if any of the variables are weird.

search for hours

give up

wait for someone to fix it...




wait, we were talking about what I do, right? lol :-P

Edit: This is how you step through the code using python debugger

http://docs.python.org/2/library/pdb.html#debugger-commands

Edit 2: It would be nice if we could get more information too. The error message you gave is the default transaction rejected error from the Bitcoin Network, and isn't something specific to Electrum.
The Bitcoin network is mad at you for something... like maybe trying to spend coins freshly mined etc.

To use the fee properly, you must

1. Have the fee set to 0.0001 BTC ( 0.1mBTC) in your preferences.

2. You must also type in 0.0001 BTC ( X number of kb for tx rounded up) for the "Fee" box on the send window. Keep trying til it lets you send, then that should be enough. a 1999 byte tx should be 0.0002 but a 2001 byte tx should be 0.0003, etc. People who receive a lot of transactions to their address will have a larger tx size because it will have to include a signatures for every single bitcoin your received in previous transactions. Miners and donation addresses are affected most.

If you have done both of these and send the transaction, you will be able to send for the 0.0001 Min Txfee. (0.9.0 adoption is still rather low at less than 30% or so, so dropping the min tx fee now to the new standard is not logical, it will cause delayed transaction times.


If you MUST send tx with 0 fees for some reason. Go in to the code and change the min tx fee constant from 0.0001 BTC to 0, or you could comment out the exception causing the error message.

Hey, it's a good opportunity to learn Python, people! :-)

DISCLAIMER: If you tinker with the program and lose all your coins, don't blame anyone but yourself. If you don't know what you're doing, hire someone who does, or post an issue on github.

To put it simply: "not much"

To be more specific: "not any more of a threat than a randomly generated 1 address would receive"


If someone were to set out with a goal of finding your seed (ie, not your Private Keys, but your seed, which would give them all your private keys)

They would need to know a large amount of your addresses, and know which type of address it was (Receive or Change) and which order it was. (whether it was the first or second or third etc.)
Then if they had a quantum computer on their side, they could then probably figure it out.

To be honest, if the crypto doesn't level up before quantum computing gets too accessible and programmers get too accustomed to programming for it, then They won't need your seed. They'll just run down the list of highest balance addresses and start hacking away.