Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.154 as permitted sender)
	client-ip=62.13.148.154; envelope-from=pete@petertodd.org;
	helo=outmail148154.authsmtp.co.uk; 
Date: Wed, 12 Mar 2014 12:47:50 -0400
From: Peter Todd <pete@petertodd.org>
To: Mike Hearn <mike@plan99.net>
Message-ID: <20140312164750.GA8199@savin>
References: <CABsx9T0Lvg84qFVRbc7Ef4vZEQj9eO7Jhup5PTRLLeuJFvXi-w@mail.gmail.com>
	<4fca6b510dd57d2f92affeb988d2ee5d.squirrel@fulvetta.riseup.net>
	<531FAA55.2020108@xeno-genesis.com> <531FC808.7060709@gmail.com>
	<9A6499BC-E546-45CC-A7EF-5182FC86052D@gmail.com>
	<53202D51.8010008@plan99.net>
	<CAJHLa0OuXyEz6gcq_dQKmGjJQf3cJjFyzjb38RCB3E6-wMLJ0g@mail.gmail.com>
	<CANEZrP2Lr0Do8dPXAvRPkZU0Hk4UBt=CjgXSSKbopawoq8NjgA@mail.gmail.com>
	<CAJHLa0OG4y_+7=z8_nuejHSynw+2CU9fzVGhAet3g0d3BoGCpg@mail.gmail.com>
	<CANEZrP02L2GsPSKFTncwvn95FpEz-LFysro4-Z+f25eRcENL8w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy"
Content-Disposition: inline
In-Reply-To: <CANEZrP02L2GsPSKFTncwvn95FpEz-LFysro4-Z+f25eRcENL8w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
Precedence: list


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

On Wed, Mar 12, 2014 at 05:41:33PM +0100, Mike Hearn wrote:
> >
> > Partially signed and multisig transactions within bitcoind go through
> > the raw transaction API, which does absolutely nothing if the sig
> > pushes the TX to a higher fee level.
>=20
>=20
> Well, we'll have to make sure this is carefully and loudly documented in
> the new developer part of the website that's being worked on. Because this
> seems like a recipe for people writing flaky apps. In practice it would
> seem like you need to implement the fee loop in your own app:
>=20
> 1) Create tx with an estimated fee level
> 2) Add signatures
> 3) Submit. If REJECT for too low fees, increment, go to 1 and try again.

Why?

It's the raw transaction API and Bitcoin Core wallet. What should be
carefully and loudly documented is the simple advice "Don't use to hold
customer funds; use Bitcoinj or something instead." followed by a
warning that SPV isn't secure enough for a business unless you run your
own full node.

The raw transaction API has no support to handle fees at all.

--=20
'peter'[:-1]@petertodd.org
00000000000000008aebcc3db3f73302ba290392eb783c509c5c7c4dd3971136

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQGrBAEBCACVBQJTII+tXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDA4YWViY2MzZGIzZjczMzAyYmEyOTAzOTJlYjc4M2M1MDlj
NWM3YzRkZDM5NzExMzYvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfvJ0Qf/Yp7zzBGsFzvnZ5eWldqHKWVe
2mslod6Gm2qknjEWMao+c++VIBgnx5G+P6GkXDaLnMafQ3yfLRmI6+EsQYKCavZF
tvoY2l2TB3vhW1Gu0MdKwgf84yHiPpMYIQA8e8sPq8FNBI4YUExZDnpRvPsesi3W
jylFlsEBqXpvt9dtxyh1rzmch7kyZ62bCBMs5SXK4ijDHQXocBThFoBoloIYcKBe
4wGo4xwNrCXJQM+OrOiCHlZTXhEuelbWj1aaHB2aUqOLUXRmCwoUOZ1rJpjhP8S/
TJcEE2jEeJGdDsAfKZE4vzuSgy+7nTdNvoblVNFAaC9Dl7irl8GJx51tHoTUpw==
=nllj
-----END PGP SIGNATURE-----

--KsGdsel6WgEHnImy--