From: Eric Lombrozo <elombrozo@gmail•com>
To: Justus Ranvier <justus@openbitcoinprivacyproject•org>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Thoughts on Forks, Scalability, and other Bitcoin inconveniences.
Date: Sun, 5 Jul 2015 14:08:12 -0700 [thread overview]
Message-ID: <CABr1YTcOGkQOr0UMTZMQvMZyuHF63n6eKEmg0uz-j5OwnJ37sA@mail.gmail.com> (raw)
In-Reply-To: <55999C27.4070604@openbitcoinprivacyproject.org>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
I was saying that somewhat tongue-in-cheek...sorry that didn't come through
in the text.
On Jul 5, 2015 2:05 PM, "Justus Ranvier" <
justus@openbitcoinprivacyproject•org> wrote:
> On 07/05/2015 03:53 PM, Eric Lombrozo wrote:
> > Perhaps I didn't write that so well if I gave that impression. Perhaps
> > taking a look at some of my work in this space would make you think
> > otherwise. (yes, I've implemented an entire SPV stack from scratch...look
> > it up.)
>
> I get concerned when I hear statement like "the raison d'etre of bitcoin
> is trustlessness" because it implies that Bitcoin promises infinite
> security, which has never been the case.
>
> I don't think we can meaningfully discuss Bitcoin security issues if
> every proposal is compared to a straw standard of perfection which is
> achievable. When everybody expects infinite security then the perfect
> turns into the enemy of the good (and the achievable).
>
> --
> Justus Ranvier
> Open Bitcoin Privacy Project
> http://www.openbitcoinprivacyproject.org/
> justus@openbitcoinprivacyproject•org
> E7AD 8215 8497 3673 6D9E 61C4 2A5F DA70 EAD9 E623
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 2002 bytes --]
prev parent reply other threads:[~2015-07-05 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABr1YTf72fdQmTDEHAWVKqvTCLSpJZyiiw4g3ifrY8x5RZ=shQ@mail.gmail.com>
[not found] ` <CABr1YTfwcOQuNyqO57=jdghTnqt56u6pBvK6+dWbED-4OMh+Ug@mail.gmail.com>
[not found] ` <CABr1YTfEEXoQJ4SUtrUki9_WetWbGV7TEB+3usJGQqu-P55kSA@mail.gmail.com>
2015-07-05 18:50 ` Eric Lombrozo
2015-07-05 19:55 ` Eric Lombrozo
2015-07-05 20:33 ` Justus Ranvier
2015-07-05 20:53 ` Eric Lombrozo
2015-07-05 21:05 ` Justus Ranvier
2015-07-05 21:08 ` Eric Lombrozo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABr1YTcOGkQOr0UMTZMQvMZyuHF63n6eKEmg0uz-j5OwnJ37sA@mail.gmail.com \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=justus@openbitcoinprivacyproject$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox