public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "James O'Beirne" <james.obeirne@gmail.com>
To: Jim Posen <jim.posen@gmail.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] assumeutxo and UTXO snapshots
Date: Thu, 4 Apr 2019 10:36:53 -0400	[thread overview]
Message-ID: <CAPfvXfJz2_rpeN3mYAJg6XuYAPKJV_KM2R7pQm6zNzbX3qp+Kw@mail.gmail.com> (raw)
In-Reply-To: <CADZtCSi394PPwEJg3bcjLDE7jkuyFoEtcKPos4NQxBM+OJPv_Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

I recommend that anyone following this thread read through the recent IRC
exchange between Greg Maxwell and Luke Dashjr:
 http://www.erisian.com.au/bitcoin-core-dev/log-2019-04-04.html
<http://www.erisian.com.au/bitcoin-core-dev/log-2019-04-04.html>

The conversation starts on line 205 at 2019-04-04T02:54:50.

On Thu, Apr 4, 2019 at 2:38 AM Jim Posen via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> 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.
>>
>
> Anyone with enough knowledge of C++ to audit the entire the Bitcoin Core
> codebase is more than capable of running it with assumeutxo disabled and
> checking the hard-coded vale themself.
>
>> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 1911 bytes --]

  reply	other threads:[~2019-04-04 14:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 20:43 [bitcoin-dev] assumeutxo and UTXO snapshots 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
2019-04-04  5:59         ` Jim Posen
2019-04-04 14:36           ` James O'Beirne [this message]
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=CAPfvXfJz2_rpeN3mYAJg6XuYAPKJV_KM2R7pQm6zNzbX3qp+Kw@mail.gmail.com \
    --to=james.obeirne@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=jim.posen@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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