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
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
|
Return-Path: <danielhoffman699@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 67BDA71
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 10 Aug 2016 01:53:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f178.google.com (mail-io0-f178.google.com
[209.85.223.178])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2E626129
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 10 Aug 2016 01:53:08 +0000 (UTC)
Received: by mail-io0-f178.google.com with SMTP id 38so28777716iol.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 09 Aug 2016 18:53:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=Hp91Z4QjYhi0AdIkXl+YajZzlQjsb6EyKhBvjj5ncFg=;
b=DdrDTNoVt5CrvdqlB/aMsIH5c0ygX6czZYZ2CpGSoYX2WsHbQLxbWjSGbhDmIomp4c
HRlZ3u5WuNMPzzdV3TvHXlFMPgj/HVOhvrFhbz3GWPnk6lwHfUiHUGVrOhmMHFVVPRM+
WSfKPpk6IaWG5G2bhXC327rLUPvNpC1+aKzUBeniPgtxt/oDx/nAq5FA1jm4WxwhSVKC
jRlRBshA6IVtFkzknDuQqRaGAPuf1BhRyCKLgS4XfrveKDU8lrxploVZkdWRMQ7JV1Vr
OYKRzMxyPPXHsrk/zPTA3XrWJEHi36MPllF6Xfgc/MMHG+F7TGbm8i1w52yZj6DJO7Q9
lKSQ==
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:from:date
:message-id:subject:to;
bh=Hp91Z4QjYhi0AdIkXl+YajZzlQjsb6EyKhBvjj5ncFg=;
b=NtNxNbLSzcRqgt5I6vvIskBkiJ1Xr/PP3vRTJbnk6XTJbSV5edg/92R525g7zk41p4
9c93pEQrmH7oIcs1Sb2QXHKRiI1NSW9H0UoOt04QlrNcLXA0WLmEldYKPmFEDYixt05S
1V91AdId6DEdRzaKKtXFndbV50sHoxt8waLS0oZoR6dNb9SM5GvJf8AwMeltT4PU7MoQ
ytudX4KEKg0uq0dyGvDaVpWt5wrvHt4mX6dqVCKH2Yt0UH1HCFMxRLqTlvoPjmoLzU+I
EzGK/mzFV63vy28gFsPZH199+nbh+1xWpOEKrRYaZqxJBQcdzeh4V/YGmhrwuuiTqlbg
LoXA==
X-Gm-Message-State: AEkoouuDfp3rjceoRR2/RidPm1IyvyXOjQoZ9a7T8FkvqkYBSvLHQ8vsFj6PG58Y2z2v2C8q7TgaFm4O8w7XrA==
X-Received: by 10.107.8.134 with SMTP id h6mr2284574ioi.49.1470793987507; Tue,
09 Aug 2016 18:53:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.128.97 with HTTP; Tue, 9 Aug 2016 18:53:06 -0700 (PDT)
In-Reply-To: <aa41549b-b392-a225-26e1-2dcf4edfeb21@gmail.com>
References: <CAL9WuQUUeR3cuUXHxUfBTNJ-+r0iJ-7Z8KRNub0G3NBujnkqcw@mail.gmail.com>
<CABqynxJ3uph-4A+Ynq70CLa2kCCspTRsFWpKo_eP1FmVxZqSwQ@mail.gmail.com>
<CALd2G5dERuX2n33MGZJ+mtM8WnvtzZcWDFFUfNFZEGJFkkHLDg@mail.gmail.com>
<CAL9WuQUt+CMG2bEX+yv3LrFV7qn-=OSdn02ZxxPQci-3_ykPNQ@mail.gmail.com>
<CAL9WuQXsbBJ0UwdS+o=UqJCcsebcPa9Ug5A=uNtc6Z+9CNEFPg@mail.gmail.com>
<aa41549b-b392-a225-26e1-2dcf4edfeb21@gmail.com>
From: Daniel Hoffman <danielhoffman699@gmail.com>
Date: Tue, 9 Aug 2016 20:53:06 -0500
Message-ID: <CAL9WuQX=nPkmt6S5KJn=8UdmAnxU206hG3cL_qqXdmzvQ83CuQ@mail.gmail.com>
To: Thomas Daede <bztdlinux@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a113f9d6429cdd40539ade9b1
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
HTML_MESSAGE,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
Subject: Re: [bitcoin-dev] BIP Number Request: Addresses over Audio
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, 10 Aug 2016 01:53:09 -0000
--001a113f9d6429cdd40539ade9b1
Content-Type: text/plain; charset=UTF-8
Thomas
In all honesty, I shouldn't have added the multiple feature. It should
always stay to one and have the Bitcoin address's built in checksum do all
of the heavy lifting (or implement another checksum into the protocol).
Having said that, it would make the most sense to not include BIP21
requests. The frequencies that are going to be used are prone to being
changed (probably moving them into the ultrasound range, at least for the
16 tones)
Luke Dashjr
I thought it was only 12, will change it accordingly.
Chris
I looked at Audio Modem and will probably look at the others soon as well.
The general idea of this BIP is to see if you all even approve of the idea
of sending Bitcoin addresses over sound waves. I will push it into the
ultrasound, and I might implement phase modulation.
On Tue, Aug 9, 2016 at 8:09 PM, Thomas Daede via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> If this is just encoding BIP-21 addresses, it is basically an "audio QR
> code". In this case, does publishing it as a BIP still make sense? (Not
> to imply that it doesn't, but it's something you should consider.)
>
> Please look at existing implementations of audio modems when creating
> your design. A lot of this work has been done many times before, so
> there is a lot to learn from.
>
> Your selected frequencies are harmonics of each other, meaning nonlinear
> distortion will make detection more difficult. The Bell 202 and similar
> modem standards chose AFSK frequencies to minimize interference.
>
> Repeating a message multiple times is a very inefficient method of error
> recovery. It works, but there may be better techniques, such as trellis
> modulation or other convolutional codes.
>
> Defining channel models to simulate your various use cases will help a
> lot to determine if you have met your requirements.
>
> - Thomas
>
> P.S. I also briefly considered audio to exchange transactions with a
> hardware wallet. Using GNU Radio made the implementation much easier.
>
> On 08/09/2016 04:06 PM, Daniel Hoffman via bitcoin-dev wrote:
> > I have updated the GitHub a lot (changed tones to be less chirpy, fixed
> > some smalls) and made a couple of samples (see attachment for MP3 and
> > FLAC of both tone tables, first 16 then 4). Is this good enough to
> > warrant an official BIP number? I haven't built a decoder yet, but it
> > seems like the encoder is working properly (looked at Audacity, seems
> > like it is working), and some people on reddit want to "allow for
> > decoding experiments"
> > <https://www.reddit.com/r/btc/comments/4wsn7v/bip_proposal_
> addresses_over_audio_thoughts/d69m3st>
> >
> > What suggestions do you all have for it?
> >
> > On Mon, Aug 8, 2016 at 8:50 PM, Daniel Hoffman
> > <danielhoffman699@gmail.com <mailto:danielhoffman699@gmail.com>> wrote:
> >
> > It wouldn't be feasible in the vast majority of cases, but I can't
> > think of a reason why it can't be built into the standard.
> >
> > On Mon, Aug 8, 2016 at 5:59 PM, Trevin Hofmann via bitcoin-dev
> > <bitcoin-dev@lists.linuxfoundation.org
> > <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> >
> > Would it be feasible to transmit an entire BIP21 URI as audio?
> > If you were to encode any extra information (such as amount), it
> > would be useful to include a checksum for the entire message.
> > This checksum could possibly be used instead of the checksum in
> > the address.
> >
> > Trevin
> >
> >
> > On Aug 8, 2016 3:06 PM, "Justin Newton via bitcoin-dev"
> > <bitcoin-dev@lists.linuxfoundation.org
> > <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> >
> > Daniel,
> > Thanks for proposing this. I think this could have some
> > useful use cases as you state. I was wondering what you
> > would think to adding some additional tones to optionally
> > denote an amount (in satoshis?).
> >
> > (FYI, actual link is here: https://github.com/Dako300/BIP
> > <https://github.com/Dako300/BIP> )
> >
> > Justin
> >
> > On Mon, Aug 8, 2016 at 2:22 PM, Daniel Hoffman via
> > bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org
> > <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> >
> > This is my BIP idea: a fast, robust, and standardized
> > for representing Bitcoin addresses over audio. It takes
> > the binary representation of the Bitcoin address (little
> > endian), chops that up into 4 or 2 bit chunks (depending
> > on type, 2 bit only for low quality audio like american
> > telephone lines), and generates a tone based upon that
> > value. This started because I wanted an easy way to
> > donate to podcasts that I listen to, and having a
> > Shazam-esque app (or a media player with this
> > capability) that gives me an address automatically would
> > be wonderful for both the consumer and producer. Comes
> > with error correction built into the protocol
> >
> > You can see the full specification of the BIP on my
> > GitHub page (https://github.com/Dako300/BIP-0153
> > <https://github.com/Dako300/BIP-0153>).
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > <mailto:bitcoin-dev@lists.linuxfoundation.org>
> > https://lists.linuxfoundation.
> org/mailman/listinfo/bitcoin-dev
> > <https://lists.linuxfoundation.org/mailman/
> listinfo/bitcoin-dev>
> >
> >
> >
> >
> > --
> >
> > Justin W. Newton
> > Founder/CEO
> > Netki, Inc.
> >
> > justin@netki.com <mailto:justin@netki.com>
> > +1.818.261.4248 <tel:+1.818.261.4248>
> >
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > <mailto:bitcoin-dev@lists.linuxfoundation.org>
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-
> dev
> > <https://lists.linuxfoundation.org/mailman/
> listinfo/bitcoin-dev>
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > <mailto:bitcoin-dev@lists.linuxfoundation.org>
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> > <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
> >
> >
> >
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a113f9d6429cdd40539ade9b1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thomas<div>In all honesty, I shouldn't have added the =
multiple feature. It should always stay to one and have the Bitcoin address=
's built in checksum do all of the heavy lifting (or implement another =
checksum into the protocol). Having said that, it would make the most sense=
to not include BIP21 requests. The frequencies that are going to be used a=
re prone to being changed (probably moving them into the ultrasound range, =
at least for the 16 tones)</div><div><br></div><div>Luke Dashjr</div><div>I=
thought it was only 12, will change it accordingly.</div><div><br></div><d=
iv>Chris</div><div>I looked at Audio Modem and will probably look at the ot=
hers soon as well.=C2=A0</div><div><br></div><div>The general idea of this =
BIP is to see if you all even approve of the idea of sending Bitcoin addres=
ses over sound waves. I will push it into the ultrasound, and I might imple=
ment phase modulation.</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Aug 9, 2016 at 8:09 PM, Thomas Daede via bitcoin-d=
ev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundatio=
n.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</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">If this is just encoding BIP-21=
addresses, it is basically an "audio QR<br>
code". In this case, does publishing it as a BIP still make sense? (No=
t<br>
to imply that it doesn't, but it's something you should consider.)<=
br>
<br>
Please look at existing implementations of audio modems when creating<br>
your design. A lot of this work has been done many times before, so<br>
there is a lot to learn from.<br>
<br>
Your selected frequencies are harmonics of each other, meaning nonlinear<br=
>
distortion will make detection more difficult. The Bell 202 and similar<br>
modem standards chose AFSK frequencies to minimize interference.<br>
<br>
Repeating a message multiple times is a very inefficient method of error<br=
>
recovery. It works, but there may be better techniques, such as trellis<br>
modulation or other convolutional codes.<br>
<br>
Defining channel models to simulate your various use cases will help a<br>
lot to determine if you have met your requirements.<br>
<br>
- Thomas<br>
<br>
P.S. I also briefly considered audio to exchange transactions with a<br>
hardware wallet. Using GNU Radio made the implementation much easier.<br>
<span class=3D""><br>
On 08/09/2016 04:06 PM, Daniel Hoffman via bitcoin-dev wrote:<br>
> I have updated the GitHub a lot (changed tones to be less chirpy, fixe=
d<br>
> some smalls) and made a couple of samples (see attachment for MP3 and<=
br>
> FLAC of both tone tables, first 16 then 4). Is this good enough to<br>
> warrant an official BIP number? I haven't built a decoder yet, but=
it<br>
> seems like the encoder is working properly (looked at Audacity, seems<=
br>
> like it is working), and some people on reddit want to "allow for=
<br>
> decoding experiments"<br>
</span>> <<a href=3D"https://www.reddit.com/r/btc/comments/4wsn7v/bip=
_proposal_addresses_over_audio_thoughts/d69m3st" rel=3D"noreferrer" target=
=3D"_blank">https://www.reddit.com/r/btc/<wbr>comments/4wsn7v/bip_proposal_=
<wbr>addresses_over_audio_thoughts/<wbr>d69m3st</a>><br>
<span class=3D"">><br>
> What suggestions do you all have for it?<br>
><br>
> On Mon, Aug 8, 2016 at 8:50 PM, Daniel Hoffman<br>
</span><span class=3D"">> <<a href=3D"mailto:danielhoffman699@gmail.c=
om">danielhoffman699@gmail.com</a> <mailto:<a href=3D"mailto:danielhoffm=
an699@gmail.com">danielhoffman699@<wbr>gmail.com</a>>> wrote:<br>
><br>
>=C2=A0 =C2=A0 =C2=A0It wouldn't be feasible in the vast majority of=
cases, but I can't<br>
>=C2=A0 =C2=A0 =C2=A0think of a reason why it can't be built into th=
e standard.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0On Mon, Aug 8, 2016 at 5:59 PM, Trevin Hofmann via =
bitcoin-dev<br>
>=C2=A0 =C2=A0 =C2=A0<<a href=3D"mailto:bitcoin-dev@lists.linuxfounda=
tion.org">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
</span><span class=3D"">>=C2=A0 =C2=A0 =C2=A0<mailto:<a href=3D"mailt=
o:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfounda=
tion.org</a>>> wrote:<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Would it be feasible to transmit an e=
ntire BIP21 URI as audio?<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0If you were to encode any extra infor=
mation (such as amount), it<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0would be useful to include a checksum=
for the entire message.<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0This checksum could possibly be used =
instead of the checksum in<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the address.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Trevin<br>
><br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On Aug 8, 2016 3:06 PM, "Justin =
Newton via bitcoin-dev"<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<<a href=3D"mailto:bitcoin-dev@lis=
ts.linuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
</span><span class=3D"">>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<mailto:<a=
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<w=
br>linuxfoundation.org</a>>> wrote:<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Daniel,<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks for prop=
osing this.=C2=A0 I think this could have some<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0useful use cases as you=
state.=C2=A0 I was wondering what you<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0would think to adding s=
ome additional tones to optionally<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0denote an amount (in sa=
toshis?).<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(FYI, actual link is he=
re:=C2=A0 <a href=3D"https://github.com/Dako300/BIP" rel=3D"noreferrer" tar=
get=3D"_blank">https://github.com/Dako300/BIP</a><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<<a href=3D"https://=
github.com/Dako300/BIP" rel=3D"noreferrer" target=3D"_blank">https://github=
.com/Dako300/<wbr>BIP</a>> )<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Justin<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On Mon, Aug 8, 2016 at =
2:22 PM, Daniel Hoffman via<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bitcoin-dev <<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>li=
nuxfoundation.org</a><br>
</span><span class=3D"">>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0<mailto:<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitc=
oin-dev@lists.<wbr>linuxfoundation.org</a>>> wrote:<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0This is m=
y BIP idea: a fast, robust, and standardized<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0for repre=
senting Bitcoin addresses over audio. It takes<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the binar=
y representation of the Bitcoin address (little<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0endian), =
chops that up into 4 or 2 bit chunks (depending<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0on type, =
2 bit only for low quality audio like american<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0telephone=
lines), and generates a tone based upon that<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0value. Th=
is started because I wanted an easy way to<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0donate to=
podcasts that I listen to, and having a<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Shazam-es=
que app (or a media player with this<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0capabilit=
y) that gives me an address automatically would<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0be wonder=
ful for both the consumer and producer. Comes<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0with erro=
r correction built into the protocol<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0You can s=
ee the full specification of the BIP on my<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0GitHub pa=
ge (<a href=3D"https://github.com/Dako300/BIP-0153" rel=3D"noreferrer" targ=
et=3D"_blank">https://github.com/Dako300/<wbr>BIP-0153</a><br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&l=
t;<a href=3D"https://github.com/Dako300/BIP-0153" rel=3D"noreferrer" target=
=3D"_blank">https://github.com/Dako300/<wbr>BIP-0153</a>>).<br>
<span class=3D"">><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0_________=
_____________________<wbr>_________________<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bitcoin-d=
ev mailing list<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>li=
nuxfoundation.org</a><br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&l=
t;mailto:<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-d=
ev@lists.<wbr>linuxfoundation.org</a>><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=
=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel=3D"=
noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org/mailma=
n/listinfo/bitcoin-<wbr>dev</a><br>
<span class=3D"">>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0<<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo=
/bitcoin-dev" rel=3D"noreferrer" target=3D"_blank">https://lists.<wbr>linux=
foundation.org/mailman/<wbr>listinfo/bitcoin-dev</a>><br>
><br>
><br>
><br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Justin W. Newton<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Founder/CEO<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Netki, Inc.<br>
><br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailt=
o:justin@netki.com">justin@netki.com</a> <mailto:<a href=3D"mailto:justi=
n@netki.com">justin@netki.com</a>><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"tel:%2B1.818=
.261.4248" value=3D"+18182614248">+1.818.261.4248</a> <tel:<a href=3D"te=
l:%2B1.818.261.4248" value=3D"+18182614248">+1.818.261.4248</a>><br>
<span class=3D"">><br>
><br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0_______________________=
_______<wbr>_________________<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bitcoin-dev mailing lis=
t<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:bitco=
in-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfoundation.or=
g</a><br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<mailto:<a hr=
ef=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>=
linuxfoundation.org</a>><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://list=
s.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel=3D"noreferrer" targ=
et=3D"_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitco=
in-<wbr>dev</a><br>
<span class=3D"">>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<<a=
href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" re=
l=3D"noreferrer" target=3D"_blank">https://lists.<wbr>linuxfoundation.org/m=
ailman/<wbr>listinfo/bitcoin-dev</a>><br>
><br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0______________________________<wbr>__=
_______________<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bitcoin-dev mailing list<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:bitcoin-dev@lists.l=
inuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<mailto:<a href=3D"mailto:b=
itcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfoundatio=
n.org</a>><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://lists.linuxfoundat=
ion.org/mailman/listinfo/bitcoin-dev" rel=3D"noreferrer" target=3D"_blank">=
https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a=
><br>
<span class=3D"im HOEnZb">>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<<a href=
=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel=3D"=
noreferrer" target=3D"_blank">https://lists.<wbr>linuxfoundation.org/mailma=
n/<wbr>listinfo/bitcoin-dev</a>><br>
><br>
><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> bitcoin-dev mailing list<br>
> <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.<wbr>linuxfoundation.org</a><br>
> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wb=
r>org/mailman/listinfo/bitcoin-<wbr>dev</a><br>
><br>
</span><div class=3D"HOEnZb"><div class=3D"h5">____________________________=
__<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</div></div></blockquote></div><br></div>
--001a113f9d6429cdd40539ade9b1--
|
