On 08/03/2017 12:48 PM, 'Jean-Pierre Rupp' via bitcoinj wrote: > Perhaps I am missing some code, but I can't seem to find any code that > enforces the BIP34, BIP65 and BIP66 block versions at specific blockchain > heights. Am I right? Will bitcoinJ allow older block version numbers to be > used in new blocks as long as they have enough PoW?
VersionTally keeps track of BIP activations in the above cases. However, this only works if you sync the chain from genesis; in the more common case of syncing from a checkpoint the first x blocks are not enforced. Enforcing BIP9-based activiations will be even harder as version bits don't keep their state after activation. In the end, we will need to depend on hardcoded block heights, but those we only know after the fact. So basically it's the PoW that counts. -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoinj+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
