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
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
Return-Path: <samad.sajanlal@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9614E13D5
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Mar 2018 22:04:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-it0-f45.google.com (mail-it0-f45.google.com
[209.85.214.45])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1BF3F4CC
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Mar 2018 22:04:37 +0000 (UTC)
Received: by mail-it0-f45.google.com with SMTP id e195-v6so8801515ita.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Mar 2018 15:04:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=M7tGvZUOSgcclsET4GBpM2QlSWyek2y4oJMZJ2xPg4M=;
b=WMCRSAL1c/72Ex8SUZiT+onKkKnXTlSwquEnMUT4unyEkHjzz0vg7IGyl+qXTAPQTk
FE4dd/MPbY/3Ed+oz/g5grzW+73FfUUDyKL8Jl93fGsJEqMU0yRQ3zIZyjlpJ9adUFGO
T6foRT7wH7NuLaYIeC+NwJnjhbOt6fYbpN3/jssQBsPcW4bZxMq/NP/mLoCaTOZjXNYX
LkFX39ciOxQxBy3cdZGm6TLBfPj6X1MEEw/zqNmvs1eCW690zCfnLreqB2APz3QN3Au6
F5sc8YH8v+tR0U8CPrfio+doIzxQF5Mlk+YmF/7FYUOmtTdwztekqt68pbtGqczqXuS0
0GnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=M7tGvZUOSgcclsET4GBpM2QlSWyek2y4oJMZJ2xPg4M=;
b=fh6u2cKlj6y62iNaO4K61riPxpyyxWVsqEu6mSEyl0IMYFs3CiabTiO6uFVzLRzxuD
2y/S32QGIL6hS4VcswpNiEiNNbMxbkvHI/q/94xU6CxLYGCUsc+PM6miT6xrDdUNE/OA
FVdSSBzmADORbdtxQLWxWSypOnqFx3A53xKm2KZFlxgn1X5YDgg2kfHADTa+SeElSdTv
ny5u4dxfiC5lSN7zqeIxeVV0KH2dgIyi0SEdeNY3O1YJ0vOStBBBp/3WyN34XqibvTsb
G4sfDhmCJtHW6yjAnzHKNe1sqId6sSX/2DSPTVReLX7/EE1BFujr/huiduA8jW5uS3lG
cvdA==
X-Gm-Message-State: AElRT7GwG6qw60/HNczu028iNffMHiUzUa5zqDS+taM9BBHLQYUR9mhD
pC8pWhPSNaPAeGe9NJj9jJiHkAMjYXnJhSR5Hz1V7g==
X-Google-Smtp-Source: AG47ELtXMQWyboGZqfAWaLS44Qbx1euSQJKGeRkcMIvN/YvVO2+YOSUCCr0UBfWp/DhPgZgFXegnONPU+pBmGYVHa7k=
X-Received: by 2002:a24:ef46:: with SMTP id
i67-v6mr6377649ith.51.1521669876239;
Wed, 21 Mar 2018 15:04:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.140.147 with HTTP; Wed, 21 Mar 2018 15:04:35 -0700 (PDT)
From: Samad Sajanlal <samad.sajanlal@gmail.com>
Date: Wed, 21 Mar 2018 17:04:35 -0500
Message-ID: <CAAQZUuDEJeMFTxxJcgUEmTUQbxM_ZWkBD1k+UOvafsqbqj++Jg@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="0000000000007052490567f36057"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 22 Mar 2018 01:46:44 +0000
Subject: [bitcoin-dev] Soft Fork Activation & Enforcement w/o Signaling?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Wed, 21 Mar 2018 22:04:37 -0000
--0000000000007052490567f36057
Content-Type: text/plain; charset="UTF-8"
Is it possible to activate soft forks such as BIP65 and BIP66 without prior
signaling from miners? I noticed in chainparams.cpp that there are block
heights where the enforcement begins.
I understand this is already active on bitcoin. I'm working on a project
that is a clone of a clone of bitcoin, and we currently do not have BIP65
or BIP66 enforced - no signaling of these soft forks either (most of the
network is on a source code fork of bitcoin 0.9). This project does not and
never intends to attempt to replace bitcoin - we know that without bitcoin
our project could never exist, so we owe a great deal of gratitude to the
bitcoin developers.
If the entire network upgrades to the correct version of the software
(based on bitcoin 0.15), which includes the block height that has
enforcement, can we simply skip over the signaling and go straight into
activation/enforcement?
At this time we are lucky that our network is very small, so it is
reasonable to assume that the whole network will upgrade their clients
within a short window (~2 weeks). We would schedule the activation ~2
months out from when the client is released, just to ensure everyone has
time to upgrade.
We have been stuck on the 0.9 code branch and my goal is to bring it up to
0.15 at least, so that we can implement Segwit and other key features that
bitcoin has introduced. The 0.15 client currently works with regards to
sending and receiving transactions but the soft forks are not active. I
understand that activating them will segregate the 0.15 clients onto their
own fork, which is why I'd like to understand the repercussions of doing it
without any signaling beforehand. I also would prefer not to have to make
intermediate releases such as 0.10, 0.11.. etc to get the soft forks
activated.
Another related question - does the block version get bumped up
automatically at the time that a soft fork activates, or is there
additional stuff that I need to do within the code to ensure it bumps up at
the same time? From what I saw in the code it appears that it will bump up
automatically, but I would like some confirmation on that.
Regards,
Samad
--0000000000007052490567f36057
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"color:rgb(34,34,34);font-fa=
mily:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligat=
ures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;=
text-align:start;text-indent:0px;text-transform:none;white-space:normal;wor=
d-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initi=
al;text-decoration-color:initial"><div><div><div><div>Is it possible to act=
ivate soft forks such as BIP65 and BIP66 without prior signaling from miner=
s? I noticed in chainparams.cpp that there are block heights where the enfo=
rcement begins.<span>=C2=A0</span><br><br>I understand this is already acti=
ve on bitcoin. I'm working on a project that is a clone of a clone of b=
itcoin, and we currently do not have BIP65 or BIP66 enforced - no signaling=
of these soft forks either (most of the network is on a source code fork o=
f bitcoin 0.9). This project does not and never intends to attempt to repla=
ce bitcoin - we know that without bitcoin our project could never exist, so=
we owe a great deal of gratitude to the bitcoin developers.<br></div></div=
><br></div>If the entire network upgrades to the correct version of the sof=
tware (based on bitcoin 0.15), which includes the block height that has enf=
orcement, can we simply skip over the signaling and go straight into activa=
tion/enforcement?<br><br></div>At this time we are lucky that our network i=
s very small, so it is reasonable to assume that the whole network will upg=
rade their clients within a short window (~2 weeks). We would schedule the =
activation ~2 months out from when the client is released, just to ensure e=
veryone has time to upgrade.<br><br></div><span style=3D"color:rgb(34,34,34=
);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-vari=
ant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacin=
g:normal;text-align:start;text-indent:0px;text-transform:none;white-space:n=
ormal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;float:none;display:inline">We hav=
e been stuck on the 0.9 code branch and my goal is to bring it up to 0.15 a=
t least, so that we can implement Segwit and other key features that bitcoi=
n has introduced. The 0.15 client currently works with regards to sending a=
nd receiving transactions but the soft forks are not active. I understand t=
hat activating them will segregate the 0.15 clients onto their own fork, wh=
ich is why I'd like to understand the repercussions of doing it without=
any signaling beforehand. I also would prefer not to have to make intermed=
iate releases such as 0.10, 0.11.. etc to get the soft forks activated.</sp=
an><div><span style=3D"font-size:12.8px"><br></span></div><div><span style=
=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-=
style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-we=
ight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transf=
orm:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,2=
55);text-decoration-style:initial;text-decoration-color:initial">Another re=
lated question - does the block version get bumped up automatically at the =
time that a soft fork activates, or is there additional stuff that I need t=
o do within the code to ensure it bumps up at the same time? From what I sa=
w in the code it appears that it will bump up automatically, but I would li=
ke some confirmation on that.<br></span><div style=3D"color:rgb(34,34,34);f=
ont-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant=
-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:n=
ormal;text-align:start;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;text-decoration-style:initial;text-decoration-color:ini=
tial;background-color:rgb(255,255,255)"><br></div><div style=3D"color:rgb(3=
4,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;fo=
nt-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter=
-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-=
space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration=
-color:initial;background-color:rgb(255,255,255)">Regards,<br></div><div st=
yle=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;fo=
nt-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font=
-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;text-decoration-style:initi=
al;text-decoration-color:initial;background-color:rgb(255,255,255)">Samad</=
div><div class=3D"gmail-yj6qo" style=3D"color:rgb(34,34,34);font-family:ari=
al,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:nor=
mal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-=
decoration-color:initial"></div><br class=3D"gmail-Apple-interchange-newlin=
e">
</div></div><br></div>
--0000000000007052490567f36057--
|
