Date: Wed, 30 Dec 2015 06:28:37 -0800
From: Peter Todd <pete@petertodd.org>
To: Martijn Meijering <martijn.meijering@mevs.nl>
Message-ID: <20151230142836.GA19507@muck>
References: <CAODYVYf764XafVsbnVnYgsYZtWwKu4Q3cwzL1B=GVWUFjZ5TWg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl"
Content-Disposition: inline
In-Reply-To: <CAODYVYf764XafVsbnVnYgsYZtWwKu4Q3cwzL1B=GVWUFjZ5TWg@mail.gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] An implementation of BIP102 as a softfork.
Precedence: list


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

On Wed, Dec 30, 2015 at 12:16:22PM +0100, Martijn Meijering via bitcoin-dev=
 wrote:
> That looks very interesting. But is effectively blocking old clients from
> seeing transactions really safe? After all, such transactions are still
> confirmed on the new chain. A person might try to send a similar
> transaction several times, perhaps with increasing fees in an attempt to
> get it to confirm and end up paying someone several times.

It's very dangerous to simply send multiple transactions in such a way
that they don't double-spend each other; you have no good way of knowing
for sure that you're seeing the longest block chain with software alone.

Competently designed software with fee-bumping wouldn't allow that
mistake to be made; the UX should make it clear that txs sent are still
pending until confirmed or clearly double-spent.

> Maybe we could require the tx version number to be increased as well so
> transactions sent from old clients would never confirm? Perhaps your code
> already includes this idea, I need to look at it more closely.

That can mess up pre-signed transations, e.g. refunds.

--=20
'peter'[:-1]@petertodd.org
00000000000000000831fc2554d9370aeba2701fff09980123d24a615eee7416

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

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

iQGrBAEBCACVBQJWg+oSXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwODMxZmMyNTU0ZDkzNzBhZWJhMjcwMWZmZjA5OTgwMTIz
ZDI0YTYxNWVlZTc0MTYvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udwQ6Af7B3XZNeyUtgslfaIkhu59S746
mO5ddXb+g1xiMX9nX+ol+1Xj83BdLCAa+JoFq/gYzvllrDGMNYnttDQ2MGF3G7z4
pE1C7TDoBUJ++CKWa5o1B4swqHCEQVFy7yUB5rWwFr8yEJTApxFXorjqoU89lhDK
rMVrbnTLjQ88Dc61U+02W0I3EHdQah5/H3tbbbKGBiFQbfCM8fuxW/+FXIhCMvdX
c+ccGkMQOK2JC/pIFzFbecNlI+kkL0gDFcWD/vZoKcL/vnyJ/Urhe4fuORmAsmWM
SY8K6PIWTAZf5MN6NVx266KHmjOMFKTr3UWKxp7ymTuRVugtf0srw4UYIwgQEA==
=UFiT
-----END PGP SIGNATURE-----

--BXVAT5kNtrzKuDFl--