Stack Exchange Network
Stack Exchange network consists of 181 Q&A communities including
Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Monero Stack Exchange is a question and answer site for developers and users of the secure, private and untraceable cryptocurrency Monero. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
The best answers are voted up and rise to the top
6 years, 10 months ago
This question is
. It is not currently accepting answers.
This question does not appear to be about Monero cryptocurrency, within the scope defined in the
ShadowCash uses traceable ring signature to anonymize the sender of a transaction. However, these were originally implemented incorrectly, resulting in a partial de-anonymization of ShadowCash from their first implementation until February 2016 by Monero Research Labs researcher, Shen Noether. wiki
From the technical perspective, how was Shadowcash's implementation of ring signatures fixed which prevented the partial de-anonymization of it? What was the fix and by whom was it performed?
Jul 19, 2016 at 23:47
1,563 2 2 gold badges 14 14 silver badges 25 25 bronze badges
This is incorrect.
The original implementation of ring signatures is not thought to be faulty.
The original implementation of ring signatures is not from Shadowcash, but from Bytecoin. Shadowcash implemented their own version of it, buggily.
So Shen did not fix ring signatures, though he did find the fault in Shadowcash's reimplementation. I believe Shadowcash eventually fixed their bug after claiming this was FUD.
https://shnoe.wordpress.com/2016/02/11/de-anonymizing-shadowcash-and-oz-coin/ for the details, and https://github.com/ShenNoether/Deanon for the deanonymization code.
Jul 20, 2016 at 7:26
34.8k 2 2 gold badges 55 55 silver badges 122 122 bronze badges
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our
Accept all cookies
Necessary cookies only