summaryrefslogtreecommitdiff
path: root/08/2cd8ceb39b1e65c9fc9a78890a098fe88f8976
blob: f866eefee6b758d23f93d47581d452c4056850b2 (plain)
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
Return-Path: <bitdev@theochino.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 22CFB82B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 10 Aug 2016 11:58:03 +0000 (UTC)
X-Greylist: delayed 00:08:42 by SQLgrey-1.7.6
Received: from ns3094582.localdomain (outbound.chino.ws [91.121.200.135])
	by smtp1.linuxfoundation.org (Postfix) with ESMTP id 39B46AD
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 10 Aug 2016 11:58:02 +0000 (UTC)
Received: from mail-it0-f43.google.com (mail-it0-f43.google.com
	[209.85.214.43])
	by ns3094582.localdomain (Postfix) with ESMTPSA id 9667681982
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 10 Aug 2016 09:42:33 +0000 (UTC)
Received: by mail-it0-f43.google.com with SMTP id x130so41789487ite.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 10 Aug 2016 04:49:18 -0700 (PDT)
X-Gm-Message-State: AEkoousXinHjJVa4StWCJOjJOdVpkTUsxN/S+D1x2xk1SnUnwbusqWp3IxRNDkRwo84O/GavYYDcyefjvZB3Ng==
X-Received: by 10.36.54.135 with SMTP id l129mr2717157itl.73.1470829757752;
	Wed, 10 Aug 2016 04:49:17 -0700 (PDT)
MIME-Version: 1.0
Reply-To: bitdev@theochino.com
Received: by 10.79.122.202 with HTTP; Wed, 10 Aug 2016 04:49:16 -0700 (PDT)
In-Reply-To: <CAJowKg+yh+PgTE14=+pPUXFdB_AGrsgk3cNSFnTGDYecsxDP5g@mail.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>
	<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>
From: Theo Chino <bitdev@theochino.com>
Date: Wed, 10 Aug 2016 07:49:16 -0400
X-Gmail-Original-Message-ID: <CAFh0iXOLN6B27Fkc=GXo-j3VwA0hkNggCiQOhR35R52yQGwSwg@mail.gmail.com>
Message-ID: <CAFh0iXOLN6B27Fkc=GXo-j3VwA0hkNggCiQOhR35R52yQGwSwg@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a1143f3523c82410539b63d97
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE
	autolearn=ham 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 14:53:25 +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 11:58:03 -0000

--001a1143f3523c82410539b63d97
Content-Type: text/plain; charset=UTF-8

Another use for the audio would be for watches that can listen but can't
use a camera (ie: Samsung S2), so sound would be great.

On Wed, Aug 10, 2016 at 7:42 AM, Erik Aronesty via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> NOTE:
>
> Addresses aren't really meant to be broadcast - you should probably be
> encoding BIP32 public seeds, not addresses.
>
> OR simply:
>
> - Send btc to rick@q32.com
> - TXT record _btc.rick.q32.com is queried (_<coin-code>.<name>.<domain>)
> - DNS-SEC validation is *required*
> - TXT record contains addr:[<bip32-pub-seed>]
>
> Then you can just say, in the podcast, "Send your bitcoin donations to
> rick@q32.com".   And you can link it to your email address, if your
> provider lets you set up a TXT record.   (By structuring the TXT record
> that way, many existing email providers will support the standard without
> having to change anything.)
>
> This works with audio, video, web and other publishing formats... and very
> little infrastructure change is needed.
>
>
> On Wed, Aug 10, 2016 at 6:41 AM, Tier Nolan via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Have you considered CDMA?  This has the nice property that it just sounds
>> like noise.  The codes would take longer to send, but you could send
>> multiple bits at once and have the codes orthogonal.
>>
>> _______________________________________________
>> 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
>
>

--001a1143f3523c82410539b63d97
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Another use for the audio would be for watches that c=
an listen but can&#39;t use a camera (ie: Samsung S2), so sound would be gr=
eat.<br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Wed, Aug 10, 2016 at 7:42 AM, Erik Aronesty via bitcoin-dev <span dir=
=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" targe=
t=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>NOTE: <br><br>Address=
es aren&#39;t really meant to be broadcast - you should probably be encodin=
g BIP32 public seeds, not addresses.=C2=A0=C2=A0 <br><br></div>OR simply:<b=
r><br><div><div>- Send btc to <a href=3D"mailto:rick@q32.com" target=3D"_bl=
ank">rick@q32.com</a><br>- TXT record _<a href=3D"http://btc.rick.q32.com" =
target=3D"_blank">btc.rick.q32.com</a> is queried (_&lt;coin-code&gt;.&lt;n=
ame&gt;.&lt;domain&gt;)<br>- DNS-SEC validation is <i>required</i><br>- TXT=
 record contains addr:[&lt;bip32-pub-seed&gt;]<br></div><br></div><div>Then=
 you can just say, in the podcast, &quot;Send your bitcoin donations to <a =
href=3D"mailto:rick@q32.com" target=3D"_blank">rick@q32.com</a>&quot;.=C2=
=A0=C2=A0 And you can link it to your email address, if your provider lets =
you set up a TXT record.=C2=A0=C2=A0 (By structuring the TXT record that wa=
y, many existing email providers will support the standard without having t=
o change anything.)<br></div><div><i></i><br></div><div>This works with aud=
io, video, web and other publishing formats... and very little infrastructu=
re change is needed.<br><br></div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote"><span class=3D"">On Wed, Aug 10, 2016 at 6:41 AM, Ti=
er Nolan via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-de=
v@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.<wbr>linux=
foundation.org</a>&gt;</span> wrote:<br></span><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><span class=3D""><div dir=3D"ltr"><div>Have you considered CDMA?=C2=A0 T=
his has the nice property that it just sounds like noise.=C2=A0 The codes w=
ould take longer to send, but you could send multiple bits at once and have=
 the codes orthogonal.<br></div></div>
<br></span><span class=3D"">______________________________<wbr>____________=
_____<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundat<wbr>ion.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-d<wbr>ev</a><br>
<br></span></blockquote></div><br></div>
<br>______________________________<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>
<br></blockquote></div><br></div>

--001a1143f3523c82410539b63d97--