<k​ayabanerve:matrix.org> I wrote a summary and statement piece on MAX_INPUTS (and a few related topics): gist.github.com/kayabaNerve/dbbadf1f2b0f4e04732fc5ac559745b7

<k​ayabanerve:matrix.org> ArticMine: ofrnxmr Lyza sech1 dave.jp midipoet blurt4949 Rucknium @ anyone else who participated in this discussion recently and cares

<s​yntheticbird:monero.social> Thx for the summary.

kayabanerve: thanks for the info, i appreciate it. I'll have to try and read it a few times to grasp the intracacies. It seems MAX_IN=8 is high enough for the vast majority of users and use-cases. Not really sure i fully understand the MAX_OUT discussions to be honest.

<k​ayabanerve:matrix.org> midipoet: If MAX_OUTPUTS == 2 * MAX_INPUTS, I can send you one transaction's worth of outputs which takes you two transaction's worth of inputs to consolidate.

<k​ayabanerve:matrix.org> It's an asymmetry between cost incurred to trigger and cost incurred which could be considered a DoS.

<k​ayabanerve:matrix.org> I'm not saying it's the end of the world, it's just a poor design decision.

Oh, now i understand it better. thank you for that.

<d​ave.jp:matrix.org> Are we limiting max input to 4/8 for Transaction uniformity ?

<o​frnxmr:monero.social> > Right now, ~220 inputs can be aggregated in a single transaction

<o​frnxmr:monero.social> kayabanerve @kayabanerve:matrix.org: this isn't accurate, as we actually limit to ~2/3 of 149kb (100kb)

<o​frnxmr:monero.social> Aprox 146 inputs

<o​frnxmr:monero.social> > 97.67% of transactions used less than or exactly 8 inputs. 97.71% of transactions used less than or exactly 8 outputs.

<o​frnxmr:monero.social> Rucknium: this goes back to 2019. I thought more recent number indicated ~30% of tx were 16 out