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 D8E6587A for ; Wed, 10 Aug 2016 17:28:18 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com [209.85.161.178]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 04E51266 for ; Wed, 10 Aug 2016 17:28:17 +0000 (UTC) Received: by mail-yw0-f178.google.com with SMTP id u134so29349136ywg.3 for ; Wed, 10 Aug 2016 10:28:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hoivrbMIqM2MJ6GmXY1GT8GIgKLwkcWP5m0ulFt3kpc=; b=GvWpLcoY+/NEVvku+iS+jjD0HotZQcXS195U428diw361mlD6/oCJW2pjGbLpUcg5f idhRGLnISiL4rlt5SQikq4LR4cdG0gG8lXo2lbAzGFIVzVdf8KboxhxagvKlmKGPbTjy 10hTjpL1AEsoHXhMKZY6MNXnsmlHhsXvHCs2FbPgHaFYDt0uKfQWLY/O78990Eo8Z4i9 yXHeIwKiLBxD+nydqtdGScle5NEyo6EbaKHv2vzlFJPX7ou3PxuIkhaLJtEDYECdbH5k Edsz9l1cZgFAMB+sJi70uRzEDZsTQcJVa6Vj4/mIMEjQp4y+HJASdY+223fg47qyo/6I 5wEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=hoivrbMIqM2MJ6GmXY1GT8GIgKLwkcWP5m0ulFt3kpc=; b=DyEyXo/dzhNIEkczoBVjB5pAjAsbbWKnXiBa7RJIEAt5bBYNWTj3nRVKXBt73Rw8ax xF/6cSf1vRTMK/NktVAd0WMohYK0Dm7IyyrDy4BRXCqDZjemPTjUqM88+4ptgnB6w7Fw 0b9qZXh1MNX/5cyO+ygAqsn4nIzG4iXnlHKyz0U9v1nnpLAF6cZhV4cW3NEgTLKY/wdl tbO6ElQ5DwMu1/28mP3pz0Gxz8pHRvg0oICTtwiJJHyHWiFZQyCflvUrychPgivI6SrF Ibe/2fyfQDfkG3th1VQzf/bp8WOjlwRbqPBz07b2FVv5jbWn/FD15nxGr305AsBQV4TD 2u4w== X-Gm-Message-State: AEkoouvJch/Fh2rPtBvnTL+Jb5YthUmGUvNkLTG3EDdswaxy1XJ69SZucisgY2+Slq9hGfhGbUsjK1D+0A3EUg== X-Received: by 10.129.83.193 with SMTP id h184mr3964364ywb.52.1470850097214; Wed, 10 Aug 2016 10:28:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.88.214 with HTTP; Wed, 10 Aug 2016 10:28:16 -0700 (PDT) Received: by 10.37.88.214 with HTTP; Wed, 10 Aug 2016 10:28:16 -0700 (PDT) Reply-To: erik@q32.com In-Reply-To: References: From: Erik Aronesty Date: Wed, 10 Aug 2016 13:28:16 -0400 Message-ID: To: Daniel Hoffman , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary=001a114d6f1c8ffab90539baf97d X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE 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 17:28:18 -0000 --001a114d6f1c8ffab90539baf97d Content-Type: text/plain; charset=UTF-8 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 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 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 (_..) >>> - DNS-SEC validation is *required* >>> - TXT record contains addr:[] >>> >>> 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 >>> >>> >> >> _______________________________________________ >> 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 > > --001a114d6f1c8ffab90539baf97d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

By sending a public seed,=C2=A0 there's no way for someo= ne to use the transmitted address and trace the total amount of payments to= it.


On Aug 10, 2016 1= 2:02 PM, "Daniel Hoffman via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org= > wrote:
Erik
What would be the advantages of transmitting a BIP32 = public seed, instead of a plain address?

Theo
I did= n't really think of that, but that's genius.

On Wed, Aug 10, 2016 at 6:4= 9 AM, Theo Chino via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
Another use for the audio would be for watches th= at can listen but can't use a camera (ie: Samsung S2), so sound would b= e great.

On Wed, Aug 10, 2016 at 7:42 AM, Erik Aronesty via bitcoin= -dev <bitcoin-dev@lists.linuxfoundation.org&g= t; wrote:
NO= TE:

Addresses aren't really meant to be broadcast - you should = probably be encoding BIP32 public seeds, not addresses.=C2=A0=C2=A0
OR simply:

- Send btc to rick@q32.com
- TXT record _btc.rick.q32.com is queried (_<= coin-code>.<name>.<domain>)
- DNS-SEC validation is re= quired
- TXT record contains addr:[<bip32-pub-seed>]
=
Then you can just say, in the podcast, "Send your bitco= in donations to rick@q32.= com".=C2=A0=C2=A0 And you can link it to your email address, if yo= ur provider lets you set up a TXT record.=C2=A0=C2=A0 (By structuring the T= XT record that way, many existing email providers will support the standard= without having to change anything.)

Th= is works with audio, video, web and other publishing formats... and very li= ttle infrastructure change is needed.


On Wed, Aug 10, 2016 at 6:41 = AM, Tier Nolan via bitcoin-dev <bitcoin-dev@lists.linu= xfoundation.org> wrote:
Have you considered CDMA?=C2=A0 This h= as the nice property that it just sounds like noise.=C2=A0 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



_______________________________________________
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

--001a114d6f1c8ffab90539baf97d--