Hi!

Do you have any plans to update the bitcoin price? It's been showing $507 for months.

Is Fastcoin still running, because I can't find any peers.

I just installed the fastcoin client and it's not able to find any peers. Do you have a list of peers I could try?

This is for people who have dozens of bitcoin addresses in different places.

This is a bug in the development version 1.9. It may, or may not be, a problem with the current release version.

Here's a private key that I'll no longer use:

5JN4PgPLhRskjUDhytEJ8tTDsUKJ9bBuEWwhdCSGFGhXbx6ofPt

In every other wallet, it will generate this public key hash:

1BbJHQStkpMcoqJ3ysZRV6HNpe3bGooiUK

In Electrum, it generates this public key hash:

1P2knF5HfFyYcdCrqxd2Ur3Z1UeGTv2dXx

This is not an isolated case. I saw this yesterday with another private key, but I want to keep that private key and do not want to disclose it. I did, however, test a specific case:

1) I ran 'importprivkey('<my key>')' from the command line of the Electrum Wallet.
2) I noticed that the public key hash was incorrect.
3) I sent funds to the incorrect public key.
4) I then tried to use the public key in the Electrum wallet by setting it to 'Prioritize', and then using it to send funds. The transaction failed completely with an error. I am not sure, but I believe the error was 'None Type', or something similar.

See:

http://electrum.org/community.html

It's just change that gets mopped up. When you put bitcoins up for sale on an exchange, or when you want to buy them, there is not a 100% match between what is being sold and what is being purchased. So if I am selling 110.09 bitcoins, and someone puts in an order to buy 110 bitcoins, then .09 bitcoins is leftover for the next purchase. That's all that's going on.

With me, a transaction was somehow missed in the history, when I sent a payment from an imported address. It may be the same problem. If so, then yes, it would be a bug in Electrum. However, I don't exactly know what the poster's problem is, so I can't say for sure.

This may have been fixed yesterday. I started using the development version, 1.9, yesterday, and the transaction goes through now. It was easily reproducible with a simple spend from one imported address to another address in the main list, with old money. However, it doesn't show up in the development version 1.9.

I came across a problem yesterday, with imported addresses, and I think it's the same problem you're seeing. I brought it to the attention of the devs and they produced a development version of the software which I think will fix this problem. However, it hasn't been released yet, but will be in version 1.9.

My problem was with an imported address which was used in a transaction. The transaction did not get recorded. To fix it, I had to erase my wallet, and then recreate it. Of course, this removed the imported addresses from the wallet, but when I reloaded them, they were correct.

Maybe you can try this, if you're interested, or wait until version 1.9 is released.

I don't know what could be wrong at this point.

However, if you use the Classic GUI and set the mode to 'Expert Mode' in the Preferences, then you can see the actual balance in each bitcoin address in your system by then selecting the 'Receive' tab on the main screen. You can compare these balances by using either btcbalance.net, or by checking each address using blockchain.info by adding the address to the end of this URL, like this:

http://blockchain.info/address/1GcKb752rgkeYC2w72dgpoCUQBpEmHAkYZ

Otherwise, there's no way to figure out the problem just by looking at wallet ledger entries.

Which server are you connecting to? And have you tried connecting with other servers?

To connect with a server, switch to the Classic GUI and click on the Green Dot at the lower right corner of the window.

Actually, if you want to see individual address balances, then you not only have to use the Classic GUI, but you also have to put the program into 'Expert Mode' by Selecting 'Preferences' from the File Menu. Then checking the 'Expert Mode' checkbox on the Display Tab. Then you can close the Preferences box and select the Receive Tab, where you will see the individual balances on each address.

Here's another thing you can try. If I were to guess, I would think that the server you're connecting to is probably not giving you the correct information.

Go to Classic GUI by selecting it from the 'View' menu, if you're using the Lite GUI.

Then in the lower right corner of the screen in the Classic GUI, you should see a green dot. Press the green dot. This will bring up a list of servers to connect to. Try connecting to different servers and see if they show you the same total balance.

