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 (_<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".   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