BIP 66 status

[jl2012]

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://bitcointalk.org/index.php?topic=152348.0

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

[keystroke]

BIP66 has been activated. Enforcement still pending.

[FinalHash]

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

[TierNolan]

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

[trout]

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.

[trout]

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

[TierNolan]

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.

[gmaxwell]

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]

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.

[windpath]

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?

[jl2012]

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

[TierNolan]

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.

[keystroke]

Pieter has updated the 2k graph to show the first possible time of 95% at v3.

[jl2012]

Pieter has updated the 2k graph to show the first possible time of 95% at v3.

Someone just found 2 version 2 blocks after a long run of version 3.

At block 363628, there are only 53 version 2 blocks in the last 1001 blocks. The first possible 95% time is 363703, with 75 blocks left.

[TierNolan]

Pieter has updated the 2k graph to show the first possible time of 95% at v3.

That assumes 100% v3 blocks from now on.  It inherently underestimates the time.

He could add an estimated time which uses his 288 average.  It looks like the average is now 95.5 - 96.0%.

[jl2012]

363721 now. 4 blocks left

[jl2012]

It completes at block 363275, an empty block by AntPool 

[Dennis7777]

It completes at block 363275, an empty block by AntPool 

And now those laggard miners who still create version 2 blocks is going to lose their blocks.
First victim: Block #363726 and #363731 by BTC Nuggets
https://blockchain.info/block/0000000000000000032527aa796d3672e32e5f85a452d3a584a28fc7efbcd5d0
https://blockchain.info/block/0000000000000000009cc829aa25b40b2cd4eb83dd498c12ad0d26d90c439d99

[jl2012]

It completes at block 363275, an empty block by AntPool  

And now those laggard miners who still create version 2 blocks is going to lose their blocks.
First victim: Block #363726 and #363731 by BTC Nuggets
https://blockchain.info/block/0000000000000000032527aa796d3672e32e5f85a452d3a584a28fc7efbcd5d0
https://blockchain.info/block/0000000000000000009cc829aa25b40b2cd4eb83dd498c12ad0d26d90c439d99

That's really poor luck. They just need to find the 363725 and that will defer the switch.

Now they have lost $12500 but I think they deserve the loss

[Dennis7777]

F2Pool is creating version 3 block but it looks like the pool has not rejected the #363731 version 2 block and is working on top of it.
https://blockchain.info/block/0000000000000000155f2519d35cd5d2869900bcc5093594b27763a0315390b4

Also, it seems blockchain.info doesn't reject version 2 blocks as well, which could create problems to those using its wallet or APIs.