public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alfred Hodler <alfred_hodler@protonmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP proposal] Private Payments
Date: Mon, 11 Jul 2022 10:28:40 +0000	[thread overview]
Message-ID: <7MZupPo-je8mhyxtw-sPQ19zypYdoXmh93RoVCLVZ_yXo9bEnUChMFjKU6E4W9gpLXbGiHMlbxY05K62BCzrYuaiPVp_7YdxM1_J3ToSnGU=@protonmail.com> (raw)
In-Reply-To: <rH1Js_T_UWcAg9lS9NDw_Qb6Js5bgs8rPILej69BjqsEZcJZwsvHhZRilkkOQZRGXabai63hrGgbTP2Yk99ojKEN6fU6HT4TmukiafqiKjo=@protonmail.com>

Update: Bob doesn't have to watch all address types he's advertising. When notifying Bob, Alice will pick one address type out of the ones Bob is advertising and include it in the notification. That way even if Bob's wallet accepts many address types, he still doesn't have to watch all of them for each Alice.

The previous spec reads:

> Alice then constructs a 72-byte OP_RETURN output whose value is set to `BIPXXXX + notification + N_Alice` (`+` is concat) and sends it in a transaction containing no other outputs (XXXX to be replaced once a BIP number is assigned).

We can extended the payload to 73 bytes and define it as: `BIPXXXX + notification + N_Alice + address_type`, where `address_type` is a single byte containing the desired address type index (1 out of 16, limited by Bob's payment code). If Alice ever wants to start sending to a different address type, she can simply re-notify Bob and Bob will switch to a new address type in the case of Alice.

Alfred



      parent reply	other threads:[~2022-07-11 10:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 18:17 [bitcoin-dev] [BIP proposal] Private Payments Alfred Hodler
2022-06-27 20:20 ` Bryan Bishop
2022-06-27 20:35   ` Ruben Somsen
2022-06-28 12:40   ` Alfred Hodler
2022-06-27 20:30 ` Ruben Somsen
2022-06-28 12:35   ` Alfred Hodler
     [not found]     ` <PS2P216MB10894F1EE83AFA648003C6339DBF9@PS2P216MB1089.KORP216.PROD.OUTLOOK.COM>
2022-07-05  9:38       ` Alfred Hodler
2022-06-28 23:33   ` Peter Todd
2022-06-29 22:33 ` Clark Moody
2022-07-01 12:41   ` Alfred Hodler
2022-07-01 17:37     ` Christopher Allen
2022-07-11 10:28 ` Alfred Hodler [this message]

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='7MZupPo-je8mhyxtw-sPQ19zypYdoXmh93RoVCLVZ_yXo9bEnUChMFjKU6E4W9gpLXbGiHMlbxY05K62BCzrYuaiPVp_7YdxM1_J3ToSnGU=@protonmail.com' \
    --to=alfred_hodler@protonmail.com \
    --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