BIP 66 status - page 2. | Bitcointalksearch.org

TierNolan

legendary

Activity: 1232

Merit: 1094

Quote from: windpath on July 02, 2015, 08:16:17 AM

From the looks of things I'd guess by Monday at the latest we will have BIP 66 enforcement, and possibly even today?

If the miner support is 95.5%, then it could take a while.

If the last 1000 blocks are 94%, then you need 2/3 of the window to be the higher rate to get over 95%. It could be a week yet. The last 288 window is only barely exceeding 95% consistently.

jl2012

legendary

Activity: 1792

Merit: 1111

Quote from: windpath on July 02, 2015, 08:16:17 AM

P2Pool is currently around 74% upgraded, and slowly climbing...

We are obviously hoping not to dump 26% of our hashrate when enforcement happens and are working to reach out to nodes that have not yet upgraded.

From the looks of things I'd guess by Monday at the latest we will have BIP 66 enforcement, and possibly even today?

If I count it correctly, there is at least 119 blocks to go at block 363484

windpath

legendary

Activity: 1258

Merit: 1027

P2Pool is currently around 74% upgraded, and slowly climbing...

We are obviously hoping not to dump 26% of our hashrate when enforcement happens and are working to reach out to nodes that have not yet upgraded.

From the looks of things I'd guess by Monday at the latest we will have BIP 66 enforcement, and possibly even today?

TierNolan

legendary

Activity: 1232

Merit: 1094

Quote from: gmaxwell on June 29, 2015, 02:32:48 AM

Minimum of 212 blocks until BIP66 enforcement right now (as of height 363020).

Based on the last 288 graph, it looks like miner support is at 94.5% and holding.

I think once it hit around 75%, CHECKLOCKTIMEVERIFY deployment could have started.

gmaxwell

staff

Activity: 4284

Merit: 8808

Quote from: TierNolan on June 28, 2015, 08:04:29 AM

I think there was a "hard fork" of the p2pool chain recently though to allow for a higher block version.

Orthogonal, there was an update which included a non-consensus change to pass through the higher version number that bitcoin core was already providing, as well as a non-consensus change to require Bitcoin core 0.10+, plus a non-consensus change to emit p2pool share v14, plus a p2pool-consensus change to enable requiring share v14, so that it's possible to fork off the participants who haven't upgraded once BIP66 has taken effect. The latest p2pool block was v3.

Unfortunately, people thought that upgrading bitcoin was sufficient for p2pool to emit version 3 blocks, but unfortunately there was a min(template.version, 2) in the codebase; I didn't get around to checking until a couple days ago. Forrestv fixed it nearly instantly after I emailed him about it. Sadly, P2pool is hardly even a thing anymore... but the remaining users upgraded quickly and about 63% of P2Pool's hashrate updated in about two days, which I think is pretty good.

Minimum of 212 blocks until BIP66 enforcement right now (as of height 363020).

TierNolan

legendary

Activity: 1232

Merit: 1094

Quote from: trout on June 28, 2015, 08:02:18 AM

P2Pool is dangerously lagging behind. As usual, for them it's more difficult to upgrade.

I don't think p2pool has a version number. It is whatever version of bitcoind that the p2pool miner is using, so different blocks found can be for different versions.

I think there was a "hard fork" of the p2pool chain recently though to allow for a higher block version.

trout

sr. member

Activity: 333

Merit: 252

P2Pool is dangerously lagging behind. As usual, for them it's more difficult to upgrade.

trout

sr. member

Activity: 333

Merit: 252

Quote from: TierNolan on June 25, 2015, 01:13:50 PM

Looks like the last few miners are updating. It exceeded 94% for a moment. Hopefully, noise will be enough to push it over 95%.

the 1001 block window is there precisely not to give the noise much chance.
But it'll get there eventually.

TierNolan

legendary

Activity: 1232

Merit: 1094

Looks like the last few miners are updating. It exceeded 94% for a moment. Hopefully, noise will be enough to push it over 95%.

FinalHash

member

Activity: 108

Merit: 10

anybody have requests for pools that are not using it? i know mostly everyone

keystroke

hero member

Activity: 900

Merit: 1014

advocate of a cryptographic attack on the globe

BIP66 has been activated. Enforcement still pending.

jl2012

legendary

Activity: 1792

