From: Theo Chino <bitdev@theochino.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Number Request: Addresses over Audio
Date: Wed, 10 Aug 2016 07:49:16 -0400 [thread overview]
Message-ID: <CAFh0iXOLN6B27Fkc=GXo-j3VwA0hkNggCiQOhR35R52yQGwSwg@mail.gmail.com> (raw)
In-Reply-To: <CAJowKg+yh+PgTE14=+pPUXFdB_AGrsgk3cNSFnTGDYecsxDP5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
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
>
>
[-- Attachment #2: Type: text/html, Size: 3170 bytes --]
next prev parent reply other threads:[~2016-08-10 11:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 21:22 [bitcoin-dev] BIP Number Request: Addresses over Audio Daniel Hoffman
2016-08-08 22:06 ` Justin Newton
2016-08-08 22:35 ` Daniel Hoffman
2016-08-08 22:59 ` Trevin Hofmann
2016-08-09 1:50 ` Daniel Hoffman
2016-08-09 23:06 ` Daniel Hoffman
2016-08-10 0:17 ` Jannes Faber
2016-08-10 0:27 ` Chris Riley
2016-08-10 0:36 ` Luke Dashjr
2016-08-10 1:09 ` Thomas Daede
2016-08-10 1:53 ` Daniel Hoffman
2016-08-10 2:14 ` Gregory Maxwell
2016-08-10 10:41 ` Tier Nolan
2016-08-10 11:42 ` Erik Aronesty
2016-08-10 11:49 ` Theo Chino [this message]
2016-08-10 16:01 ` Daniel Hoffman
2016-08-10 17:28 ` Erik Aronesty
2016-08-10 17:38 ` Pieter Wuille
2016-08-10 17:55 ` Daniel Hoffman
2016-08-10 22:31 ` James MacWhyte
2016-08-11 13:55 ` Erik Aronesty
2016-08-11 15:13 ` Tier Nolan
2016-08-11 20:37 ` Erik Aronesty
2016-08-12 0:36 ` Gregory Maxwell
2016-08-12 12:36 ` Erik Aronesty
2016-08-12 15:49 ` Jorge Timón
2016-08-12 18:39 ` James MacWhyte
2016-08-13 4:41 ` Daniel Hoffman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFh0iXOLN6B27Fkc=GXo-j3VwA0hkNggCiQOhR35R52yQGwSwg@mail.gmail.com' \
--to=bitdev@theochino.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox