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
|
Return-Path: <luke@dashjr.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id BD4FDE5E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 8 Mar 2016 17:19:30 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id CBF44141
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 8 Mar 2016 17:19:29 +0000 (UTC)
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:61b6:56a6:b03d:28d6])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id B196938A2C18;
Tue, 8 Mar 2016 17:19:21 +0000 (UTC)
X-Hashcash: 1:25:160308:bitcoin-dev@lists.linuxfoundation.org::dTAeGLUn0jkuymLN:LdX5
X-Hashcash: 1:25:160308:g.andrew.stone@gmail.com::T2/IToi2ghThYWJe:q0Zs
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org,
"G. Andrew Stone" <g.andrew.stone@gmail.com>
Date: Tue, 8 Mar 2016 17:19:19 +0000
User-Agent: KMail/1.13.7 (Linux/4.1.18-gentoo; KDE/4.14.8; x86_64; ; )
References: <CAHUwRvuR9qtYc+rVh1yPbQoESxm4m0r6a+Fd6VF=FuT0vom_HQ@mail.gmail.com>
<CALcNmJwY=pQuRpnb-MJ1QiME3mPUSe2KmHD7XykhX08yku9mhQ@mail.gmail.com>
<CAHUwRvv_UMoRhcwy7u2XLz19q3aKNfHXyTNbfaSUsEapFnH2kg@mail.gmail.com>
In-Reply-To: <CAHUwRvv_UMoRhcwy7u2XLz19q3aKNfHXyTNbfaSUsEapFnH2kg@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201603081719.20662.luke@dashjr.org>
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,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
X-Mailman-Approved-At: Tue, 08 Mar 2016 17:21:23 +0000
Subject: Re: [bitcoin-dev] Services bit for xthin blocks
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, 08 Mar 2016 17:19:30 -0000
X-List-Received-Date: Tue, 08 Mar 2016 17:19:30 -0000
On Tuesday, March 08, 2016 2:35:21 AM G. Andrew Stone via bitcoin-dev wrote:
> Not an unreasonable request, however while I personally respect the many
> great accomplishments of individual engineers loosely affiliated with
> "Core", Bitcoin Unlimited has our own process for documentation and
> discussion on an uncensored forum located here:
> https://bitco.in/forum/threads/buip010-passed-xtreme-thinblocks.774/. We
> would love to have any interested engineer join us there with ideas and
> criticisms.
Bitcoin-dev and the BIP process are not affiliated with Core at all. In fact,
the BIP process was created by Amir Taaki, who was a libbitcoin developer
(libbitcoin is not Core).
I encourage Bitcoin Unlimited to use the BIP process for cross-implementation
standards like this, as do other implementations, so that you can benefit from
peer review from the wider Bitcoin development community, as well as have a
common repository for these standards.
Many BIPs are discussed on reddit in addition to this mailing list, and you
would certainly remain free to discuss your own proposals on any forum you
like - it isn't restricted to only this mailing list.
If this is of interest, I will be happy to try to go over and assign BIP
numbers to the current (15?) BUIPs assuming they meet the basic requirements
for such assignment (see BIP 1:
https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki). Is there an
easy way to get links to each of the BUIPs? I couldn't find BUIP 1 at all, for
example.
Thanks,
Luke
|
