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 5B82782B for ; Wed, 10 Aug 2016 11:43:01 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-yb0-f172.google.com (mail-yb0-f172.google.com [209.85.213.172]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D8FCC1B9 for ; Wed, 10 Aug 2016 11:42:59 +0000 (UTC) Received: by mail-yb0-f172.google.com with SMTP id x196so13124780ybe.1 for ; Wed, 10 Aug 2016 04:42:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=lukuvx6fjk3WCG4EW9/nMZbbslaK5jqnrVpAyJun8Rg=; b=yNMZWUevSb1puePyDbqzaPZhStMEZFTJTKlK9sW3J43YaNsllDdymeziJ5XtlA82+2 xyWd1VHkZ9VqppZ8RvDbhAE8huAQyg6BoUx3uVZ0Ck+pbBzC5SVT9ULbW4AMznIujw4A CBil/cNWPz7VDF9HNUs8r7R+dYr1mhk68+7jyAYU7RgqXw+hywYJbVGlIUpLEPd8xxI0 eCD+2rILNUDY5u+dm3gI8tYpdfHP8t1MH2Ev2mn+17wbirjV8ktRH5xT3UXCA1/bfoLs 5WYUlFgbSyu5cSVfYuGDEbb+BT5qTQm6DPLa/vyZX8wv/hSn1mm0wmDs8i1/d9YKgy+Y 3xeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=lukuvx6fjk3WCG4EW9/nMZbbslaK5jqnrVpAyJun8Rg=; b=NeHRiYdwspIfRpZP78pLpjsKbn5rwsjc0X+RG/1AKSiOOQ8G5i78U9HhA91vXZQwbR 513rx/4qSr/DjR9x7pf+vLYvSzNirdxVbTnDN3UDon+YF3x7X38BMiwBQtRlV9ScpJEs zpPMEZA6VdUuS427gR37NYFGSmE4voHUpyVpOI7t6Ke/Yapd6DShpdUVLVUb3ASXuEBa pRWbD6sWzSMh01L5ZVJwJXU65G8CZEqyuY9EmgyIs2cY78EGdM5LxvqEa6L8lI1uOg5f 4Y6z9HfJOQQ/XGF2tUSBs0Ll+4yy/H3m91m9fY0mejwwkQNgYnecRMlzGTsakyusNSam RfJA== X-Gm-Message-State: AEkoouv6rnJ+FTKO/BQ0r+B9uUkWc5ZID3kvjFOUCs/tQ9UHaXvIcp4GWrdI9EZ721KxkmblYTPTPBPNbmXnaQ== X-Received: by 10.37.210.197 with SMTP id j188mr2239458ybg.52.1470829378055; Wed, 10 Aug 2016 04:42:58 -0700 (PDT) MIME-Version: 1.0 Sender: earonesty@gmail.com Received: by 10.37.88.214 with HTTP; Wed, 10 Aug 2016 04:42:57 -0700 (PDT) In-Reply-To: References: From: Erik Aronesty Date: Wed, 10 Aug 2016 07:42:57 -0400 X-Google-Sender-Auth: INc0M27_LkyxGTrN9-aiShBfTK0 Message-ID: To: Tier Nolan , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary=94eb2c0655029abd610539b62679 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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 11:43:01 -0000 --94eb2c0655029abd610539b62679 Content-Type: text/plain; charset=UTF-8 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 > > --94eb2c0655029abd610539b62679 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
NOTE:

Addresses aren't really meant to be= broadcast - you should probably be encoding BIP32 public seeds, not addres= ses.=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 required- TXT record contains addr:[<bip32-pub-seed>]

Then you can just say, in the podcast, "Send your bitcoin donations= to rick@q32.com".=C2=A0=C2=A0 And= you can link it to your email address, if your provider lets you set up a = TXT record.=C2=A0=C2=A0 (By structuring the TXT record that way, many exist= ing email providers will support the standard without having to change anyt= hing.)

This works with audio, video, we= b 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 consider= ed CDMA?=C2=A0 This has the nice property that it just sounds like noise.= =C2=A0 The codes would take longer to send, but you could send multiple bit= s at once and have the codes orthogonal.

_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev


--94eb2c0655029abd610539b62679--