Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.100 as permitted sender)
	client-ip=62.13.148.100; envelope-from=pete@petertodd.org;
	helo=outmail148100.authsmtp.co.uk; 
Date: Fri, 19 Jun 2015 12:15:53 -0400
From: Peter Todd <pete@petertodd.org>
To: Stephen Morse <stephencalebmorse@gmail.com>
Message-ID: <20150619161553.GA20730@savin.petertodd.org>
References: <20150619103959.GA32315@savin.petertodd.org>
	<CABHVRKR7bXfDX0_frAv_Ph4Saz3SXwXeZae1DEokorvekPeinw@mail.gmail.com>
	<20150619134408.GB27280@savin.petertodd.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o"
Content-Disposition: inline
In-Reply-To: <20150619134408.GB27280@savin.petertodd.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee
Precedence: list


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

On Fri, Jun 19, 2015 at 09:44:08AM -0400, Peter Todd wrote:
> On Fri, Jun 19, 2015 at 09:33:05AM -0400, Stephen Morse wrote:
> > It is disappointing that F2Pool would enable full RBF when the safe
> > alternative, first-seen-safe RBF, is also available, especially since t=
he
> > fees they would gain by supporting full RBF over FSS RBF would likely be
> > negligible. Did they consider using FSS RBF instead?
>=20
> Specifically the following is what I told them:

Incidentally, because someone asked that message was sent two weeks ago.


Also, a shout-out to Marshal Long of FinalHash for his help with
(FSS)-RBF deployment and for getting F2Pool and myself in touch, as well
as his work in talking getting pools on board with BIP66.

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

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

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

iQGrBAEBCACVBQJVhEA1XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwZjZhZTZkMTlhMDVhODRlMjk2NDAyYjIxNzQ2ZWNjNmEy
MThmZThhNDE5Yzc2MWIvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfuyAQf/TK3nK2DNpDiLNYnmx2pt0uEm
emKXDROsVVCkhcsH3RF+8c6vO5uPhssqhEjbsjQBg61zBIjk2gou4aKJqhA0vfTx
x0mVde38AYRZWBsjjW+xZFhfpVCzV7gce3fcGYAFDdbR9EApKK7DpOE60xd56qoy
WRF9WZriBtZpAu3G4kyOsBixImDpAS8WUFV1qwLnBFuXDoPJ6UmTV2GhGmgUm7zD
oxl+JALSv+r0KsAgkafd0OdpwxsWciRjDmPW7kLzRV49JfLP1dHulzfLtCEs/YLL
SUOBtYbiXctuhauC1PEyGte8ca2V6YJIDnGpxtAcfb0BPj/rXJJoDVzWtWm2Yg==
=0ozn
-----END PGP SIGNATURE-----

--IS0zKkzwUGydFO0o--