Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.102 as permitted sender)
	client-ip=62.13.148.102; envelope-from=pete@petertodd.org;
	helo=outmail148102.authsmtp.net; 
Date: Sun, 21 Dec 2014 13:51:26 -0500
From: Peter Todd <pete@petertodd.org>
To: Adam Back <adam@cypherspace.org>
Message-ID: <20141221185126.GC18711@savin.petertodd.org>
References: <CALqxMTFK_sxdFjVi0qAC0JMdXa=tVBBNp0VrveRUfwa3b1UYhw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="4ZLFUWh1odzi/v6L"
Content-Disposition: inline
In-Reply-To: <CALqxMTFK_sxdFjVi0qAC0JMdXa=tVBBNp0VrveRUfwa3b1UYhw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] one-show signatures (Re: The relationship
 between Proof-of-Publication and Anti-Replay Oracles)
Precedence: list


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

On Sun, Dec 21, 2014 at 06:10:47PM +0000, Adam Back wrote:
> Yes you could for example define a new rule that two signatures
> (double-spend) authorises something - eg miners to take funds. (And
> this would work with existing ECDSA addresses & unrestricted R-value
> choices).
>=20
> I wasnt really making a point other than an aside that it maybe is
> sort-of possible to do with math what you said was not possible where
> you said "This [preventing signing more than one message] is
> impossible to implement with math alone".

Introducing a bunch of clever ECDSA math doesn't change the fact that
the clever math isn't what is preventing double-spending, clever
economics is. Just like Bitcoin itself.

No sense getting people potentially confused by a bunch of complex
equations that aren't relevant to the more fundemental and much more
important principle that math alone can't prevent double-spending.

--=20
'peter'[:-1]@petertodd.org
00000000000000001bc21486eb6e305efc085daa6b9acd37305feba64327342e

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

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

iQGrBAEBCACVBQJUlxaqXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwOGJjY2JlNGQyYjgxN2M4MThhNzJjNDBjMzQ3NjFmZGZm
OTcwNWVmOWY4ZGVhNTEvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfsvwgf/QUONliB1i50Bl4DIpDfath8n
v4KaiOF8gWQacG1Xnp6VCEcF6BG/czcnzldfxOIwidOc4J25QWgLOZATnhWF4blY
pOCKLgtjjxvjv1mH+EFmFzdEhKZ3Uc7cnLhB2Oee/RVEy2XTJXU4qO7t6wtZvL5I
R8ugwNHrXJJNl8aX7PvqhpMJsAl0/+hEbdAaAil/ac2lsT04BNs/bt53XWaGbMvn
vZYt9SHmaZSoC91IoQp7Ji/2XPIhQMm2rg8qQir0gWe3fc87ntakHYVYOzqjNf5g
H7l+Vhf5DN44hv451xDKa1LNG//KoG86firOkmlTx79rZzvdHvdChNpIP4WHqw==
=Aa0k
-----END PGP SIGNATURE-----

--4ZLFUWh1odzi/v6L--