BitShares Forum

Other => Graveyard => BitShares PTS => Topic started by: dav on November 06, 2013, 05:34:41 am

Title: Difficulty did not change after block 2016
Post by: dav on November 06, 2013, 05:34:41 am: It's still 0.00000095.

Something wrong?
Title: Re: Difficulty did not change after block 2016
Post by: 5chdn on November 06, 2013, 05:36:18 am: I thought the retarget is after 1.5 days?
Title: Re: Difficulty did not change after block 2016
Post by: bytemaster on November 06, 2013, 05:43:37 am: Quote from: qdoe on November 06, 2013, 05:36:18 am
I thought the retarget is after 1.5 days?

An oversight in tweaking the parameters left it set at Bitcoins default of 2 weeks... which means tomorrow it will correct.
Title: Re: Difficulty did not change after block 2016
Post by: bytemaster on November 06, 2013, 05:44:58 am: Given that 24 hours is far to quick to launch a patch we have opted to leave it be.
Title: Re: Difficulty did not change after block 2016
Post by: mitao on November 06, 2013, 07:44:45 am: A new client with different difficulty target adjusting time may cause the blockchain diverged.

Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: Difficulty did not change after block 2016
Post by: bytemaster on November 06, 2013, 07:46:11 am: Quote from: mitao on November 06, 2013, 07:44:45 am
A new client with different difficulty target adjusting time may cause the blockchain diverged.

Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)

This adjustment would be made with lots of time for people to update. We are not going to make rash updates. Right now the parameters are the same as bitcoin so it cannot be all that bad :)
Title: Re: Difficulty did not change after block 2016
Post by: rando on November 06, 2013, 06:51:54 pm: Quote from: bytemaster on November 06, 2013, 05:43:37 am
Quote from: qdoe on November 06, 2013, 05:36:18 am
I thought the retarget is after 1.5 days?

An oversight in tweaking the parameters left it set at Bitcoins default of 2 weeks... which means tomorrow it will correct.

is it currently set to 2 weeks or 2 days?
Title: Re: Difficulty did not change after block 2016
Post by: Lighthouse on November 06, 2013, 06:58:16 pm: Currently it's set to two weeks, but because of how much power is in the network, the 5 minute blocks are taking 30 seconds or less so 1 day = 1 week, adjustment should be in the next 18 hours.
Title: Re: Difficulty did not change after block 2016
Post by: bytemaster on November 06, 2013, 06:59:12 pm: Quote from: Lighthouse on November 06, 2013, 06:58:16 pm
Currently it's set to two weeks, but because of how much power is in the network, the 5 minute blocks are taking 30 seconds or less so 1 day = 1 week, adjustment should be in the next 18 hours.
Adjustment should be in the next 8 hours...
Title: Re: Difficulty did not change after block 2016
Post by: smith88 on November 07, 2013, 03:26:15 am: Quote from: bytemaster on November 06, 2013, 06:59:12 pm
Quote from: Lighthouse on November 06, 2013, 06:58:16 pm
Currently it's set to two weeks, but because of how much power is in the network, the 5 minute blocks are taking 30 seconds or less so 1 day = 1 week, adjustment should be in the next 18 hours.
Adjustment should be in the next 8 hours...

I am seeing difficulty at: 0.00000382 is this the current and correct? Thanks :)
Title: Re: Difficulty did not change after block 2016
Post by: FreeTrade on November 07, 2013, 03:34:09 am: Quote from: smith88 on November 07, 2013, 03:26:15 am
I am seeing difficulty at: 0.00000382 is this the current and correct? Thanks :)

Yes, that's correct - we got the maximum difficulty adjustment allowed in the code. However a lot of the computational power in the network was masked by orphan and stale block, so we've still got very fast block time of about 48 seconds.