From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
Dave Scotese <dscotese@litmocracy•com>
Subject: Re: [bitcoin-dev] assumeutxo and UTXO snapshots
Date: Thu, 4 Apr 2019 03:01:00 +0000 [thread overview]
Message-ID: <201904040301.01074.luke@dashjr.org> (raw)
In-Reply-To: <CAGLBAhf1NZfT9TunhHAb==mFTfaAacjekQh6Pqn4yBS+90Zw6A@mail.gmail.com>
On Wednesday 03 April 2019 21:39:32 Dave Scotese via bitcoin-dev wrote:
> Luke's comment that it could "lead to users trusting third parties (like
> developers) way too much" is pertinent too, but I think an honest abatement
> of that concern is impossible without teaching everyone C++.
Learning C++ is something within everyone's capability. Even people who do not
wish to learn it can hire someone to perform review for them.
> "Developers"
> as an open group (anyone can fork the github repo, find a problem, and make
> an issue) deserve the trust we put in them, and that's because they're
> accountable (any such error found in the repo will have been put there by
> someone).
No, we are not. We explicitly disclaim any warranty, and do not want your
trust.
> The same thing goes for making it possible to download (*not
> just the compiled software*, but) the entire UTXO Set if a commitment of it
> is hardcoded into the software, as James suggests.
Verifying a UTXO set commitment is impossible short of a real IBD. It's not
even comparable.
> We all trust
> "developers" like that, and it's okay.
No, it isn't okay. There are plenty of fiat options if you want a trust-based
currency. Bitcoin is supposed to be something more than that.
Luke
next prev parent reply other threads:[~2019-04-04 3:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 20:43 James O'Beirne
2019-04-03 6:37 ` Jonas Schnelli
2019-04-03 15:39 ` Ethan Scruples
2019-04-03 21:39 ` Dave Scotese
2019-04-04 3:01 ` Luke Dashjr [this message]
2019-04-04 5:59 ` Jim Posen
2019-04-04 14:36 ` James O'Beirne
2019-04-13 19:09 ` Peter Todd
2019-04-15 0:44 ` Dave Scotese
2019-04-04 2:48 ` Luke Dashjr
2019-04-04 3:04 ` Ethan Scruples
2019-04-03 19:51 ` James O'Beirne
2019-04-03 9:55 ` Luke Dashjr
2019-04-03 23:03 ` Jim Posen
2019-04-14 13:16 ` Omar Shibli
2019-04-23 14:17 ` James O'Beirne
[not found] <mailman.2593.1554248572.29810.bitcoin-dev@lists.linuxfoundation.org>
2019-04-03 7:51 ` Nicolas Dorier
2019-04-04 10:27 ` Kulpreet Singh
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=201904040301.01074.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dscotese@litmocracy$(echo .)com \
/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