Merit: 1111

Quote from: altcoinex on May 21, 2015, 02:37:04 PM

Quote from: jl2012 on May 21, 2015, 12:59:50 PM

Quote from: TierNolan on May 21, 2015, 09:34:19 AM

Quote from: FinalHash on May 21, 2015, 08:16:18 AM

I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.

There was a version of 0.9 released which can handle version 3 blocks.

This allows nodes running older versions of the software to vote/accept version 3 blocks.

http://sourceforge.net/p/bitcoin/mailman/message/34124466/

https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.md

Once 75% of the network starts enforcing the rules, legacy nodes could end up accepting invalid version 3 blocks. That is an expensive DOS attack though, since it requires spending POW on invalid blocks.

And the attack like this would not be very effective because 75% of the network is mining a more restrictive chain.

I think the more common theorized attack vector with this situation is double spending.

--edit--: It has happened prior : https://bitcointalksearch.org/topic/a-successful-double-spend-us10000-against-okpay-this-morning-152348

The one you quote was a purposive 51% attack. Not comparable with a planned softfork

altcoinex

sr. member

Activity: 293

Merit: 251

Director - www.cubeform.io

Quote from: jl2012 on May 21, 2015, 12:59:50 PM

Quote from: TierNolan on May 21, 2015, 09:34:19 AM

Quote from: FinalHash on May 21, 2015, 08:16:18 AM

I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.

There was a version of 0.9 released which can handle version 3 blocks.

This allows nodes running older versions of the software to vote/accept version 3 blocks.

http://sourceforge.net/p/bitcoin/mailman/message/34124466/

https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.md

Once 75% of the network starts enforcing the rules, legacy nodes could end up accepting invalid version 3 blocks. That is an expensive DOS attack though, since it requires spending POW on invalid blocks.

And the attack like this would not be very effective because 75% of the network is mining a more restrictive chain.

I think the more common theorized attack vector with this situation is double spending.

--edit--: It has happened prior : https://bitcointalksearch.org/topic/a-successful-double-spend-us10000-against-okpay-this-morning-152348

jl2012

legendary

Activity: 1792

Merit: 1111

Quote from: TierNolan on May 21, 2015, 09:34:19 AM

Quote from: FinalHash on May 21, 2015, 08:16:18 AM

I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.

There was a version of 0.9 released which can handle version 3 blocks.

This allows nodes running older versions of the software to vote/accept version 3 blocks.

http://sourceforge.net/p/bitcoin/mailman/message/34124466/

https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.md

Once 75% of the network starts enforcing the rules, legacy nodes could end up accepting invalid version 3 blocks. That is an expensive DOS attack though, since it requires spending POW on invalid blocks.

And the attack like this would not be very effective because 75% of the network is mining a more restrictive chain.

TierNolan

legendary

Activity: 1232

Merit: 1094

Quote from: FinalHash on May 21, 2015, 08:16:18 AM

I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.

There was a version of 0.9 released which can handle version 3 blocks.

This allows nodes running older versions of the software to vote/accept version 3 blocks.

http://sourceforge.net/p/bitcoin/mailman/message/34124466/

https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.md

Once 75% of the network starts enforcing the rules, legacy nodes could end up accepting invalid version 3 blocks. That is an expensive DOS attack though, since it requires spending POW on invalid blocks.

FinalHash

member

Activity: 108

Merit: 10

I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.

FinalHash

member

Activity: 108

Merit: 10

Doing my boy Petey A solid of course!

Peter Todd

legendary

Activity: 1120

Merit: 1152

Quote from: trout on May 18, 2015, 01:01:55 AM

Quote from: TierNolan on May 17, 2015, 04:58:39 PM

I guess a pool must have upgraded.

yep, it's AntPool

It's my buddies at FinalHash.

trout

sr. member

Activity: 333

Merit: 252

Quote from: TierNolan on May 17, 2015, 04:58:39 PM

I guess a pool must have upgraded.

yep, it's AntPool

TierNolan

legendary

Activity: 1232

Merit: 1094

Looks like there was a spike in the last few days. If that is maintained, it means the vote is around 57% - 43%. I guess a pool must have upgraded. The 1 year graph shows a slope due to initial release then level then a step and level again and now another step.

Topic: BIP 66 status - page 2. (Read 8230 times)