Bitcoin Forum

Bitcoin => Bitcoin Discussion => Topic started by: Kermee on September 06, 2011, 11:25:15 AM



Title: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: Kermee on September 06, 2011, 11:25:15 AM
Granted, I'll be the first to admit that I'm not the sharpest tool in the shed, but could someone explain to me why within our 2016 block range between difficulty retargets, we have some blocks at 1777774 and some at 1779164?

This is the first time I've seen a difficulty change/difference during a 2016 block range.

Did I miss something?

Cheers,
Kermee

EDIT: bitcoind still shows 1777774.48200146, and all the latest blocks solved still shows 1777774.48200146... But http://blockexplorer.com/q/getdifficulty ...  ???


Title: Re: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: Furyan on September 06, 2011, 12:16:12 PM
All my bitcoin instances report 1777774.48200146 so I'm going to go with, blockexplorer has a bug.

Interestingly, some of the pools are displaying the 1779163 number, thus revealing that they're obtaining the number from blockexplorer.  We obtain it directly from bitcoin.


Title: Re: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: kjj on September 06, 2011, 08:34:22 PM
There was a bug in the difficulty display in some previous versions.  The actual difficulty was always right, but it was reported incorrectly.  This has been fixed in recent versions.  Update your nodes, and if you mine for a pool showing 1779163, pester the pool operator to update his.


Title: Re: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: ampirebus on September 07, 2011, 12:20:48 AM
Estimated   1741808 in 871 blks


Title: Re: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: Kermee on September 07, 2011, 01:34:38 AM
Ah.

http://blockexplorer.com/q/getdifficulty

Looks like it's fixed now =)

But yes... It does show how many sites, pools, etc. are getting their #'s from there vs. directly from bitcoind.

Cheers,
Kermee


Title: Re: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: payb.tc on September 07, 2011, 01:43:51 AM
simple explanation:

0.3.20.2 calculates less accurately => 1779163.94366
0.3.24 calculates more accurately => 1777774.482

they must have been grabbing the difficulty factor from an older install temporarily.

edit: sorry i just noticed kjj said basically the same thing above.


Title: Re: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: Kermee on September 07, 2011, 01:52:04 AM
There was a bug in the difficulty display in some previous versions.  The actual difficulty was always right, but it was reported incorrectly.  This has been fixed in recent versions.  Update your nodes, and if you mine for a pool showing 1779163, pester the pool operator to update his.

simple explanation:

0.3.20.2 calculates less accurately => 1779163.94366
0.3.24 calculates more accurately => 1777774.482

they must have been grabbing the difficulty factor from an older install temporarily.

edit: sorry i just noticed kjj said basically the same thing above.

Awesome. Thanks you two for the explanation!

Cheers,
Kermee


Title: Re: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: theymos on September 07, 2011, 03:08:38 AM
Sorry about that. I fixed it.

There are two instances of BBE: one is run by me and one is run by MtGox Live. Usually you get MtGox Live's version, but they were running slowly yesterday and my monitoring system automatically switched to my version. My version is running an old version of Bitcoin, which caused that discrepancy. I updated that part of my Bitcoin code to use the new calculation.


Title: Re: Difficulty from 1777774.48200146 to 1779163.943662?
Post by: Furyan on September 07, 2011, 01:04:51 PM
Sorry about that. I fixed it.

There are two instances of BBE: one is run by me and one is run by MtGox Live. Usually you get MtGox Live's version, but they were running slowly yesterday and my monitoring system automatically switched to my version. My version is running an old version of Bitcoin, which caused that discrepancy. I updated that part of my Bitcoin code to use the new calculation.

Thanks theymos!