From: Luke Dashjr <luke@dashjr.org>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Payment address tokens
Date: Wed, 15 Mar 2017 04:03:40 +0000 [thread overview]
Message-ID: <201703150403.43194.luke@dashjr.org> (raw)
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
reply other threads:[~2017-03-15 4:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201703150403.43194.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox