Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 0E159412 for ; Wed, 15 Mar 2017 04:03:57 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 87817106 for ; Wed, 15 Mar 2017 04:03:56 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:a45d:823b:2d27:961c]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 3AF7138A3120 for ; Wed, 15 Mar 2017 04:03:44 +0000 (UTC) X-Hashcash: 1:25:170315:bitcoin-dev@lists.linuxfoundation.org::ydp4oWOMZF/lkL+y:a3wpX From: Luke Dashjr To: Bitcoin Protocol Discussion Date: Wed, 15 Mar 2017 04:03:40 +0000 User-Agent: KMail/1.13.7 (Linux/4.4.45-gentoo; KDE/4.14.28; x86_64; ; ) X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201703150403.43194.luke@dashjr.org> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: [bitcoin-dev] Payment address tokens 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, 15 Mar 2017 04:03:57 -0000 I've put together a fairly incomplete BIP draft for a new stateless address format that aims to address the many shortcomings of current addresses, including: - Current addresses special-case specific transaction types, and have needed sender-side upgrades for new types. - Outputs are produced which cannot be distinguished from disguised data storage, making spam detection harder. - Privacy is severely harmed by reuse of addresses. - Funds can be lost due to (accidental or intentional) reuse of very old addresses. https://github.com/luke-jr/bips/blob/bip-genaddr/bip-genaddr.mediawiki A downside of this approach is that parsing addresses to outputs can be complicated, but this is resolvable by writing libraries for popular languages. Thoughts on how it might be improved, before I get too deep into the current design? Luke