Re: [bitcoin-dev] Introducing a POW through a soft-fork

> On Nov 6, 2017, at 20:38, Devrandom wrote: > > A hard-fork is a situation where non-upgraded nodes reject a block mined and > relayed by upgraded nodes. As Peter pointed out, that is the case here. > This creates a fork that cannot heal regardless of what follows.

Re: [bitcoin-dev] Generalised Replay Protection for Future Hard Forks

OK, so nForkId 0 is exactly the "valid on all chains" specifier I was asking about, cool. And your LN example (and nLockTime txs in general) illustrate why it's preferable to implement a generic replay protection scheme like yours *in advance*, rather than before each fork: all ad hoc RP schemes

[bitcoin-dev] Bitcoin Core 0.15.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version *0.15.1* is now available from: or Or through bittorrent: