Ça fait plusieurs fois que je vois passer ça sur le forum et ça semble très intéressant. Une avancée qui va dans le bon sens!
![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
Les adresses Silent Payments qui commencent par "sp1",sont faites pour être réutilisables tout en préservant votre vie privée.
Chaque dépôt fait sur une adresse sp1 est redirigé vers une nouvelle adresse.
Pour en savoir plus :
https://bitcointalk.org/index.php?topic=5400363.0 et
https://github.com/bitcoin/bips/blob/master/bip-0352.mediawikiWe aim to present a protocol which satisfies the following properties:
No increase in the size or cost of transactions
Resulting transactions blend in with other bitcoin transactions and can't be distinguished
Transactions can't be linked to a silent payment address by an outside observer
No sender-receiver interaction required
No linking of multiple payments to the same sender
Each silent payment goes to a unique address, avoiding accidental address reuse
Supports payment labeling
Uses existing seed phrase or descriptor methods for backup and recovery
Separates scanning and spending responsibilities
Compatible with other spending protocols, such as CoinJoin
Light client/SPV wallet support
Protocol is upgradeable
Pour le moment seuls quelques wallets sont compatibles (Cake, Silentium, Blue wallet, Seedsigner), mais il semblerait que d'autres wallets ont pour projet d'ajout SP prochainement :
Foundation Passport has also announced that they are planning to introduce support for BIP351 and Silent Payments. They plan to integrate it with both Envoy and the Passport hardware wallet in the future. Of course, it's not added yet, but just something for you to keep an eye on.
Apparement ça sera bientôt dans Bitcoin Core aussi :
This almost made it to Bitcoin Core's next major release v28 but was dropped from the priority list to be replaced by another update.
There's a "
Tracking Issue" for those who want to see when this will get implemented in the reference client, currently at 4/15 tasks completed.
Link:
BIP352 tracking issue (issue# 28536)