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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
Return-Path: <laanwj@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 1E0801D73
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 1 Oct 2015 10:15:49 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com
[209.85.212.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8F4B0259
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 1 Oct 2015 10:15:48 +0000 (UTC)
Received: by wicge5 with SMTP id ge5so22233738wic.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 01 Oct 2015 03:15:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=date:from:to:cc:subject:message-id:references:mime-version
:content-type:content-disposition:in-reply-to;
bh=39G0fMV4mw3QSQtoN7Rb3KbV83Wn/dEfyft7cS1WWqc=;
b=vq/QDWfkHK2f9VlIBpxrogp85e+VHo5qyXKGVsM57l/VkFCvgMKnI+yxISIKWp8lyL
GLa5Nqtjt5ap+8RfEzy9o1m8lTWSzK46NEuDWsrkps2mMiKBRDTFHU4zk8E+5ErT+7wu
6+8boCPx9kIfKy4HSGkBsZLtQS1cG97FeGKYk7DjympxYfUzr5V2PI+d+BFThgrgN5e8
saqdqIOS0f81MmBxYqrhYlRdS1ywfxQopN1YmCXhSpGc8GTJoA0MaOVOmO6jC8hVQoQa
C7e72K8RTQjlhxg4Y2xVX/95seZA858f6QssjdHDgQMTPKHDrDWzjV05/yPsttafKQs2
YJ+g==
X-Received: by 10.180.8.132 with SMTP id r4mr2611701wia.70.1443694547143;
Thu, 01 Oct 2015 03:15:47 -0700 (PDT)
Received: from amethyst.visucore.com (dhcp-089-098-228-253.chello.nl.
[89.98.228.253])
by smtp.gmail.com with ESMTPSA id h6sm2393658wiy.14.2015.10.01.03.15.46
(version=TLS1_2 cipher=AES128-SHA256 bits=128/128);
Thu, 01 Oct 2015 03:15:46 -0700 (PDT)
Date: Thu, 1 Oct 2015 12:15:45 +0200
From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: Marcel Jamin <marcel@jamin.net>
Message-ID: <20151001101544.GA10901@amethyst.visucore.com>
References: <20150924112555.GA21355@amethyst.visucore.com>
<201509301757.44035.luke@dashjr.org>
<20151001085058.GA10010@amethyst.visucore.com>
<CAAUq486=TisNp0MbFjWYdCsyVX-qx5dV_KKZuNR7Jp63KNWeiQ@mail.gmail.com>
<CADJgMzuDPoQacdrH7n_ajwuYLMZ4-Z19KZSa=w=rLhmOkJhfQg@mail.gmail.com>
<CAAUq484+g89yD+s7iR_mGWPM3TTN7V6-EPb1ig=P1BKfcbztPg@mail.gmail.com>
<CAAUq4861Wd2c42gVy7SoW9414R8RGY+Yzp7rDtzagrwQewnFWg@mail.gmail.com>
<20151001095654.GB10010@amethyst.visucore.com>
<CAAUq486EXSJ1ri-3nWMt9vWhoajLp+LkWTV_-ZvU_FE+qfqcpA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAAUq486EXSJ1ri-3nWMt9vWhoajLp+LkWTV_-ZvU_FE+qfqcpA@mail.gmail.com>
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fwd: Bitcoin Core 0.12.0 release schedule
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: Thu, 01 Oct 2015 10:15:49 -0000
On Thu, Oct 01, 2015 at 12:10:45PM +0200, Marcel Jamin wrote:
> I think the question has already been answered for you by the companies
> that build on top of it, the investments being made and the $3.5 billion
> market cap. The 1.0.0 tag is probably long overdue.
May I remind you that by far, most of that investment is not in the Bitcoin Core software.
It is made to things building on top of the network/protocol, under the assumption that nothing really stupid will happen and the network will not go down etc.
This implies a level of trust in the node software to maintain consensus, but doesn't necessarily mean that all rough corners have been dealt with regarding implementation.
(but this is exactly the kind of argument I'm trying to avoid getting pulled into)
> Then you could start using the version as a signaling mechanism.
We certainly could, it is a decision to not to.
> Yeah, probably not a very important topic right now.
Exactly.
Wladimir
>
>
>
> 2015-10-01 11:56 GMT+02:00 Wladimir J. van der Laan <laanwj@gmail.com>:
>
> > On Thu, Oct 01, 2015 at 11:41:25AM +0200, Marcel Jamin wrote:
> > > I guess the question then becomes why bitcoin still is <1.0.0
> >
> > I'll interpret the question as "why is the Bitcoin Core software still
> > <1.0.0". Bitcoin the currency doesn't have a version, the block/transaction
> > versions are at v3/v1 respectively, and the highest network protocol
> > version is 70011.
> >
> > Mostly because we don't use the numbers as a signaling mechanism. They
> > just count up, every half year.
> >
> > Otherwise, one'd have to ask hard questions like 'is the software mature
> > enough to be called 1.0.0', which would lead to long arguments, all of
> > which would eventually lead to nothing more than potentially increasing a
> > number. We're horribly stressed-out as is.
> >
> > Wladimir
> >
|