A wallet is composed of multiple individual addresses. The addresses are the items that actually hold the bitcoins. It's difficult to figure out if a total balance is correct when looking at the whole wallet. We need to check the balance in each address.

In electrum, bring up the Classic GUI, (if you're using the Lite GUI), by going to the View Menu and selecting Classic GUI.

Then go to the 'Receive' tab. On the 'Receive' tab, you should see a balance associated with each individual address. This should be the actual balance in each of those addresses. You can double check them by going to 'www.btcbalance.net', and entering the addresses into that web page, which will also show you the balances in each address. If the two balances match, the one in electrum, and the one in www.btcbalance.net, then you can be confident that the balance in that address is correct. If you find an address in Electrum which has a different amount of bitcoins in it than in www.btcbalance.net, then it's probably Electrum's fault.

Let us know.

I don't know pywallet, but here's another way to do it.

1) In bitcoin-qt, go to Help/Debug Window.

2) Choose the Console Tab.

3) In the text box, enter 'listaddressgroupings'.

This will bring up a list of 100 addresses. Your money could be in several addresses, but probably only in two or three. Look through the list. wherever you see some bitcoins, dump the private key of that address using, 'dumpprivkey <bitcoinaddress>'.

4) Import all of these private keys into Electrum, resync with an Electrum server, and your balances should match.

Change Addresses are a pain. One of the things that I like about Electrum, is that you don't have to use them. Most wallets, however, create NEW addresses EVERY TIME you make a spend, and some of your bitcoins go into hidden 'change' addresses.

The best way to move money into a new wallet is to send the funds. Don't try to import the keys unless you know what you're doing.

If you want to check the actual balances on your individual addresses to determine the actual balance of the imported keys, then go to this webpage and enter your public keys of the addresses that you want to check.

www.btcbalance.net

One of the reasons I really like Electrum is that it has really good address control. I can import addresses, export addresses, turn off change addresses, and by prioritizing an address, I can send from that address alone, to another address.

The bug is this:

1) Import a private key for a foreign address.

2) Prioritize that address when sending, but leave all other addresses unprioritized.

3) Initiate a payment. When doing so, an error is returned. The error in the server log is this:

error: {u'message': u'TX rejected', u'code': -22} [u'<Big Raw Transaction Number>']

I've tested this when sending the transaction through my new Electrum server and other Electrum Servers.

Thank you! I think that solved it. I changed from 'host=localhost' to 'host=0.0.0.0', and I commented out the 'password=secret'. This isn't the bitcoind section, so I don't think it's the bitcoin password. I DO have the bitcoin password set in the bitcoind section.

Anyway, now I can connect REMOTELY using TCP, SSL, HTTP, and HTTPS.

Cool... If this works, I'll be running another public electrum server soon. Electrum is really the ONLY wallet that doesn't suck in some way.
[I hope Thomas doesn't take offense to this. This is my highest compliment.]

I'm starting it and stopping it with the 'start' and 'stop' scripts in ~/src/electrum/server, and seems to run fine and connect when I run a local electrum client. It brings up the transactions and the balances just fine.

What are these two parameters from the electrum.conf server file?

host=localhost (?? Is this correct? Since this is the Electrum server, then isn't this correct?)

password=secret ( This bugs me a lot. Do I just make something up for the password, or is this supposed to somehow be used?)

From 'electrum.conf' file:

[server]
host = localhost
#report_host =                                                                                                                                 
native_port=50000
stratum_tcp_port = 50001
stratum_http_port = 8081
stratum_tcp_ssl_port = 50002                                                                                                                   
stratum_http_ssl_port = 8082                                                                                                                   
#report_stratum_tcp_port = 50001                                                                                                               
#report_stratum_http_port = 80                                                                                                                 
#report_stratum_tcp_ssl_port = 50002                                                                                                           
#report_stratum_http_ssl_port = 443                                                                                                             
password = secret