HERE IS HOW THE FORK WILL HAPPEN. - page 2.

DannyHamilton

legendary

Activity: 3388

Merit: 4615

Quote from: JNiks_ZLisa on July 28, 2017, 10:01:42 AM

D1=blocks/days
D2=blocks/(days+days*3)
D2=D1/4

Maximum possible is handled here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/pow.cpp#L58

Code:

if (nActualTimespan > params.nPowTargetTimespan*4)
nActualTimespan = params.nPowTargetTimespan*4;

Since target timesapan is 14 days, if actual timespan is greater than:
14 days * 4 = 56 days

Then actual timespan is adjusted and set equal to
14 days * 4 = 56 days

Difficulty retarget is then calculated here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/pow.cpp#L65

Code:

bnNew.SetCompact(pindexLast->nBits);
bnNew *= nActualTimespan;
bnNew /= params.nPowTargetTimespan;

So...

Start with existing difficulty X

Code:

Multiply by actual timespan (maximum 56 days)

Code:

56 * X = 56X

divide by target timespan (14 days)

Code:

56X / 14 = 4X

result is 4X difficulty fall at 56 or more days.

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: DannyHamilton on July 28, 2017, 08:49:34 AM

Quote from: JNiks_ZLisa on July 28, 2017, 08:40:06 AM

- snip -
optimal is 15*3 = 45 days, for 4x difficulty fall (maximum posible for 1 period).

Check the math in case I'm wrong, but I think 45 days is only 3.2x difficulty fall.

If you want 4x difficulty fall, I think you need 14*4 = 56 days.

D1=blocks/days
D2=blocks/(days+days*3)
D2=D1/4

DannyHamilton

legendary

Activity: 3388

Merit: 4615

Quote from: JNiks_ZLisa on July 28, 2017, 08:40:06 AM

- snip -
optimal is 15*3 = 45 days, for 4x difficulty fall (maximum posible for 1 period).

Check the math in case I'm wrong, but I think 45 days is only 3.2x difficulty fall.

If you want 4x difficulty fall, I think you need 14*4 = 56 days.

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: DannyHamilton on July 27, 2017, 07:33:38 PM

Quote from: JNiks_ZLisa on July 27, 2017, 05:22:25 PM

then (after 15 days) generate 1 block.

Maybe more than 15 days.

Maybe 28 days. Maybe more than 56 days.

optimal is 15*3 = 45 days, for 4x difficulty fall (maximum posible for 1 period).

Kwelstr

member

Activity: 107

Merit: 10

I've got amazing powers of observation

I have created a poll to see how the community views the fork and the future of bitcoin. Please answer the poll so we can have a statistically significant number of responses.

https://bitcointalk.org/index.php?topic=2048167.0;all

I am trying to be fair on that poll and included as many answers as I could think of. I will keep the poll open until a couple of hours before the Aug 1st fork. Let's see if the wisdom of the forum is indicative of how it will turn out.

Thank you for participating.

btccashacc

legendary

Activity: 1120

Merit: 1000

Quote from: Sithara007 on July 24, 2017, 10:25:02 PM

Quote from: tauceramica on July 24, 2017, 05:35:46 PM

3-4 months ago, poloniex had explained that they were ready for hard fork and they will also issue the splitted bitcoin one. But this time, they're very silent and we don't know what will happen to our bitcoins.

Check this:

https://poloniex.com/press-releases/2017.07.24-Our-plans-to-handle-potential-BTC-network-disruptions/

I think that Poloniex has gone back on its word. This is what they are saying now:

Quote

Even if two viable blockchains emerge, we may or may not support both and will make such a decision only after we are satisfied that we can safely support either blockchain in an enterprise environment.

Bittrex also has just announced their statement regarding the hard fork.

Quote

If you have a Bitcoin (BTC) balance on Bittrex 24 during the BCC UAHF time on August 1st, 5:20am (12:20pm UTC), you will be credited the equivalent amount of Bitcoin Cash (BCC) on a 1:1 basis. i.e. 1 BTC on Bittrex held during the on-exchange snapshot will get you 1 BCC.

Here's the link : https://support.bittrex.com/hc/en-us/articles/115000808991

I personally control my private key, i have some on poloniex and bittrex but only small amount, it's not big deal if something bad happens with my coin.

DannyHamilton

legendary

Activity: 3388

Merit: 4615

Quote from: JNiks_ZLisa on July 27, 2017, 05:22:25 PM

then (after 15 days) generate 1 block.

Maybe more than 15 days.

Maybe 28 days. Maybe more than 56 days.

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: DannyHamilton on July 27, 2017, 06:43:06 PM

