From: Peter Todd <pete@petertodd•org>
To: Troy Benjegerdes <hozer@hozed•org>,
Tamas Blummer <tamas@bitsofproof•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] On Rewriting Bitcoin (was Re: [Libbitcoin] Satoshi client: is a fork past 0.10 possible?)
Date: Thu, 19 Feb 2015 03:44:34 +0000 [thread overview]
Message-ID: <065C5F2E-FC1D-4994-A39A-9125D663FC71@petertodd.org> (raw)
In-Reply-To: <20150219033205.GS14804@nl.grid.coop>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 18 February 2015 22:32:05 GMT-05:00, Troy Benjegerdes <hozer@hozed•org> wrote:
>The work that Tamas did re-implementing is probably one of the most
>valuable
>things he ever did.
...in the same way going to university may be one of the more valuable things you ever do. But using the code resulting from that process over Satoshi Bitcoin/libconsensus is foolish.
>It would significantly improve the quality of the consensus code if
>this
>community would start treating it as a buggy & poorly defined
>proof-of-concept
>that just happens to actually run, rather than some holy scripture upon
>which
>we must never question (or change)
I suggest you actually look at the git commit history for the consensus-critical part of the Bitcoin Core codebase - so much work cleaning it up and refactoring has been done for v0.10.0/libconsensus that I think we're risking the introduction of a consensus bug unnecessarily and should slow down a little.
"holy scripture" it ain't.
>I'm impressed by the secp256k1 work, and other modularity efforts, but
>at
>some point main.cpp needs to get untangled, and have some critical
>review
>if bitcoin wants to remain relevant.
Again, this is exactly what people are working towards, at a speed that if anything is probably a bit too rapid.
-----BEGIN PGP SIGNATURE-----
iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJU5Vwc
AAoJEMCF8hzn9Lnco2EH/3bXwUTJ9iVLfYH0d/nvSXmt+C0Mpj5YFYr1h1vJv/3M
e/By1ORRdre9fdJjgMmr3pj9lIiZfd/qEKEnrmULqBsoSd/5EmMjFB2gpZmQ1xyM
ndUyy56S2TFr//3hpJukvuG01X6q+GRGymlpk+fYfNlna3IjpARUabmlB9dKKRPI
/XfyfpYyZh9G6DLsRg6+5BgKeW9OFRFm9aQY/yHiDgxpffIvYJ9QyOVm5vjtMgBQ
bs0P7yuCUJ06xdSrYK1ylTcEbFyVIXa5w+AYQRHfx5aw7fZkD7q5pmwv8mWJfy8n
IroSkmd1Erk0L3e+wJtAZn8S/6094IJ3v+2NajEC2hQ=
=MfY/
next prev parent reply other threads:[~2015-02-19 3:45 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 ` 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
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 [this message]
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=065C5F2E-FC1D-4994-A39A-9125D663FC71@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=hozer@hozed$(echo .)org \
--cc=tamas@bitsofproof$(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