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: Sun, 29 Mar 2015 07:20:43 -0700
From: Peter Todd <pete@petertodd.org>
To: Brian Deery <brian@factom.org>
Message-ID: <20150329142043.GA7204@muck>
References: <CAFjbNjH01=TK1Xfy3W3FG6FO6yqBskPTeyBiVA5FMyR-auEtiQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V"
Content-Disposition: inline
In-Reply-To: <CAFjbNjH01=TK1Xfy3W3FG6FO6yqBskPTeyBiVA5FMyR-auEtiQ@mail.gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] My thoughts on the viability of the
 Factom token
Precedence: list


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

On Fri, Mar 20, 2015 at 12:46:18AM -0500, Brian Deery wrote:
> Greetings mailing list.
>=20
> Not sure that this content is 100% appropriate here, but Peter Todd
> invited me to post this for archival purposes.  The original thread
> has been removed from the search results, but is still up here:
> http://www.reddit.com/r/Bitcoin/comments/2z9k5p/factom_announces_launch_d=
ate_for_software_token/
>=20
>=20
> I have added more thoughts too.

Thanks.

You know, looking though your writeup, I think we're talking past each
other. I've found with a lot of other projects a good way to start is to
explicitly list what you think Factom *prevents* from happening. It is
after all security software - the most important thing it does is what
it prevents the attacker from doing. Be specific - you really need to
nail down exactly what kind of guarantees you're trying to get out of
the Factom system.

--=20
'peter'[:-1]@petertodd.org
0000000000000000064a6b620c22d89697757f4d81c3b839e50b03e2d3f8e168

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

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

iQGrBAEBCACVBQJVGAo4XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwNjRhNmI2MjBjMjJkODk2OTc3NTdmNGQ4MWMzYjgzOWU1
MGIwM2UyZDNmOGUxNjgvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udyP3gf/SJ48bAQxv08d6PHMVsoiwnLw
v24svd8qMMilUV1mvhj6QNabVChC6nSQTIKr7T1/vQB5TdIp60E6TBmWD3/3beg5
7E7acD8+b/fD+BE76Btv2a/dltuDKO58btHm7PCPSjJ1Yul1B8mq7IGGMk4rI7/B
2P5OGVb83z7MOtY9HJ6FtBfwsq5GrUMXSvauHO16aVWO6KXdZAVsh9Otd3UbE5nO
K8VzW8J5b/kJmjCvk9N6hm9ZMBlbLRCwC9la7COWveyAHkgYhmUyQ4hp1JzoXkkw
bBo/0DHvCjUq11YZZQt5SwWyafBeK5ePbAgpK94AAnu0xuFEi/zuD/GjfPO3Cw==
=DKOZ
-----END PGP SIGNATURE-----

--xHFwDpU9dbj6ez1V--