Re: [bitcoin-dev] Multi-Stage Merge-Mine Headers Hard-Fork BIP

I've updated the BIP with your suggestions, would it make sense to just move the activation condition to the 42 week boundary instead of repeating the last header? Would that be at block 6048 from the start of the timewarp?

Re: [bitcoin-dev] Multi-Stage Merge-Mine Headers Hard-Fork BIP

You need more detail for it to be a BIP. New Header new_header.prev = hash of previous header's bitcoin header new_header.small_nonce = 4 byte nonce new_header.big_nonce = 8 byte nonce new_header (Can contain any new fields desired) Fake Block block.version = 4 block.prev =

[bitcoin-dev] Multi-Stage Merge-Mine Headers Hard-Fork BIP

https://github.com/bitcoin/bips/pull/340 BIP: ? Title: 2016 Multi-Stage Merge-Mine Headers Hard-Fork Author: James Hilliard Status: Draft Type: Standards Track Created: 2016-02-23 ==Abstract== Use a staged hard fork to implement a headers format change that is merge