pull down to refresh

0 sats \ 9 replies \ @optimism 9h \ parent \ on: Privacy in Bitcoin, state of the practice privacy
the BlocSci tool has a collection of known WabiSabi flaws
this BlockSci?
write
preview
10 sats \ 8 replies \ @fd055dcc2f 8h
there was a recent fork https://github.com/crocs-muni/blocksci
reply
100 sats \ 1 reply \ @kruw 6h
Yep, this fork was used for the research I posted about here: #1264872
reply
0 sats \ 0 replies \ @optimism 6h
Crap, I missed that post, thanks for linking.
I fixed my error and subscribed to your posts.
reply
0 sats \ 5 replies \ @satsbridge OP 8h
Yes they did a good job about updating it. Oxt.me was a great too, hopefully someone will make something similar but using BlockSci.
reply
105 sats \ 4 replies \ @optimism 8h
I've browsed that fork. What flaw exactly?
reply
21 sats \ 3 replies \ @satsbridge OP 7h
A set of CJ-related heuristics implementations is here.
https://github.com/crocs-muni/blocksci/blob/d30dd09c8908fe0bf27fe9115bac1917d820d6c8/src/heuristics/tx_identification.cpp#L601
reply
105 sats \ 2 replies \ @optimism 6h
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?
reply
0 sats \ 0 replies \ @satsbridge OP 6h
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.
reply
0 sats \ 0 replies \ @optimism 6h
ps: @kruw you might want to look at this lol
reply