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
|
Return-Path: <btcdrak@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id BBCCF279
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 8 Jan 2017 06:51:13 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f171.google.com (mail-yw0-f171.google.com
[209.85.161.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3FC3C10A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 8 Jan 2017 06:51:13 +0000 (UTC)
Received: by mail-yw0-f171.google.com with SMTP id v81so300800674ywb.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 07 Jan 2017 22:51:13 -0800 (PST)
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=WrlqX7K+i/ol6hGw4j6ENXXuPrRCa1CCYOdf2WYYZMw=;
b=joYemsFcToUrNgkvcru5W+2gXJUWwSBWqF2moDCa2jSmYhs3BcBijy/pzpoF/Q5E4B
u7oY0tZ4RfMCxZ4SnSxCZMh5qis7b2Tcwi3Omr+zwjiXrhh0RpGtfYACqVJffc9V+FPR
FPjaYhHEmT1R864pve5zi+5heE18pBxTx4PwBh2Vc+4bTcYsgjL3i94FERGY9xFr5PR8
4eBG4UGXIPjqRwBmanwh7YS4jl08OucqnUPwn9jn3b+17VfiCnAaqRkum+YHy/QDbQcG
DFOscaXfVIzp9zWN1NNRLAivB+SHHUR2m3ZM4i6QthNjvI0GPgatBkj90KyQtO5U4tGp
7dTg==
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=WrlqX7K+i/ol6hGw4j6ENXXuPrRCa1CCYOdf2WYYZMw=;
b=YHrm564Znv9i++CTz3ondyWOZoxCaIPEy4JLOIcLuL37A9JDn+rVd4y/q9mW++9pJt
pvKO6F67Zs0zoUpBVqokQPk/DUaXt4LlZiplqTxpubYg++V4vmECRFJWNJqq/hFa/cx+
kZ9i31D4DUFePJH+vLQulx7rDKHXFPdJAEAhvgHK1L8SbtGWl86ztyQRC/JBAxFqJDjh
wkrx92bWHNLyot10aoy7w+a+jYThRC4+0qVHg/TlLpxjkOoOqV/1Lsn7EmGe2eXTHAgX
NokKRHZCK7G46ZUGvjzn3OVumwRfuu7cldVvKKH+Vb3vb0nDlgMNrFP1gDaTZPoa/g2C
d6Tw==
X-Gm-Message-State: AIkVDXIOtYhBKxbdR6vyA7FqdvhEzzaTfSHX70QwaoXizFm1jlrHlfquk7mbEi4znWSlN9R6mPQ3Blyr8zD2ag==
X-Received: by 10.129.169.132 with SMTP id g126mr82466704ywh.92.1483858272357;
Sat, 07 Jan 2017 22:51:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.161.70 with HTTP; Sat, 7 Jan 2017 22:50:52 -0800 (PST)
From: Btc Drak <btcdrak@gmail.com>
Date: Sun, 8 Jan 2017 06:50:52 +0000
Message-ID: <CADJgMztS7Rd2MS_1nLcx-Sk_towzKD21_Kb89COBjYEuhLHOTQ@mail.gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM,
RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sun, 08 Jan 2017 06:55:32 +0000
Subject: [bitcoin-dev] Announcements on bitcoin-dev
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: Sun, 08 Jan 2017 06:51:13 -0000
The purpose of this list is Bitcoin protocol discussion of all kinds,
including consensus rules that require hard and soft forks and there
have been many discussions about both. There is also a clear technical
process for proposing, discussing and peer reviewing consensus rule
changes via the BIPs process which this list has traditionally played
a large role. BIP specifications allow community wide coordination
across multiple implementations.
Since the recent thread announcing a new version of Bitcoin Classic,
many people have complained on and off-list that is should not be
allowed on the bitcoin-dev mailing list because it is not consensus
compatible nor is it a change which has been arrived at through wide
community consensus. There isn't even a formal specification that
other implementations could follow if they wanted to. The general
feeling seems to be that announcements for consensus compatible
implementations is ok on this list. If there is ever community wide
consensus for a hard fork, then that too would be ok since there would
be consensus.
This list does strive to be somewhat high signal to noise ratio where
possible and we need to be clear about the list remit. So let's be
clear, announcing/advertising software that is consensus incompatible
is off-topic, however, discussion of hard forks, peer review etc has
always been, and remains, on topic.
I've copied the current list remit below for completeness. General
discussions should be directed at bitcoin-discuss, where as actual
protocol development discussion belongs on bitcoin-dev.
Bitcoin development and protocol discussion.
This list is lightly moderated.
- No offensive posts, no personal attacks.
- Posts must concern development of bitcoin protocol.
- Posts should be technical or academic in nature.
- Generally encouraged: patches, notification of pull requests, BIP
proposals, academic paper announcements. And discussions that follow.
- Generally discouraged: shower thoughts, wild speculation, jokes,
+1s, non-technical bitcoin issues, rehashing settled topics without
new data, moderation concerns.
- Detailed patch discussion generally better on a GitHub PR.
- Meta-discussion is better on bitcoin-discuss
(https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-discuss)
Thanks
|
