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
|
Return-Path: <keatonatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 8643492
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 10 Aug 2016 22:31:28 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com
[209.85.220.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F346E217
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 10 Aug 2016 22:31:27 +0000 (UTC)
Received: by mail-qk0-f179.google.com with SMTP id t7so58383602qkh.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 10 Aug 2016 15:31:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=QwCyChX8A7A9XwRzk18dHYUEE5+RxHAmh+ZZ7pf5v74=;
b=QDvDZToDUleFotoVwuapkHAz6Ghoqamki1Nof/F2iCNRd9hUFioewW4OW4HphEEMrR
hmzbD9oq/+J5jdetsEojqRGONzAia/cAuDhz2h7par/Dqnc4E9JQrbDcigSjOwOcdxAi
tP3q6NImEMnnajugO7Bld7xv9MksA7r8XZv1PXQIR+i1X+utdZUlCbk3uiIrRF2dqhZ6
b0/3cTDKTGkFLulU09uC4qtx7TYHRyeLvGwXt+NgguAbdqf5znepmUXbbqt24RRjSCyf
fsxlPt8qzqXqWKnTVtY93oOPy9IT7jamJnMSkm3vvhkK+szDrFcDSwU7CrDa37jWmEPK
tKsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=QwCyChX8A7A9XwRzk18dHYUEE5+RxHAmh+ZZ7pf5v74=;
b=Eyua3Fk5DwOy4XmapeWTXV0UcYO1rHGnmheQ7fJt0L5RFr5FTYUjBGSKhV9JwygNIe
72zhzlliOxXyJYjfBhnVNJXYHwCKPPxCGKFaTqaghkmTwwlNYydFU4Mg0yhYowIxmbaN
lXkzcgt8dIzTO3GnWuWGypUQowkr0q8d0DcKAAdv8F+829o3CrroPIkk4jgHSL1Ldh83
afrKjyAJqX6JXfSW4Ga+qpGgrwGr28mTzNo12o6MYdZgWs9yjTSAtpIka4pKuwgRt46o
Jii7avNF1s54p74tIRqzwkWpiWlC4BfnWlsOgakQ6qN3X0rMx7EWsxk6P5wCWgW8g36L
5LhQ==
X-Gm-Message-State: AEkoousAk9SZkJ7eVUR2l+mMG0n7nEEq+Z56LpWG5aTqJT/KbpyJuAQJ/OoJXpJwi4366SdUUbFgRQh/8XwNFg==
X-Received: by 10.55.36.131 with SMTP id k3mr7266753qkk.86.1470868287150; Wed,
10 Aug 2016 15:31:27 -0700 (PDT)
MIME-Version: 1.0
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>
<CAAS2fgR-weACn_Ezg8-uZuSH0QT5dfLEFE5WO2VDi0nx8H1e9g@mail.gmail.com>
<CAE-z3OXeJHvjyF_phVh2u9S45_xss=C9ykL=BN=n=BxTx+AbrQ@mail.gmail.com>
<CAJowKg+yh+PgTE14=+pPUXFdB_AGrsgk3cNSFnTGDYecsxDP5g@mail.gmail.com>
<CAFh0iXOLN6B27Fkc=GXo-j3VwA0hkNggCiQOhR35R52yQGwSwg@mail.gmail.com>
<CAL9WuQXH8TAKRabPSrZzMzpFBwmujdv-uSXJLeTt9u3H9WAFGw@mail.gmail.com>
<CAJowKgK0N9VJZsm4fbZ5VvteUjoQkh9-xhg1yfcD3NRTuFV78Q@mail.gmail.com>
<CAPg+sBi6mPviRRKysbuuOFKoYoyTufpUO_rJxJdB-8=7KGurYw@mail.gmail.com>
<CAL9WuQVGu-7V3+Ty86zOMm1HdqCw5+999Vw7VCn6HXBwdoKBpA@mail.gmail.com>
In-Reply-To: <CAL9WuQVGu-7V3+Ty86zOMm1HdqCw5+999Vw7VCn6HXBwdoKBpA@mail.gmail.com>
From: James MacWhyte <macwhyte@gmail.com>
Date: Wed, 10 Aug 2016 22:31:16 +0000
Message-ID: <CAH+Axy7ZCn4BLyk1GxhTNx945x-7sqW8Ehks32eLod3N0=HJYA@mail.gmail.com>
To: Daniel Hoffman <danielhoffman699@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=001a114533eac460a50539bf3526
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,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 22:31:28 -0000
--001a114533eac460a50539bf3526
Content-Type: text/plain; charset=UTF-8
I agree, audio-based transference isn't really great for a podcast or radio
ad. It could be used to transmit payment details between phones that don't
have cameras, though. I think it would be better to define a standard for
transmitting information over audio, but not define what information is to
be conveyed so people could use the method for sending pub keys, payment
protocol requests, or anything else developers might want to make use of.
I'm guessing some sort of data-over-audio standard already exists? In which
case the bip could just say "we use [standard] to convey any
bitcoin-related data".
On Wed, Aug 10, 2016, 10:55 Daniel Hoffman via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> thats how i thought it worked originally, but im not well versed on that,
> so i took his word for it
>
> On Aug 10, 2016 12:38 PM, "Pieter Wuille via bitcoin-dev" <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> On Wed, Aug 10, 2016 at 7:28 PM, Erik Aronesty via bitcoin-dev
>> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> > By sending a public seed, there's no way for someone to use the
>> transmitted
>> > address and trace the total amount of payments to it.
>>
>> Worse. By revealing a public seed, anyone who has seen it (= anyone
>> who ever pays you through it) can identity all payments to _any_
>> address derived from that seed.
>>
>> --
>> Pieter
>> _______________________________________________
>> 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
>
--001a114533eac460a50539bf3526
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I agree, audio-based transference isn't really great f=
or a podcast or radio ad. It could be used to transmit payment details betw=
een phones that don't have cameras, though. I think it would be better =
to define a standard for transmitting information over audio, but not defin=
e what information is to be conveyed so people could use the method for sen=
ding pub keys, payment protocol requests, or anything else developers might=
want to make use of.</div><span>
</span><p dir=3D"ltr">I'm guessing some sort of data-over-audio standar=
d already exists? In which case the bip could just say "we use [standa=
rd] to convey any bitcoin-related data".<br>
</p><span>
</span><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Aug 10, 2016=
, 10:55 Daniel Hoffman via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@li=
sts.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">thats how i thoug=
ht it worked originally, but im not well versed on that, so i took his word=
for it</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Aug 10, 2016 1=
2:38 PM, "Pieter Wuille via bitcoin-dev" <<a href=3D"mailto:bi=
tcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.li=
nuxfoundation.org</a>> wrote:<br type=3D"attribution"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">On Wed, Aug 10, 2016 at 7:28 PM, Erik Aronesty via bitcoin-de=
v<br>
<<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bla=
nk">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br>
> By sending a public seed,=C2=A0 there's no way for someone to use =
the transmitted<br>
> address and trace the total amount of payments to it.<br>
<br>
Worse. By revealing a public seed, anyone who has seen it (=3D anyone<br>
who ever pays you through it) can identity all payments to _any_<br>
address derived from that seed.<br>
<br>
--<br>
Pieter<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--001a114533eac460a50539bf3526--
|
