I started work on the decoder. It works by comparing each cycle of the sine
wave recorded with a certain frequency (freq_t). The function that does
this currently returns the last sample that falls in that range over all
samples. The longest chain to match up with a certain frequency the best is
For reasons others have pointed out, it's not really plausible.
Either way, this has nothing to do with transmitting data over audio.
Please start a new thread if you want to discuss your idea instead of
hijacking this one. Thanks ;)
On Fri, Aug 12, 2016, 05:36 Erik Aronesty via bitcoin-dev <
No, anyone with the bip32 public seed can do the same as the receiver as
"watch only". The only difference is rhat the receiver can actually spend
the coins. As gmaxwell explained, if it's expensive for everyone, it will
be also expensive for the receiver (assuming no interaction after the bip32
I'm imagining a "publishable seed" such that:
- someone can derive a random bitcoin address from it - and send funds to
it.
- the possible derived address space is large enough that generating all
possible addresses would be a barrier
- the receiver, however, knowing the private key, can
On Thu, Aug 11, 2016 at 8:37 PM, Erik Aronesty via bitcoin-dev
wrote:
> Still not sure how you can take a BIP32 public seed and figure out if an
> address was derived from it though. I mean, wouldn't I have to compute all
> 2^31 possible public child
Can't have shared secrets or interactivity for a public address to have the
love it needs.
Still not sure how you can take a BIP32 public seed and figure out if an
address was derived from it though. I mean, wouldn't I have to compute
all 2^31 possible public child addresses?
On Thu, Aug
On Thu, Aug 11, 2016 at 2:55 PM, Erik Aronesty via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Sorr, I thought there was some BIP for a public seed such that someone can
> generate new random addresses, but cannot trivially verify whether an
> address was derived from the seed.
Sorr, I thought there was some BIP for a public seed such that someone can
generate new random addresses, but cannot trivially verify whether an
address was derived from the seed.
On Wed, Aug 10, 2016 at 1:38 PM, Pieter Wuille
wrote:
> On Wed, Aug 10, 2016 at 7:28 PM,
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
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
>
On Wed, Aug 10, 2016 at 7:28 PM, Erik Aronesty via bitcoin-dev
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
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.
On Aug 10, 2016 12:02 PM, "Daniel Hoffman via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Erik
> What would be the advantages of transmitting a
Erik
What would be the advantages of transmitting a BIP32 public seed, instead
of a plain address?
Theo
I didn't really think of that, but that's genius.
On Wed, Aug 10, 2016 at 6:49 AM, Theo Chino via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Another use for the audio would
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
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
Wow. No value judgement, but 1980 called, they want their radio broadcast
for analogue modems back. Both very cool and very cringe worthy.
It sounds quite horrible tbh. Imagine this being as pervasive as bar and qr
codes. And it's as meaningful and unpleasant to the human ear as a qr code
is to
On Tue, Aug 9, 2016 at 11: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
If this is just encoding BIP-21 addresses, it is basically an "audio QR
code". In this case, does publishing it as a BIP still make sense? (Not
to imply that it doesn't, but it's something you should consider.)
Please look at existing implementations of audio modems when creating
your design. A
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
On Tuesday, August 09, 2016 11:06:20 PM Daniel Hoffman via bitcoin-dev wrote:
> Is this good enough to warrant an official BIP number?
Yeah, let's call it BIP 170.
Next step is to:
- Fix the BIP number in the file
- Format it in the usual BIP mediawiki format instead of markdown
- Add it to a
I wouldn't worry about payment requests until I built a decoder and made
the transmission a lot faster (probably adding tones and making it 5 bits
wide), which shouldn't be hard
On Mon, Aug 8, 2016 at 5:06 PM, Justin Newton 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
Sorry about the last email, I deleted the repository to get rid of the BIP
number to prevent confusion. The correct address is
https://github.com/Dako300/BIP
This is my BIP idea: a fast, robust, and standardized way for representing
Bitcoin addresses over audio. It takes the binary representation
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),
24 matches
Mail list logo