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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YIFG3-0000su-Sp
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Feb 2015 11:33:35 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.175 as permitted sender)
client-ip=209.85.212.175; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f175.google.com;
Received: from mail-wi0-f175.google.com ([209.85.212.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YIFG1-0001D5-MJ
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Feb 2015 11:33:35 +0000
Received: by mail-wi0-f175.google.com with SMTP id fb4so16020093wid.2
for <bitcoin-development@lists.sourceforge.net>;
Mon, 02 Feb 2015 03:33:27 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.7.103 with SMTP id i7mr41725518wja.53.1422876806860;
Mon, 02 Feb 2015 03:33:26 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Mon, 2 Feb 2015 03:33:26 -0800 (PST)
In-Reply-To: <CAG86ZOxYh+=rny3sPHeJ0qs6R=5frLXERKmwhVECGHo7tkrz3w@mail.gmail.com>
References: <CAG86ZOxYh+=rny3sPHeJ0qs6R=5frLXERKmwhVECGHo7tkrz3w@mail.gmail.com>
Date: Mon, 2 Feb 2015 12:33:26 +0100
X-Google-Sender-Auth: yAoYvGNMbZO8HyCbK4yyZkimJ0Q
Message-ID: <CANEZrP3Tuw3mJLSuoOA4iOmg6u9sdh-E5NNm_FgdYs3Mx39znA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Levin Keller <post@levinkeller.de>
Content-Type: multipart/alternative; boundary=047d7b5d43f4a1d6ed050e1952ef
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YIFG1-0001D5-MJ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Export format for xpub
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 11:33:36 -0000
--047d7b5d43f4a1d6ed050e1952ef
Content-Type: text/plain; charset=UTF-8
We generally don't edit BIPs like that after they've been written except to
add helpful links, examples etc and other things that don't add new
functionality. For this you'd write a new BIP. It doesn't have to be hard.
The process is:
1) Adapt the template BIP and fill it out with your motivation, design,
rationale and ideally some examples.
2) Post it here and ask Gregory for a BIP number. He will select one
through some magic algorithm I am still reverse engineering ;)
3) People will give feedback and try to spot problems in your spec.
I looked at what Andreas is doing a few days ago - basically it's just an
xpub string with a ?a=b&c=d query string added to the end, with a hierarchy
type specifier and something else I forgot, encoded into a QR code. So it
should be a very easy BIP to add.
Whilst you're at it you might want to add an HTTP POST based method,
though. Web apps scanning QR codes is kind of clunky compared to just
picking Coyno from a list in the wallet app and having it all
auto-magically activate.
On Mon, Feb 2, 2015 at 9:56 AM, Levin Keller <post@levinkeller.de> wrote:
> Hello everyone,
>
> I think this is my first email to this mailinglist so I will shortly
> introduce myself:
>
> I am Levin and the CEO of Coyno (www.coyno.com). Based in Berlin,
> mathematician. Bitcoiner since 2011.
>
> And now the reason for this email: Andreas (Schildbach) just released a
> new update of his wallet. It now provides an export functionality for the
> m/0' key in order to run read only copies on other devices. We already
> support the format on our website. Of course we would love for this to
> become standard. I also updated the Wiki article for Andreas' Wallet:
> https://en.bitcoin.it/wiki/Bitcoin_Wallet
>
> How do you like it? How does this format get standard? Shall I try to get
> a pull request to BIP32 passed?
>
> Cheers
>
> Levin
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--047d7b5d43f4a1d6ed050e1952ef
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">We generally don't edit BIPs like that after they'=
ve been written except to add helpful links, examples etc and other things =
that don't add new functionality. For this you'd write a new BIP. I=
t doesn't have to be hard. The process is:<div><br></div><div>1) Adapt =
the template BIP and fill it out with your motivation, design, rationale an=
d ideally some examples.</div><div><br></div><div>2) Post it here and ask G=
regory for a BIP number. He will select one through some magic algorithm I =
am still reverse engineering ;)</div><div><br></div><div>3) People will giv=
e feedback and try to spot problems in your spec.</div><div><br></div><div>=
I looked at what Andreas is doing a few days ago - basically it's just =
an xpub string with a ?a=3Db&c=3Dd query string added to the end, with =
a hierarchy type specifier and something else I forgot, encoded into a QR c=
ode. So it should be a very easy BIP to add.</div><div><br></div><div>Whils=
t you're at it you might want to add an HTTP POST based method, though.=
Web apps scanning QR codes is kind of clunky compared to just picking Coyn=
o from a list in the wallet app and having it all auto-magically activate.<=
/div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon=
, Feb 2, 2015 at 9:56 AM, Levin Keller <span dir=3D"ltr"><<a href=3D"mai=
lto:post@levinkeller.de" target=3D"_blank">post@levinkeller.de</a>></spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hello everyone=
,<div><br></div><div>I think this is my first email to this mailinglist so =
I will shortly introduce myself:</div><div><br></div><div>I am Levin and th=
e CEO of Coyno (<a href=3D"http://www.coyno.com" target=3D"_blank">www.coyn=
o.com</a>). Based in Berlin, mathematician. Bitcoiner since 2011.</div><div=
><br></div><div>And now the reason for this email: Andreas (Schildbach) jus=
t released a new update of his wallet. It now provides an export functional=
ity for the m/0' key in order to run read only copies on other devices.=
We already support the format on our website. Of course we would love for =
this to become standard. I also updated the Wiki article for Andreas' W=
allet:=C2=A0<a href=3D"https://en.bitcoin.it/wiki/Bitcoin_Wallet" target=3D=
"_blank">https://en.bitcoin.it/wiki/Bitcoin_Wallet</a></div><div><br></div>=
<div>How do you like it? How does this format get standard? Shall I try to =
get a pull request to BIP32 passed?</div><div><br></div><div>Cheers</div><s=
pan class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>Levin</div=
></font></span></div>
<br>-----------------------------------------------------------------------=
-------<br>
Dive into the World of Parallel Programming. The Go Parallel Website,<br>
sponsored by Intel and developed in partnership with Slashdot Media, is you=
r<br>
hub for all things parallel software development, from weekly thought<br>
leadership blogs to news, videos, case studies, tutorials and more. Take a<=
br>
look and join the conversation now. <a href=3D"http://goparallel.sourceforg=
e.net/" target=3D"_blank">http://goparallel.sourceforge.net/</a><br>_______=
________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>
--047d7b5d43f4a1d6ed050e1952ef--
|
