Quote from: CryptoBroker012 on Today at 11:10:01 AM

COULD YOU ALREADY UPDATE

Hi "CryptoBroker"

This is not an attack on Beam, nor is it anything that wasn't known about Mimblewimble from the onset. In fact, this is why Beam is designed the way it was, to include decoy outputs, and obfuscate the transaction graph.

You can find our reply here to the above piece here:
https://medium.com/beam-mw/will-breaking-mimblewimbles-privacy-model-work-on-beam-9125bc2ee863

The author, was called out, and encouraged to recreate the "attack" (It's not really an attack at all) on Beam, and didn't take up the challenge. Since the article came out, Beam has also added LelantusMW which utilises a shielded pool to further increase privacy, and allow for an anonymity set of 64k.

All of this has been updated, already. If you have any further questions, feel free to let us know.