From: Tom Harding <tomh@thinlink.com>
To: Bitcoin-Dev <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <26b3141b-1e7b-05fd-317b-e03b28beb4db@thinlink.com>
Date: Sun, 31 Jul 2016 11:01:18 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101
	Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="Ax7VFeT0Ts7sp7tQjpf8tHIxKN5DjJK78"
Subject: [bitcoin-dev] Proposal: Hard fork opt-out bits
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Ax7VFeT0Ts7sp7tQjpf8tHIxKN5DjJK78
Content-Type: multipart/mixed; boundary="cRGdkDW4ag0SUoiwG6iDhiBBhkpDI6BDb"
From: Tom Harding <tomh@thinlink.com>
To: Bitcoin-Dev <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <26b3141b-1e7b-05fd-317b-e03b28beb4db@thinlink.com>
Subject: Proposal: Hard fork opt-out bits

--cRGdkDW4ag0SUoiwG6iDhiBBhkpDI6BDb
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Your thoughts are sought on this simple proposal to allow transaction
authors to restrict execution to fewer than all blockchain forks where
the transaction would otherwise be valid.


Proposal

Node implementations select a bit from among the upper 8 bits of the
transaction version space to enforce as a hard fork opt-out bit.

To specify that a transaction NOT be mined by nodes that enforce a
particular bit, authors set that bit in the transaction version.
Opt-out is enforced by consensus among nodes enforcing each bit.

An implementation will relay, process and mine transactions that opt out
of other blockchain forks; just not those that opt out of its own fork.


Notes

Example: Via soft fork, all implementations may begin enforcing hard
fork opt-out bit 30.  Post soft fork, setting this bit would make a
transaction invalid, unless a fork emerges that has stopped enforcing
bit 30.

Example: BIP109 implementations may stop enforcing bit 30 and begin
enforcing bit 28 when the BIP109 hard fork is activated for a chain they
are tracking.

Enforcing more than one hard fork opt-out bit would imply that an
implementation is actively participating in building more than one
blockchain fork, and therefore providing a way to opt out of each.


--cRGdkDW4ag0SUoiwG6iDhiBBhkpDI6BDb--

--Ax7VFeT0Ts7sp7tQjpf8tHIxKN5DjJK78
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJXnjz1AAoJEG/AI00/Ca/qwswP/A/w7ppxIK3GRNtH/BPGbfGX
re5HSwrY0dMOOWaJx0w8fLkOSQ8l6n+sI4jGlUpBkm27qihgIJjpQelY8RAllYH/
3XC3zzrn8TeHnZb5424FJLi0tL9B9lWqIUU21UEl7hHJOlSGrhALs6oYppCG7Wcv
+bB+Ehm28/zsoNdpQBsPQBOJCEU+VLN+uBkj6+eCWT77FwMR5dwk78ujNgOzWnqA
bx6nqKBHXrqu5Tze8P5jW62h3YUkFQ3uYR9TW4esDBodSjx68OPAuaAM4K1pFUBV
rT1a1Ya8skqFOeTgpZ5qmcjiqBF/fEyToGvaV7NTHdoKWYHh8WO95NKg8RkeC54N
Hp0y0/vRy404KaFpftvXj2JoyWwGgVszl4SU6cH2d4iCXtIAVT8OU9gNIkpaAwXN
quizSj5etBEYCr/hYWIVwI9sehY4cyRG2OrhKaxIZffo4eB++HfvV01NJVh7n4pZ
cO8NO2blpCJsVBRbpuHTpb85+ef0xLRJuyHxts5WeivfJ2SUUxxsJ5Pf49lUEtUb
DrQrDB+2lQNhigQ50kPyaUVCOWRzyRAITnhFomeE0/H6oq2QQJgx63pG8U8A/0oc
f6DMAuaJ3GnDnGLgW8i6WFaG/Qby2EtmczSXtGFRcKoPJUVMUPXRZgbGQAyyZ1QE
xT3kFrnCWKendZRj3tb9
=iQoc
-----END PGP SIGNATURE-----

--Ax7VFeT0Ts7sp7tQjpf8tHIxKN5DjJK78--