[Ethereum] All the mined coins are going to address 0x000000

mining

I have an ethereum miner up and going for about 24 hours now. For the first 15 hours or so I saw the following text repeated on the screen (each time updating only the timestamp).

23:17:27.282|gpuminer0 workloop 1 #6f9a4b23... #6f9a4b23...
23:17:27.342|gpuminer1 workloop 1 #6f9a4b23... #6f9a4b23...
23:17:27.763|gpuminer2 workloop 1 #6f9a4b23... #6f9a4b23...
23:17:28.120|gpuminer3 workloop 1 #6f9a4b23... #6f9a4b23...

However I woke up this morning (so about 15 hours passed total) and the output changed such that only the hash changed to something like this

21:52:56.111|gpuminer0 workloop 1 #5e57d24f.. #5e57d24f...
21:52:56.156|gpuminer1 workloop 1 #5e57d24f.. #5e57d24f...
21:52:56.212|gpuminer2 workloop 1 #5e57d24f.. #5e57d24f...
21:52:56.678|gpuminer3 workloop 1 #5e57d24f.. #5e57d24f...

I had assumed this meant I mined a block while I slept. However when I went to my account it didn't have any additional ether in it and i could find no signs of any mined blocks on my account. Sadly my scroll buffer is too shallow to scroll back and actually see if I mined a block.

So any ideas? Does the hash update on the output even when you don't mine a block? Or did I mine a block and somehow it didn't make it into my account and got lost due to bad configuration or something?

EDIT

So I finally saw the notification that I did in fact successfully mine a block. The block I mined can be seen here: https://www.etherchain.org/block/960905

What is confusing is apparently the block mined went to miner 0x0000* instead of to my own account. What is even weirder is that I am running the miner as follows:

geth --rpc --rpccorsdomain localhost --etherbase '0xblahblahblah'&
ethmine -G

and when I go into geth to confirm the coinbase address it is set correctly to my own address. I check using:

eth.coinbase

So why is it still using the 0x0000 miner?

Best Answer

Ok so I found the solution. In the official tutorial it tells you to include the ethereum-dev repository in Ubuntu to get everything installed. This caused me to install from GIT which apparently had this bug in it (which might be related to the recent transaction bug where all transactions were being sent to 0x00000). The version reported off the current install was 1.4.0-unstable. I had since downgraded back to a stable 1.3.3 and mining appears to be successfully working again.

Related Topic