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
|
Return-Path: <kalle@rosenbaum.se>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id CC9AE8A8
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 23 Jul 2015 21:36:47 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com
[209.85.220.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1CB011A1
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 23 Jul 2015 21:36:47 +0000 (UTC)
Received: by qkbm65 with SMTP id m65so3588249qkb.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 23 Jul 2015 14:36:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=JLsmLjxeb0L7EZ2INwCrbzkdLF4eXSH1JkC2ZzhPR/o=;
b=FeNJzNItFdW3Zx6P0jqTfJBj4BH+k8rrY+46n9qvbwDn19STxOT/O0oJTJVobuGoQf
Oftfed64sFxtQrSuaUk0zC0TiuAJXbnHyMZ66ppovuc/37gx6CQhMLU50dyY9TxNMFz7
3vVTNJdGgRMRiSXDXAGWP7Lk58jqwLrRdCw5gOc5Laa8b0wWTU2o0a7hjfk5vYJcR9hn
1vtyR4kthYz7GDXFLgfpx9GRePjr19tu4HPCXaeHXc3ulPtGQ748qTfEU5PfMv0u3NSp
kKYYWUj5/uAY1fUbPvCZV7GGdfvQOD6CfgFXHCQpVhV1uO9EQgdGqEC/cTQY6ehENro5
QYMw==
X-Gm-Message-State: ALoCoQmOl1t7BIqgl8P8DDVg37IV5/Q6RQraC/tWle19RtxwiHnBIFP33E9S1M702YyW7zO4mdMt
MIME-Version: 1.0
X-Received: by 10.140.37.50 with SMTP id q47mr15232500qgq.22.1437687406391;
Thu, 23 Jul 2015 14:36:46 -0700 (PDT)
Received: by 10.96.127.227 with HTTP; Thu, 23 Jul 2015 14:36:45 -0700 (PDT)
In-Reply-To: <E1C2C971-03EB-47F6-9879-D6EC659404D4@petertodd.org>
References: <CAPswA9yU8MkbS_7CkJBmRTTxBdZ+2fx7FetGaqeHMZGG0G=1eA@mail.gmail.com>
<E1C2C971-03EB-47F6-9879-D6EC659404D4@petertodd.org>
Date: Thu, 23 Jul 2015 23:36:45 +0200
Message-ID: <CAPswA9zCxZ+mmwpHxF2Q8zur+UjjUMfZmgn75j4hLu1kux36AA@mail.gmail.com>
From: Kalle Rosenbaum <kalle@rosenbaum.se>
To: Peter Todd <pete@petertodd.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Process for BIP number allocation
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, 23 Jul 2015 21:36:47 -0000
A PoP-enabled fork of Mycelium is available at
https://github.com/kallerosenbaum/wallet and the server (validating
code) is available at https://github.com/kallerosenbaum/poppoc/
There's also a demo site using the server code at
http://www.rosenbaum.se:8080/ and a demo video at
https://www.youtube.com/watch?v=euzZcoCilhc
Mycelium Binaries are also available on the demo site.
Regards,
Kalle
2015-07-23 21:29 GMT+02:00, Peter Todd <pete@petertodd.org>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
>
> On 23 July 2015 06:21:55 GMT-04:00, Kalle Rosenbaum via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>>Hi all
>>
>>I suggest that we add to the "BIP Editor Responsibilities & Workflow"
>>section of BIP0001 that if the BIP editor for some reason won't handle
>>the BIP within a week, he/she should notify the author within that
>>same week with an estimate on when it will be handled.
>>
>>Maybe we could extend it to two weeks instead, the important thing is
>>that the author knows what to expect.
>>
>>I'm trying to get BIP numbers allocated for Proof of Payment. I have
>>requested it from the BIP editor Gregory Maxwell with CC this list. I
>>also emailed Gregory in private about it. So far I have not seen any
>>reaction to my requests.
>
> To be clear, where is an implementation of your proposed BIP?
>
> The philosophy of the process - particularly for non-consensus BIPs - is
> running code, preferably in production. An actual number for the standard
> that code implements isn't a barrier to that process.
>
> Remember that it's convenient for all if the number of BIPs out there isn't
> significantly higher than the number of actual standards in place that are
> being used.
>
>
> -----BEGIN PGP SIGNATURE-----
>
> iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVsUBy
> AAoJEMCF8hzn9Lnc47AIAI11FdNBCFr9TybCvxKS32Idk4aZ4fveJ6ucHZx1PWPl
> lzoz/CJBZGolWF9jWnpyiCnNxl64MjflNxi62ZD+VS4SEl0uHcYXdqXsNQzk9OoK
> bZFXHJ57jZlHCwpwiLM72EWN6AZG/XZZFXisNRAvoYqryHdb5dDmVok0wPH87qOH
> PBTlspyaKH4/OFDpslCdoDTLHcMxlasiyqNdC5NxC7eB1WpEtyGbOd1twvNeNH00
> 1opJNuajiUm1vJEhMS67a9DhfnYf9/3TDRtkc0lrYfF3r1n2aVtyzlPcJANX/cWa
> 7L9HtC4WpVLqny0AiTs5dK6DxPIUy/u2Q9yFZ2oL6dM=
> =RW4h
> -----END PGP SIGNATURE-----
>
>
|
