nopara73

> i think we can just sample a subset of the blocks (or txs, but that's harder to sample uniformly), i don't expect we will gain much insight from exhaustively...

I'm ready. Starting the algorithm and praying it won't bloat my disk or be too slow. Otherwise I'll have to optimize.

Unfortunately it didn't work out. I encountered multiple issues, I'll work on them. - I realized we need to collect post mix transactions, too, because Core isn't able to walk...

Index is done and some checks suggest it's correct. I'm moving on to the metrics.

LOL, I found this unsent comment here for days. By tomorrow hopefully all the stats I described will be published. Problem that WabiSabi Solves and what statistics can prove that...

# Consolidation leads to privacy loss due to common input ownership heuristics.  # Minimum denomination prevents some people from being able to participating.  # Unmixed change leads to...

I think it'd also make sense to constrain this initial discussion between @nothingmuch @seresistvanandras @MaxHillebrand @lontivero and @molnard based on the "too many cooks spoil the soup" principle. In fact,...

# Pow2 ``` Number of users: 40 Number of inputs: 50 Number of outputs: 329 Total in: 12.80436976 BTC Fee paid: 0.00163568 BTC Size: 14307 vbyte Fee rate: 11 sats/vbyte...

I've added some more information to look at. # Summary | | outputs | avg out anon | |--------------|---------|--------------| | pow2 | 325 | 11.34 | | pow3 | 362...

Blockspace efficiency: ``` POW2 0.22, 0.34, 0.41, 0.33, 0.22, 0.37, 0.25, 0.33, 0.34, 0.22, 0.34, 0.17, 0.21, 0.31, 0.44, 0.41, 0.32, 0.28, 0.22, 0.26, 0.35, 0.32, 0.28, 0.28, 0.26, 0.38,...