Date: Tue, 16 May 2017 08:23:53 -0400
From: Peter Todd <pete@petertodd.org>
To: Alex Mizrahi <alex.mizrahi@gmail.com>
Message-ID: <20170516122353.GA5808@fedora-23-dvm>
References: <20170223011147.GB905@savin.petertodd.org>
	<CAE28kUTxc4KPvijiaJQ6M=LDPf_Du1pFdehfTtXtqs0hOtyWTw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/"
Content-Disposition: inline
In-Reply-To: <CAE28kUTxc4KPvijiaJQ6M=LDPf_Du1pFdehfTtXtqs0hOtyWTw@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] TXO commitments do not need a soft-fork to be
 useful
Precedence: list


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

On Tue, May 16, 2017 at 03:15:17PM +0300, Alex Mizrahi via bitcoin-dev wrot=
e:
> > Something I've recently realised is that TXO commitments do not need to=
 be
> > implemented as a consensus protocol change to be useful.
>=20
>=20
> You're slow, Peter. I figured this out back in 2013:
>=20
> https://bitcointalk.org/index.php?topic=3D153662.10

Lol, good job! And you even figured out that lovely "distributed file syste=
m"
explanation first.

Though, it does look like I'm still the person who made it 100% *clear* the
first time - you're explanation is easy to read the wrong way, particularly
when you say:

"Next time I will teach you how to implement a blockchain-based cryptocurre=
ncy
in such a way that new miners can start mining right away without downloadi=
ng
whole blockchain, stay tuned..."

After all, at the time UTXO commitments had been already discussed. Also,
talking about a DHT in relation to this stuff probably made the explanation=
 get
missed by some people.


Unfortunately, I think this is a good example of how important coming up wi=
th
good explanations and analogies is. :/

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

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

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

iQEcBAEBCAAGBQJZGu9WAAoJECSBQD2l8JH7J3wH/jgwJM0Wf2fpfLPhPMY8VpQt
MxfkUNrUgTyYwbibY1mbZ8lJ955d20MjFx6LrRhmeldsIDlLlhawHzdO63smUinu
H0bz2RMoCfPCLXAibrbiIig+tnF5JySKpPy6piXx30YhI+lMqrLAs13rSy4J6wgV
kCCo7j2BjQBCLdgDx1dHSdON93J+bi5lvdh7v+JMEuXxLzN1tjhXcNh21ra3aWaY
bdlh+OC9iPnMz1GZBWoews9vunFvkvYd4N2jQ7u2ttUcDZ+jlgxHpexu/VyXCI0O
/t73EAuUBYuTZMzxT/cQf24RHNPdUQZ6AxrwrPHdUYDPMCFlWTuQTbcI6McYIfU=
=UG19
-----END PGP SIGNATURE-----

--pWyiEgJYm5f9v55/--