-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Comments:BIP 0047
Poorly designed. I recommend against implementing this version. --Luke Dashjr, 2016-12-23
I support the goal. But this proposal is not well designed, and the way that it has been implemented in practice is by clients sending their scanning codes to third party servers; linking all of their payments-- a design flaw that was called out early in this (and related proposals lives). --Greg Maxwell, 2017-03-14
No comment as to design. However, I think that there is a typo in the Identity section. A sentence reads "For example, the payment code created represented by (m / 47' / 0' / 0') is part of the account represented by (m / 44' / 0' / 0')." I think that the account should not have a hardened final key pair. It should read "(m / 44' / 0' / 0)" instead. -- Paul Imthurn, 2018-8-15
I regularly use this feature on Samourai Wallet on Android, Sparrow wallet on Desktop and Stack Wallet on iOS. From a user perspective the feature is very valuable and removes a great deal of friction when making payments between peers and trying to avoid address reuse. -- Ape Mithrandir, 2023-04-08
📌 Final Note from the Researcher:
This report is submitted as an initiative to raise security awareness and improve the implementation quality of the BIP-39 standard across different languages and platforms. All observations are based on scientific analysis and public data without compromising any privacy or breaching any system.
I welcome all your feedback and comments, and look forward to collaborating with the developer and research community to ensure a more secure environment for blockchain technology users.
Best regards, Okba [GUIAR OQBA] Cybersecurity Researcher