Date: Mon, 29 Jun 2015 01:53:15 -0400
From: Peter Todd <pete@petertodd.org>
To: Gregory Maxwell <gmaxwell@gmail.com>
Message-ID: <20150629055314.GB502@savin.petertodd.org>
References: <20150629050726.GA502@savin.petertodd.org>
	<201506290540.26019.luke@dashjr.org>
	<CAAS2fgRZh=__VGH8aJq4D9G62ostt20YUafJ66mm7BhdBRKe=Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="s2ZSL+KKDSLx8OML"
Content-Disposition: inline
In-Reply-To: <CAAS2fgRZh=__VGH8aJq4D9G62ostt20YUafJ66mm7BhdBRKe=Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP: Full Replace-by-Fee deployment schedule
Precedence: list


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

On Mon, Jun 29, 2015 at 05:43:13AM +0000, Gregory Maxwell wrote:
> On Mon, Jun 29, 2015 at 5:40 AM, Luke Dashjr <luke@dashjr.org> wrote:
> > Policy is node/miner fiat and not the domain of BIPs.
>=20
> Even accepting the premise that policy is pure local fiat, the
> conclusion doesn't follow for me. BIPs about best practices or
> especially anything where interop or coordination are, I think,
> reasonable uses of the process.
>=20
> E.g. you might want to know what other kinds of policy are in use if
> you're to have any hope of authoring transactions that work at all!

For example, consider Luke-Jr's own BIP19, M-of-N Standard Transactions,
a non-consensus-critical suggested policy change!

    https://github.com/bitcoin/bips/blob/master/bip-0019.mediawiki

Anyway, full-RBF has significant impacts for wallet authors and many
other stakeholders. At minimum it changes how you will want to author
and (re)author transactions, much like BIP19 does.

--=20
'peter'[:-1]@petertodd.org
00000000000000000ffad4a87861689c067f5dd3b98b84d8096572c163aa913a

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

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

iQGrBAEBCACVBQJVkN1FXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwZmZhZDRhODc4NjE2ODljMDY3ZjVkZDNiOThiODRkODA5
NjU3MmMxNjNhYTkxM2EvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkft4BAf+PLQR40Li1C0wfAq6jMN1J8Es
TaYdjTEQSelvhEgmc5Qx9yBOtdkJppKSLbDFriBRjNy1KnqRwJg2xGppP2u/gBGH
XsKuNusym3cRDFJlG+/4t66e/8iu7MI91+xoBsdx1DLcTunsretWe18IqmsJf9VA
2uQCY5qXi+rvZBv4EcA2qbdvZlTFbqRrhI9O3jdPqF3yVoF88QCow9A0W1lhk8Af
3LAW13v1MxEezobk19qBEROvstgO4hzSRz9KnDOwcPWzucn/Xy3KPOVS+DJSqkuJ
PCDKh2FrT0jK7RPItGH+2+djMw10X+mEZ+FL1RGFl/uAQo450bH1djL4HUAAWA==
=Fmp2
-----END PGP SIGNATURE-----

--s2ZSL+KKDSLx8OML--