Date: Fri, 12 May 2017 18:22:14 -0400
From: Peter Todd <pete@petertodd.org>
To: Luke Dashjr <luke@dashjr.org>
Message-ID: <20170512222214.GA4462@fedora-23-dvm>
References: <201705121922.57445.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK"
Content-Disposition: inline
In-Reply-To: <201705121922.57445.luke@dashjr.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP: Block signal enforcement via tx fees
Precedence: list


--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, May 12, 2017 at 07:22:56PM +0000, Luke Dashjr via bitcoin-dev wrote:
> I've written a new BIP draft for OP_CHECKBLOCKVERSION to allow the commun=
ity=20
> to put economic pressure on miners to deploy softforks without the extrem=
e of=20
> a UASF.
>=20
>     https://github.com/luke-jr/bips/blob/bip-cbv/bip-cbv.mediawiki

I strongly disagree with this proposal.

nVersion signaling is already technically unenforceable, in the sense that =
we
don't have good ways of ensuring miners actually adopt the rules they're
claiming to signal. Equally, it's users who ultimately adopt rules, not min=
ers,
and attempting to pay miners to signal certain bits will further confuse th=
is
point.

Quite likely the outcome of users trying to anonymously pay anonymous miner=
s to
signal certain bits will be the complete breakdown of the honesty of the
nVersion signalling system, currently enforced only by "gentlemans agreemen=
t".

A more productive direction would be a direct coin-owner signalling process,
with users taking action based on what provable coin-ownership has signalle=
d.


Also, as an aside, this "specification" again shows the inadequacy and
unreadability of English language specifications. I'd strongly suggest you
delete it and instead mark the "reference implementation" as the specificat=
ion.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJZFjWUAAoJECSBQD2l8JH7eEMH/2Vtbl3oDycuJZ5TQgvj55x5
0lMod3nzh51PBfUSaIEefDxHbXvacl6QDsRusGOU27VcxxX+pcnrl8TVbmR5URO6
5z5L2AffJtnNLKWvqAxWSaH8jJr0Ss9QyGcGArjKySa3ZqdKSq/S0cKI1NeBz1Fw
0rRgFXps6uVGjOzfveNtzGvJcGyuhlfcKPwkeHEmBmnl0l6ZSzRNaTaPE3SRZqqe
foe/i7ZAvaodhNKbicX2Y8EpE8pOW4/AV4gG9JmAPxj9vn9NiOveDYVhyOPDGncO
0Q3dLOwwGEaswZpxuLEd/c7M7LaxJmjHh9c4H0e5Fa4aK0ohsHtEubeXh/i3AUI=
=dqOY
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--