public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: Justus Ranvier <justus@openbitcoinprivacyproject.org>,
	"Bitcoin Dev" <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin-development] Reusable payment codes
Date: Thu, 22 Oct 2015 05:53:59 +0000	[thread overview]
Message-ID: <201510220554.00367.luke@dashjr.org> (raw)

On Friday, April 24, 2015 8:00:46 PM Justus Ranvier wrote:
> This link contains an RFC for a new type of Bitcoin address called a
> "payment code"

Sorry for the late review. I'm concerned with the "notification address" 
requirement, which entails address reuse and blockchain spam. Since it entails 
address reuse, the recipient is forced to either leave them unspent forever 
(bloating the UTXO set), or spend it which potentially compromises the private 
key, and (combined with the payment code) possibly as much as the entire 
wallet.

Instead, I suggest making it a single zero-value OP_RETURN output with two 
pushes: 1) a hash of the recipient's payment code, and 2) the encrypted 
payment code. This can be searched with standard bloom filters, or indexed 
with whatever other optimised algorithms are desired. At the same time, it 
never uses any space in the UTXO set, and never needs to be 
spent/mixed/dusted.

Luke


             reply	other threads:[~2015-10-22  5:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22  5:53 Luke Dashjr [this message]
2015-10-22 14:55 ` [bitcoin-dev] [Bitcoin-development] Reusable payment codes Justus Ranvier
2015-10-22 20:43   ` Luke Dashjr
2015-10-22 20:58     ` Justus Ranvier
2015-10-22 21:47       ` Luke Dashjr
2015-10-22 22:01         ` Justus Ranvier
2015-10-23  1:22       ` Peter Todd
2015-10-23 15:57         ` Justus Ranvier
2015-10-22 21:05     ` Kristov Atlas

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=201510220554.00367.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=justus@openbitcoinprivacyproject.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