public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Hoffman <danielhoffman699@gmail•com>
To: Trevin Hofmann <trevinhofmann@gmail•com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Number Request: Addresses over Audio
Date: Tue, 9 Aug 2016 18:06:20 -0500	[thread overview]
Message-ID: <CAL9WuQXsbBJ0UwdS+o=UqJCcsebcPa9Ug5A=uNtc6Z+9CNEFPg@mail.gmail.com> (raw)
In-Reply-To: <CAL9WuQUt+CMG2bEX+yv3LrFV7qn-=OSdn02ZxxPQci-3_ykPNQ@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 3297 bytes --]

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>
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> 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> 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 )
>>>
>>> Justin
>>>
>>> On Mon, Aug 8, 2016 at 2:22 PM, Daniel Hoffman via bitcoin-dev <
>>> 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).
>>>>
>>>> _______________________________________________
>>>> bitcoin-dev mailing list
>>>> bitcoin-dev@lists•linuxfoundation.org
>>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Justin W. Newton
>>> Founder/CEO
>>> Netki, Inc.
>>>
>>> justin@netki•com
>>> +1.818.261.4248
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 #1.1.2: Type: text/html, Size: 6996 bytes --]

[-- Attachment #1.2: PastedGraphic-1.tiff --]
[-- Type: image/tiff, Size: 10972 bytes --]

[-- Attachment #2: BIP_latest_custom_address.flac --]
[-- Type: audio/flac, Size: 2484566 bytes --]

[-- Attachment #3: BIP_latest_custom_address.mp3 --]
[-- Type: audio/mpeg, Size: 585142 bytes --]

  reply	other threads:[~2016-08-09 23:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 21:22 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 [this message]
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
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='CAL9WuQXsbBJ0UwdS+o=UqJCcsebcPa9Ug5A=uNtc6Z+9CNEFPg@mail.gmail.com' \
    --to=danielhoffman699@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=trevinhofmann@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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