1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
Return-Path: <monarch@cock.li>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 1013AFE3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 16:51:56 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from cock.li (cock.li [176.9.0.140])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9EB93261
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 16:51:55 +0000 (UTC)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 01 Sep 2015 16:51:54 +0000
From: Monarch <monarch@cock.li>
To: bitcoin-dev@lists.linuxfoundation.org
In-Reply-To: <55E5CB5C.2020405@conformal.com>
References: "\"<602b978abcedd92fbed85f305d9d7bfe@cock.li> <55E4B8C9.5030606@openbitcoinprivacyproject.org> <e786da226b8e9cfaad335454b299ffd5@cock.li>"
<CAJfRnm4kwHkBLUUOmfzViUwsdAf3LYSTruvHw9+-RbgxSMHLRg@mail.gmail.com>"
<5A3D7824-F1E3-421B-A32A-0EF21DD215BD@gmx.com>
<5b7c2ba6e785e59595c2ee9a4596f097@cock.li>
<55E5CB5C.2020405@conformal.com>
Message-ID: <67820b46cdcb549aac36b9496b19b6b0@cock.li>
X-Sender: monarch@cock.li
User-Agent: Roundcube Webmail/0.9.5
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Your Gmaxwell exchange
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 16:51:56 -0000
On 2015-09-01 15:59, Dave Collins via bitcoin-dev wrote:
> I'd be interested to know about these supposed btcd mainnet forks that
> have occurred due to a consensus failure since it came out of alpha.
> I'll go ahead and save you some research time - there hasn't been one.
> I'm not claiming there will never be one as that would be just as
> foolish as claiming Bitcoin Core won't have any more either.
>
For the purposes of the conversation this was only brought up to re-
enforce my claim that this is outrageously difficult software
development, irrespective of the quality of the code being produced in
alternate implementations. Sorry if that came across as an attack
against your software in particular, it wasn't intended.
> On the other hand, Bitcoin Core has had actual forks on mainnet during
> the same period. I'm not casting stones at Bitcoin Core here, because
> as I've said many times, none of us are perfect. No matter how careful
> everyone is, it is bound to happen from time to time.
>
The point I was trying to make is that this is simply a hard
development situation to be working in, we don't know what behavior is
inferred by the use of CPP and even more so OpenSSL (as the DER
encoding consensus failure made abundantly clear). There's almost
certainly more problems lying around given how generally dusty a lot
of the transaction environment is, it's very easy to get off the
beaten track with Bitcoin script.
|