Quote from: JNiks_ZLisa on July 27, 2017, 05:22:25 PM

Need to make blockchain split just before Difficulty adjusts, then (after 15 days) generate 1 block.

How many blocks during those 15 days?

If blockchain splits then there will be less hash power.

If there is less hash power, then blocks will be slower.

If blocks are slower, then it takes more than 15 days for difficulty adjustment.

https://bitcoinwisdom.com/bitcoin/difficulty
split will happen 99.99% , people want trustable software and miners want money and will do it.

DannyHamilton

legendary

Activity: 3388

Merit: 4615

Quote from: JNiks_ZLisa on July 27, 2017, 05:22:25 PM

Need to make blockchain split just before Difficulty adjusts, then (after 15 days) generate 1 block.

How many blocks during those 15 days?

If blockchain splits then there will be less hash power.

If there is less hash power, then blocks will be slower.

If blocks are slower, then it takes more than 15 days for difficulty adjustment.

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: DannyHamilton on July 27, 2017, 05:09:57 PM

Quote from: JNiks_ZLisa on July 26, 2017, 11:38:52 AM

- snip -
Need to generate 1 block at the and of 15 days period and it will cause 4x difficulty drop.
- snip -

Not true.

Difficulty adjusts after 2016 blocks. NOT after 15 days.

If blocks happen at near NORMAL speed (average 1 block every nearly 10 minutes) then difficulty adjusts after approximately 14 days:
2016 blocks * 10 minutes = 20160 minutes = 336 hours = 14 days

If there is not enough hash power and therefore blocks take longer, then difficulty takes longer to adjust.

2016 blocks * average 40 minutes per block = 80640 minutes = 1344 hours = 56 days until difficulty adjusts 4X

See code here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/pow.cpp#L19

Specifies params.DifficultyAdjustmentInterval:

Code:

