From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Cc: libbitcoin@lists.dyne.org
Subject: Re: [Bitcoin-development] On Rewriting Bitcoin (was Re: [Libbitcoin] Satoshi client: is a fork past 0.10 possible?)
Date: Sun, 15 Feb 2015 00:05:24 +0000 [thread overview]
Message-ID: <201502150005.25183.luke@dashjr.org> (raw)
In-Reply-To: <3D4F2E23-CADE-4FE7-B960-3F79815E868C@bitsofproof.com>
On Saturday, February 14, 2015 2:23:47 PM Tamas Blummer wrote:
> We have seen that the consensus critical code practically extends to
> Berkley DB limits or OpenSSL laxness, therefore it is inconceivable that a
> consensus library is not the same as Bitcoin Core, less its P2P service
> rules, wallet and RPC server.
You can describe 'A' from a group of A, B, C, D, E as "the group minus B, C,
D, E", sure - but I don't see how this is relevant?
UTXO storage is indeed consensus critical, as you say, but it is a lot simpler
to get right than the rest combined. Thus, the end goal is to have a
libbitcoinconsensus with "the rest", and a (as of yet named)
libbitcoincompleteconsensus that ties in the canonical UTXO storage. Ideally,
software should use the latter when it is available, but if there is a strong
reason to change UTXO storage, one can remain mostly-safe with just the
former. I'm not sure why this topic is of relevance, though...
Luke
next prev parent reply other threads:[~2015-02-15 0:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABm2gDpReRty6TdfMDssjF27XgC_SYs_U__SFBNdsYW24Mzh8w@mail.gmail.com>
[not found] ` <54CC0E1D.7030409@voskuil.org>
[not found] ` <CABm2gDqM6q24tPEBKSHbbVQu-mvfV37PNc4hD=VjyRHk2jujZw@mail.gmail.com>
[not found] ` <54D0414F.6030806@voskuil.org>
[not found] ` <CABm2gDo_sYjNWU6EEsKmOXt5uUu87Lj1oFzqio79MxSx2SYrNg@mail.gmail.com>
[not found] ` <54DE7601.4070509@voskuil.org>
[not found] ` <CABm2gDpt60B=Sf_2X9xt4fPH7x4fff7K4h36XfosHigV5tP+4Q@mail.gmail.com>
[not found] ` <54DF07A5.1060004@voskuil.org>
[not found] ` <CABm2gDoS+XOR7Ugt91kNWNdvwsb1_Zb-aO0sma_Xps2Sx-0N5g@mail.gmail.com>
[not found] ` <54DF2E80.5060506@voskuil.org>
2015-02-14 13:13 ` [Bitcoin-development] On Rewriting Bitcoin (was Re: [Libbitcoin] Satoshi client: is a fork past 0.10 possible?) Peter Todd
2015-02-14 14:23 ` Tamas Blummer
2015-02-14 19:04 ` Adam Back
2015-02-14 19:29 ` Bryan Bishop
2015-02-15 17:11 ` Peter Todd
2015-02-14 20:00 ` Jorge Timón
2015-02-15 0:05 ` Luke Dashjr [this message]
2015-02-15 17:02 ` Peter Todd
2015-02-15 17:13 ` Tamas Blummer
2015-02-15 17:21 ` Peter Todd
2015-02-15 21:48 ` joliver
2015-02-19 3:32 ` Troy Benjegerdes
2015-02-19 3:44 ` Peter Todd
2015-02-19 5:22 ` Tamas Blummer
2015-02-19 5:27 ` Tamas Blummer
2015-02-19 14:03 ` Bryan Bishop
2015-02-19 14:09 ` Tamas Blummer
2015-02-19 17:16 ` Jorge Timón
2015-02-19 17:30 ` Mike Hearn
2015-02-19 21:43 ` Sean Gilligan
2015-02-19 22:53 ` Angel Leon
2015-02-20 3:47 ` Jorge Timón
[not found] ` <54EE17DD.7050309@voskuil.org>
2015-03-25 8:04 ` Eric Voskuil
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=201502150005.25183.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=libbitcoin@lists.dyne.org \
/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