Have you checked AudioModem out: https://github.com/applidium/AudioModem Or Chirp: http://www.chirp.io/faq/ Or this Network World article (particularly the last portion on bitcoin): http://www.networkworld.com/article/2956450/smartphones/sending-data-over-sound-revisited.html and http://www.networkworld.com/article/2689597/opensource-subnet/how-a-tv-network-is-being-used-to-move-financial-transactions.html Instead of re-inventing the wheel, perhaps take a look at them. Or at least to see their design choices and rationale. Cheers! On Tue, Aug 9, 2016 at 7:06 PM, Daniel Hoffman via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> 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" > > > What suggestions do you all have for it? > > On Mon, Aug 8, 2016 at 8:50 PM, Daniel Hoffman > 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 >>> >>> >> > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > >