Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.78 as permitted sender)
	client-ip=62.13.149.78; envelope-from=pete@petertodd.org;
	helo=outmail149078.authsmtp.net; 
Date: Wed, 10 Jun 2015 16:03:23 -0400
From: Peter Todd <pete@petertodd.org>
To: Nathan Wilcox <nathan@leastauthority.com>
Message-ID: <20150610200323.GA13724@savin.petertodd.org>
References: <CAFdHNGgtgWGu8gnnJfM0EcVn2m_Wff5HPwAe-9FBvjR++q0Q-Q@mail.gmail.com>
	<CACq0ZD5=EunMZJJMKfFUGkR=Ye_8nmV0qLkJJ997gbWk1MTC9w@mail.gmail.com>
	<CAFdHNGh=eGCwoMF36Siup-h6aSQtE0mvxCfk+OQRJb-37pds9w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu"
Content-Disposition: inline
In-Reply-To: <CAFdHNGh=eGCwoMF36Siup-h6aSQtE0mvxCfk+OQRJb-37pds9w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
Precedence: list


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

On Wed, Jun 10, 2015 at 02:00:27PM -0600, Nathan Wilcox wrote:
> On Wed, Jun 10, 2015 at 1:19 PM, Aaron Voisine <voisine@gmail.com> wrote:
>=20
> > It could be done by agreeing on a data format and encoding it in an
> > op_return output in the coinbase transaction. If it catches on it could
> > later be enforced with a soft fork.
> >
> >
> Sounds plausible, except SPV protocols would need to include this coinbase
> txn if it's going to help SPV clients. (Until a softfork is activated, SPV
> clients should not rely on this encoding, since until that time the resul=
ts
> can be fabricated by individual miners.)

Fee stats can always be fabricated by individual miners because fees can
be paid out-of-band.

--=20
'peter'[:-1]@petertodd.org
00000000000000001245bd2f5c99379ee76836227ded9c08324894faabc0d27f

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

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

iQGrBAEBCACVBQJVeJgHXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxMjQ1YmQyZjVjOTkzNzllZTc2ODM2MjI3ZGVkOWMwODMy
NDg5NGZhYWJjMGQyN2YvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfsZ6Af+PN7fDxOf/WmqTN6hsxmf5xmu
fl/HwTl6+GDWtERs91l+LhmSvFrYohNxSvGmgSJwxciYIDXlPQJwH6062ENhWLmh
wc6weHPmp9q/ZaeFYvw6hzv1kXUfxQjOIjTJ0ZOMNAL+0+OvUakwl2sxeedDzq1N
qfASPMFSw3lm2pVsUd+UQETEUMG3u4LQSA4gLKPwbyWKkvNUOBet1Fv5O7VEHpEW
/gxejMuXxCSsP/2s8nGhqZJcf4J2SVdNpU1FYfLjbxNr6dnUJVqwtU3DVGUXIobR
+iWb6vDKWGVKE+1U5ZRFSlNWCCwRc7o/kfH21D7/PwJMXxMgrhIFn10BABNKhw==
=zd6Y
-----END PGP SIGNATURE-----

--sdtB3X0nJg68CQEu--