// Only change once per difficulty adjustment interval
if ((pindexLast->nHeight+1) % params.DifficultyAdjustmentInterval() != 0)
{
...

params.DifficultyAdjustmentInterval calculated here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/consensus/params.h#L63

Code:

int64_t DifficultyAdjustmentInterval() const { return nPowTargetTimespan / nPowTargetSpacing; }

nPowTargetTimespan is set here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/chainparams.cpp#L79

Code:

consensus.nPowTargetTimespan = 14 * 24 * 60 * 60;

Note: 14*24*60*60 = 1209600

nPowTargetSpacing is set here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/chainparams.cpp#L80

Code:

consensus.nPowTargetSpacing = 10 * 60;

Note: 10 * 60 = 600

So, DifficultyAdjustmentInterval = 1209600 / 600 = 2016

So, adjustment happens when:
(pindexLast->nHeight+1) === 2016

In other words...

Only once every 2016 blocks.

Need to make blockchain split just before Difficulty adjusts, then (after 15 days) generate 1 block.

DannyHamilton

legendary

Activity: 3388

Merit: 4615

Quote from: JNiks_ZLisa on July 26, 2017, 11:38:52 AM

- snip -
Need to generate 1 block at the and of 15 days period and it will cause 4x difficulty drop.
- snip -

Not true.

Difficulty adjusts after 2016 blocks. NOT after 15 days.

If blocks happen at near NORMAL speed (average 1 block every nearly 10 minutes) then difficulty adjusts after approximately 14 days:
2016 blocks * 10 minutes = 20160 minutes = 336 hours = 14 days

If there is not enough hash power and therefore blocks take longer, then difficulty takes longer to adjust.

2016 blocks * average 40 minutes per block = 80640 minutes = 1344 hours = 56 days until difficulty adjusts 4X

See code here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/pow.cpp#L19

Specifies params.DifficultyAdjustmentInterval:

Code:

// Only change once per difficulty adjustment interval
if ((pindexLast->nHeight+1) % params.DifficultyAdjustmentInterval() != 0)
{
...

params.DifficultyAdjustmentInterval calculated here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/consensus/params.h#L63

Code:

int64_t DifficultyAdjustmentInterval() const { return nPowTargetTimespan / nPowTargetSpacing; }

nPowTargetTimespan is set here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/chainparams.cpp#L79

Code:

consensus.nPowTargetTimespan = 14 * 24 * 60 * 60;

Note: 14*24*60*60 = 1209600

nPowTargetSpacing is set here:
https://github.com/bitcoin/bitcoin/blob/1b046603b30ebfab6199a2f92015d507b248b590/src/chainparams.cpp#L80

Code:

consensus.nPowTargetSpacing = 10 * 60;

Note: 10 * 60 = 600

So, DifficultyAdjustmentInterval = 1209600 / 600 = 2016

So, adjustment happens when:
(pindexLast->nHeight+1) === 2016

In other words...

Only once every 2016 blocks.

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: iluvpie60 on July 27, 2017, 03:48:57 PM

Quote from: ?? on ??

This feels like it'll be a damn cluster fuck.

To be completely honest, it feels like there is more cluster FING going around by trolls and or paid trolls. Ithink once the update happens there really won't be almost any drama.

we are in the middle of pre-drama and it is worse than what is really gonna happen.

People are not able to correctly assess information. People respond to the tone and keywords like animals.

iluvpie60

hero member

Activity: 700

Merit: 500

Quote from: ?? on ??

This feels like it'll be a damn cluster fuck.

To be completely honest, it feels like there is more cluster FING going around by trolls and or paid trolls. Ithink once the update happens there really won't be almost any drama.

we are in the middle of pre-drama and it is worse than what is really gonna happen.

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: xmasdobo on July 27, 2017, 02:13:10 PM

fact: core devs have kept bitcoin safe and segwit has made the price skyrocket

How you know?

Quote from: xmasdobo on July 27, 2017, 02:13:10 PM

you are going to need more than that to convince me to run outdated software

Only well tested and trustable software.

xmasdobo

full member

Activity: 168

Merit: 100

fact: core devs have kept bitcoin safe and segwit has made the price skyrocket

you suggest going back to some old ass insecure version for no reason other than segwit conspiracy theory paranoia

you are going to need more than that to convince me to run outdated software

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: xmasdobo on July 27, 2017, 01:24:33 PM

Quote from: JNiks_ZLisa on July 26, 2017, 07:47:51 PM

Quote from: Qunenin on July 26, 2017, 12:32:26 PM

The world will not die with a bang, but with a whisper. I believe that this soft Fork while it solved many problems, basically since people up for hard Forks in the future. Basically, you get people past the first soft Fork, build up a lot of fear, and then show them there was nothing to be afraid of. Then, after a little more time is past. You start issuing a few more soft Fork here and there.

Problem is: no reason to trust bitcoin-core developers.

yeah, let's trust some retard that can't even speak english that spams forum with nonsense instead

Successful people talk about facts. Unsuccessful people talk about people.

xmasdobo

full member

Activity: 168

Merit: 100

Quote from: JNiks_ZLisa on July 26, 2017, 07:47:51 PM

Quote from: Qunenin on July 26, 2017, 12:32:26 PM

The world will not die with a bang, but with a whisper. I believe that this soft Fork while it solved many problems, basically since people up for hard Forks in the future. Basically, you get people past the first soft Fork, build up a lot of fear, and then show them there was nothing to be afraid of. Then, after a little more time is past. You start issuing a few more soft Fork here and there.

Problem is: no reason to trust bitcoin-core developers.

yeah, let's trust some random guy that can't even speak english that spams forum with nonsense instead

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: taxmanmt5 on July 27, 2017, 12:07:23 AM

Quote from: JNiks_ZLisa on July 26, 2017, 07:47:51 PM

Problem is: no reason to trust bitcoin-core developers.

once a forking is no big deal

If you have big money it big deal.

taxmanmt5

legendary

Activity: 1190

Merit: 1024

Quote from: JNiks_ZLisa on July 26, 2017, 07:47:51 PM

Quote from: Qunenin on July 26, 2017, 12:32:26 PM

The world will not die with a bang, but with a whisper. I believe that this soft Fork while it solved many problems, basically since people up for hard Forks in the future. Basically, you get people past the first soft Fork, build up a lot of fear, and then show them there was nothing to be afraid of. Then, after a little more time is past. You start issuing a few more soft Fork here and there.

Problem is: no reason to trust bitcoin-core developers.

You get people desensitized, to code changes, get them to the point where they expect him every few weeks or every few months or whatever, and then once a forking is no big deal, that's when you slam in the hard Fork with the big changes.

JNiks_ZLisa

full member

Activity: 182

Merit: 111

Quote from: Qunenin on July 26, 2017, 12:32:26 PM

The world will not die with a bang, but with a whisper. I believe that this soft Fork while it solved many problems, basically since people up for hard Forks in the future. Basically, you get people past the first soft Fork, build up a lot of fear, and then show them there was nothing to be afraid of. Then, after a little more time is past. You start issuing a few more soft Fork here and there.

Problem is: no reason to trust bitcoin-core developers.

Topic: HERE IS HOW THE FORK WILL HAPPEN. - page 2. (Read 6237 times)