pull down to refresh
the BlocSci tool has a collection of known WabiSabi flaws
there was a recent fork
https://github.com/crocs-muni/blocksci
Yep, this fork was used for the research I posted about here: #1264872
Crap, I missed that post, thanks for linking.
I fixed my error and subscribed to your posts.
Yes they did a good job about updating it.
Oxt.me was a great too, hopefully someone will make something similar but using BlockSci.
I've browsed that fork. What flaw exactly?
A set of CJ-related heuristics implementations is here.
That's just the heuristics of detecting whether a tx is a wasabi2 coinjoin. There's also a isLongDormantInRemixes above that that attempts to identify based on the time between remixes whether the cj is initiated from trezor suite.
There are some deeper heuristics defined here which are about as far as you'd get. But are these weaknesses in the wasabi protocol? Or are they patterns that can be broken by behavior?
You are right these are heuristics. However they may be amended with data from other sources.
Wasabi was great to address issues of WabiSabi in multiple versions.
Yes. It was my mistake.
However, the BlocSci tool has a collection of known WabiSabi flaws when it comes to chain analysis. Albeit I am personally do not consider it as flawed protocol unlikely to JoinMarket for which my own analysis indicates that Fidelity bonds are ineffective and there is high likability that the orderbook is full of Sybills.