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
|
Return-Path: <bztdlinux@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3C5F171
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 10 Aug 2016 01:09:53 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pf0-f169.google.com (mail-pf0-f169.google.com
[209.85.192.169])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A7702172
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 10 Aug 2016 01:09:52 +0000 (UTC)
Received: by mail-pf0-f169.google.com with SMTP id p64so10106598pfb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 09 Aug 2016 18:09:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-transfer-encoding;
bh=GiMj9ExpjwQwd5oudzGar3hHWmsQgHrD8F2otnLdAtk=;
b=liSM376RI9xFJKY7qg9JKdw9oPpuypu0G6MVp85FJ+3+HRFl+tc3YCsAx10vC44nna
tySROL2wsqlSvvTU8kkhNp9jrrsmPCPKjnkcdDGyutcCq6HE4klbxxmDmXFNRpjFJn54
G9za+lBAv48tTtiqrwh/jFf4YZAZVzBOKb0WMS7PCQxxVRfT7oY1xBB4pncWdbsgKeqN
xcgrRi66BpC30CDVPPqRxT83OcO036hQOVHuN1XCB4Kzyy2HxL5XYkoXxL3rrbF5FpzY
CHdJPFNSg3vGmRkSd6uE+RMq/kZtnJ04dJ5RZtgWLfwTJlU6HUI+mkpLeUcc/YrONlie
YEiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-transfer-encoding;
bh=GiMj9ExpjwQwd5oudzGar3hHWmsQgHrD8F2otnLdAtk=;
b=KtnCeU/x9j9iiDnd5qpKZ5y0JNnzSDY/2TZ88FtPtM0WuOdhTVgs7ux/g5vlK82gI7
AExpbAJy9S3IxA1Df3XQVF61vV8fjAemNieGA1e1ytAkV7fGRHPPBRgUBwSbeY29d1eb
dl1EiD2TnOj0BSx3ciS5lmDtq/nsD7fl5LQiITsy93q7d+yMTrAGNF/Qj0KlGBkNmVQS
3+ZAorGvSPNgyV+vFt3pNgovsD/Uf15/aYbZmhqbjYiEEdkOPNjEjeA5exxrTavvpJVQ
8Y12l6gXzOTbAslze8qmuYPQJ00rhuZ8F1IXERO5KNV0TsXtOqhobYzEU3VJSzMz6Xmn
yYww==
X-Gm-Message-State: AEkoous/chzLl3V3oEijz/3XCu1uL1C0kUvLdimKfOJV/JFNuK+92bk27qB+u+VERYmNRw==
X-Received: by 10.98.149.131 with SMTP id c3mr2268898pfk.73.1470791392104;
Tue, 09 Aug 2016 18:09:52 -0700 (PDT)
Received: from ?IPv6:2620:101:80fc:232:7e7a:91ff:fe9e:8126?
([2620:101:80fc:232:7e7a:91ff:fe9e:8126])
by smtp.googlemail.com with ESMTPSA id
uc1sm58932684pac.24.2016.08.09.18.09.51
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Tue, 09 Aug 2016 18:09:51 -0700 (PDT)
To: bitcoin-dev@lists.linuxfoundation.org
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>
From: Thomas Daede <bztdlinux@gmail.com>
Message-ID: <aa41549b-b392-a225-26e1-2dcf4edfeb21@gmail.com>
Date: Tue, 9 Aug 2016 18:09:50 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAL9WuQXsbBJ0UwdS+o=UqJCcsebcPa9Ug5A=uNtc6Z+9CNEFPg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, FREEMAIL_REPLY,
HK_RANDOM_ENVFROM,
HK_RANDOM_FROM,RCVD_IN_DNSWL_LOW 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: Wed, 10 Aug 2016 01:15:47 +0000
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:09:53 -0000
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
>
|
