04:56:58 <m-relay> <c​haserene:matrix.org> is there an up-to-date specification of the dynamic block size and penalty system?
06:59:10 <m-relay> <b​itcoiner:monero.social> how many output txs are being made in this flooding attack?
07:00:06 <m-relay> <b​itcoiner:monero.social> https://matrix.monero.social/_matrix/media/v1/download/monero.social/kZPwCHvROxrBQJWvCubHsxYi
07:00:10 <m-relay> <b​itcoiner:monero.social> is it possible to apply this table to what is going on currently?
07:00:27 <m-relay> <b​itcoiner:monero.social> this is for 16 output txs
15:58:13 <m-relay> <r​ucknium:monero.social> "is it possible to apply this table to what is going on currently?" The short answer is "no". That paper estimated the privacy impact of flooding under different parameters than what we have now. Ring size and the ratio of real outputs to suspected spam are different.