From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8643492 for ; Wed, 10 Aug 2016 22:31:28 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com [209.85.220.179]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F346E217 for ; Wed, 10 Aug 2016 22:31:27 +0000 (UTC) Received: by mail-qk0-f179.google.com with SMTP id t7so58383602qkh.0 for ; Wed, 10 Aug 2016 15:31:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=QwCyChX8A7A9XwRzk18dHYUEE5+RxHAmh+ZZ7pf5v74=; b=QDvDZToDUleFotoVwuapkHAz6Ghoqamki1Nof/F2iCNRd9hUFioewW4OW4HphEEMrR hmzbD9oq/+J5jdetsEojqRGONzAia/cAuDhz2h7par/Dqnc4E9JQrbDcigSjOwOcdxAi tP3q6NImEMnnajugO7Bld7xv9MksA7r8XZv1PXQIR+i1X+utdZUlCbk3uiIrRF2dqhZ6 b0/3cTDKTGkFLulU09uC4qtx7TYHRyeLvGwXt+NgguAbdqf5znepmUXbbqt24RRjSCyf fsxlPt8qzqXqWKnTVtY93oOPy9IT7jamJnMSkm3vvhkK+szDrFcDSwU7CrDa37jWmEPK tKsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=QwCyChX8A7A9XwRzk18dHYUEE5+RxHAmh+ZZ7pf5v74=; b=Eyua3Fk5DwOy4XmapeWTXV0UcYO1rHGnmheQ7fJt0L5RFr5FTYUjBGSKhV9JwygNIe 72zhzlliOxXyJYjfBhnVNJXYHwCKPPxCGKFaTqaghkmTwwlNYydFU4Mg0yhYowIxmbaN lXkzcgt8dIzTO3GnWuWGypUQowkr0q8d0DcKAAdv8F+829o3CrroPIkk4jgHSL1Ldh83 afrKjyAJqX6JXfSW4Ga+qpGgrwGr28mTzNo12o6MYdZgWs9yjTSAtpIka4pKuwgRt46o Jii7avNF1s54p74tIRqzwkWpiWlC4BfnWlsOgakQ6qN3X0rMx7EWsxk6P5wCWgW8g36L 5LhQ== X-Gm-Message-State: AEkoousAk9SZkJ7eVUR2l+mMG0n7nEEq+Z56LpWG5aTqJT/KbpyJuAQJ/OoJXpJwi4366SdUUbFgRQh/8XwNFg== X-Received: by 10.55.36.131 with SMTP id k3mr7266753qkk.86.1470868287150; Wed, 10 Aug 2016 15:31:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: James MacWhyte Date: Wed, 10 Aug 2016 22:31:16 +0000 Message-ID: To: Daniel Hoffman , Bitcoin Protocol Discussion , Pieter Wuille Content-Type: multipart/alternative; boundary=001a114533eac460a50539bf3526 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2016 22:31:28 -0000 --001a114533eac460a50539bf3526 Content-Type: text/plain; charset=UTF-8 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 to be conveyed so people could use the method for sending pub keys, payment protocol requests, or anything else developers might want to make use of. I'm guessing some sort of data-over-audio standard already exists? In which case the bip could just say "we use [standard] to convey any bitcoin-related data". On Wed, Aug 10, 2016, 10:55 Daniel Hoffman via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > 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 >> 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 seen it (= anyone >> who ever pays you through it) can identity all payments to _any_ >> address derived from that seed. >> >> -- >> Pieter >> _______________________________________________ >> 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 > --001a114533eac460a50539bf3526 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I agree, audio-based transference isn't really great f= or a podcast or radio ad. It could be used to transmit payment details betw= een phones that don't have cameras, though. I think it would be better = to define a standard for transmitting information over audio, but not defin= e what information is to be conveyed so people could use the method for sen= ding pub keys, payment protocol requests, or anything else developers might= want to make use of.

I'm guessing some sort of data-over-audio standar= d already exists? In which case the bip could just say "we use [standa= rd] to convey any bitcoin-related data".


On Wed, Aug 10, 2016= , 10:55 Daniel Hoffman via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrot= e:

thats how i thoug= ht it worked originally, but im not well versed on that, so i took his word= for it


On Aug 10, 2016 1= 2:38 PM, "Pieter Wuille via bitcoin-dev" <bitcoin-dev@lists.li= nuxfoundation.org> wrote:
On Wed, Aug 10, 2016 at 7:28 PM, Erik Aronesty via bitcoin-de= v
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> By sending a public seed,=C2=A0 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 seen it (=3D anyone
who ever pays you through it) can identity all payments to _any_
address derived from that seed.

--
Pieter
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--001a114533eac460a50539bf3526--