From: Peter Todd <pete@petertodd•org>
To: 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: Sun, 15 Feb 2015 12:21:09 -0500 [thread overview]
Message-ID: <20150215172108.GA27520@savin.petertodd.org> (raw)
In-Reply-To: <E0CB8E24-C67D-48B1-8D9F-2B71BAF13446@bitsofproof.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Sun, Feb 15, 2015 at 06:13:06PM +0100, Tamas Blummer wrote:
>
> On Feb 15, 2015, at 6:02 PM, Peter Todd <pete@petertodd•org> wrote:
> > Yes you are dicking around.
>
> I thought I was clear, that I am using Bitcoin Core as border router talking to its P2P interface.
Ah, sorry, that wasn't clear to me.
> The reimplementation of consensus code helped me to deeply understand the protocol, aids debugging
> and now comes handy to create a side chain.
Indeed, which is why I've done a lot of work on a reimplementation of
the Bitcoin scripting system as well:
https://github.com/petertodd/python-bitcoinlib/blob/master/bitcoin/core/scripteval.py
Which has this cheery warning at the top:
"""Script evaluation
Be warned that there are highly likely to be consensus bugs in this
code; it is unlikely to match Satoshi Bitcoin exactly. Think carefully
before using this module.
"""
I'll be adding a FFI interface to libconsensus in the future... and I
probably should make that warning scarier...
--
'peter'[:-1]@petertodd.org
000000000000000000ffb7a576b7aa5236c53f51ec07ccf174067beed3398056
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-02-15 17:21 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 [this message]
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=20150215172108.GA27520@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--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