HERE IS HOW THE FORK WILL HAPPEN.

[cpfreeplz]

- 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.

What I could say on this overwhelmingly mathematical information that bursts into my  small head. This are really amazing.

I am just the other guy who gladly receiving great information.

As understanding on the suggestion above. I have to pull out my bitcoin from online and put it to my desktop wallet. To make it safe.

Now if you're smart you'll keep it off of exchanges for the rest of your life... or you'll be one of these dumbos that shows up only when their bitcoins get hacked off of each exchange they use. Buy your bitcoins then transfer them to yourself. Don't ever trust an exchange.

[pizamoi]

- 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.

What I could say on this overwhelmingly mathematical information that bursts into my  small head. This are really amazing.

I am just the other guy who gladly receiving great information.

As understanding on the suggestion above. I have to pull out my bitcoin from online and put it to my desktop wallet. To make it safe.

Now if you're smart you'll keep it off of exchanges for the rest of your life... or you'll be one of these dumbos that shows up only when their bitcoins get hacked off of each exchange they use. Buy your bitcoins then transfer them to yourself. Don't ever trust an exchange.

Wait if I understood this correctly assuming the current futures price of BCC is correct they will get around 10% of bitcoins mining power, that means I will have to wait over 1-2 hours per confirmation? That makes it even less attractive a choice...

[DannyHamilton]

Wait if I understood this correctly assuming the current futures price of BCC is correct they will get around 10% of bitcoins mining power, that means I will have to wait over 1-2 hours per confirmation? That makes it even less attractive a choice...

I haven't looked at BCC code yet, so I'm not ceratin, but I'm guessing that they altered the difficulty calculation so that mining will initially be easier.

[d1ceplayer]

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

Yes exactly we are watching these people in the forum in daily base they should need to contact to writers that they will write a posts for them. That they will run this forum if they are do not know about English but instead saying you should need to say that in positive words that he might not get hurt by this because he also want to work in bitcoin but it is not his fault suggest him some site where he can learn.

[Ewinsane]

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.

It is right that nothing happening with the world to destroy completely and may be the expected fork solved many problems in future for a smooth run of bitcoin in the market. We should have to keep hope for better of the future. Why we consider that the fork will be hard, may be it is soft. For the time being sorrow may not cause for complete disappointment.

[JNiks_ZLisa]

Since Bitcoin Cash is a large block hard fork, does this mean that Bitcoin Classic (current protocol with no changes as discussed in this thread) will be a third chain actively supported on August 1?

Yes

[xbiv2]

Now all miners signaling segwit acceptance, because no any profit not to do this.
But when come time to fork BITCOIN of 2014 (CLASSIC) from BITCOIN SEGWIT "soft fork" this will be changed.

[alecfisker]

Original Bitcoin Classic developer abandoned project, coin was taken over by investors community, I contacted exchange to reactivate coin, they ask for a secret word, who have developer contacts please