MIME-Version: 1.0
From: El_Hoy <eloyesp@gmail.com>
Date: Thu, 22 Sep 2022 00:06:50 -0300
Message-ID: <CAPapNH28iCxEcTOKt3YC+zuZzxbM=AudbbYByjS3aUZAgFHUag@mail.gmail.com>
To: Bitcoin DEV <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000ed9ec505e93b5ad6"
Subject: [bitcoin-dev] RFC for a BIP32 recurrent address derivation scheme
Precedence: list

--000000000000ed9ec505e93b5ad6
Content-Type: text/plain; charset="UTF-8"

There is a known issue on bitcoin, that is that every transaction requires
a new address to prevent address reuse, making it uncomfortable to make
recurring payments, as every payment requires a new off-chain interaction.
A scheme is already mentioned on the [on the BIP32 itself][1], but it
cannot be implemented as is.

Here I propose a scheme that follows the structure described on [BIP44]
that should make it possible to send recurring payments using a single
offline interaction.

The proposed scheme is:

    master / purpose' / coin_type' / contact' / index

Where the definitions of all the levels follow BIP44, except for `contact`
that is described below.

Example usage: Bob wants to make recurring payments to Carol, so he asks
her for a _contact address_, that is, an extended public key.

Bob can use that public key to generate multiple derived addresses to make
multiple recurring payments to Carol, the contact address is stored
off-chain, anyone inspecting the chain will just see normal transactions
on-chain.

## Considerations

[BIP47] tries to solve the same issue, but the solution is more complex and
involves more on-chain transactions that involve data, this implementation
simpler and requires less work to implement.

Also, the derivation path might need some adjustments for different address
types on bitcoin.

Finally, this only works in a single direction and does not make it
possible for Carol to send anything to Bob, as it would require Bob sending
her a contact address.

## Advantages

A positive side effect of using this, is that Bob can choose to send
payments to Carol using multiple outputs, giving him more privacy.

Also, those payments can be easily labeled by the receiving wallet, as they
are received.

Regards.

### References

[1]:
https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#recurrent-business-to-business-transactions-nmih0
[BIP47]: https://github.com/bitcoin/bips/blob/master/bip-0047.mediawiki
"Reusable Payment Codes for Hierarchical Deterministic Wallets"
[BIP43]:
https://github.com/bitcoin/bips/blob/master/bip-0043.mediawiki#Purpose

--- Eloy

--000000000000ed9ec505e93b5ad6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">There is a known issue on bitcoin, that is that every tran=
saction requires a new address to prevent address reuse, making it uncomfor=
table to make recurring payments, as every payment requires a new off-chain=
 interaction. A scheme is already mentioned on the [on the BIP32 itself][1]=
, but it cannot be implemented as is.<br><br>Here I propose a scheme that f=
ollows the structure described on [BIP44] that should make it possible to s=
end recurring payments using a single offline interaction.<br><br>The propo=
sed scheme is:<br><br>=C2=A0 =C2=A0 master / purpose&#39; / coin_type&#39; =
/ contact&#39; / index<br><br>Where the definitions of all the levels follo=
w BIP44, except for `contact` that is described below.<br><br><div>Example =
usage: Bob wants to make recurring payments to Carol, so he asks her for a =
_contact address_, that is, an extended public key.</div><div><br></div>Bob=
 can use that public key to generate multiple derived addresses to make mul=
tiple recurring payments to Carol, the contact address is stored off-chain,=
 anyone inspecting the chain will just see normal transactions on-chain.<br=
><div><br></div><div>## Considerations</div><div><br></div><div>[BIP47] tri=
es to solve the same issue, but the solution is more complex and involves m=
ore on-chain transactions that involve data, this implementation simpler an=
d requires less work to implement.<br></div><div><br></div><div>Also, the d=
erivation path might need some adjustments for different address types on b=
itcoin.<br></div><div><br></div><div>Finally, this only works in a single d=
irection and does not make it possible for Carol to send anything to Bob, a=
s it would require Bob sending her a contact address.</div><div><br></div><=
div>## Advantages<br></div><br><div>A positive side effect of using this, i=
s that Bob can choose to send payments to Carol using multiple outputs, giv=
ing him more privacy.</div><div><br></div><div>Also, those payments can be =
easily labeled by the receiving wallet, as they are received.</div><div><br=
></div><div>Regards.</div><div><br></div>### References<br><div><br></div><=
div>[1]: <a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0032.me=
diawiki#recurrent-business-to-business-transactions-nmih0">https://github.c=
om/bitcoin/bips/blob/master/bip-0032.mediawiki#recurrent-business-to-busine=
ss-transactions-nmih0</a><br></div>[BIP47]: <a href=3D"https://github.com/b=
itcoin/bips/blob/master/bip-0047.mediawiki">https://github.com/bitcoin/bips=
/blob/master/bip-0047.mediawiki</a> &quot;Reusable Payment Codes for Hierar=
chical Deterministic Wallets&quot;<br>[BIP43]: <a href=3D"https://github.co=
m/bitcoin/bips/blob/master/bip-0043.mediawiki#Purpose">https://github.com/b=
itcoin/bips/blob/master/bip-0043.mediawiki#Purpose</a><br><br>--- Eloy</div=
>

--000000000000ed9ec505e93b5ad6--