Boog900 93e85c5ce6 Monero: use only the first input ring length for RCT deserialization. (#504) ... * Use only the first input ring length for all RCT input signatures. This is what Monero does: ac02af9286/src/ringct/rctTypes.h (L422) https://github.com/monero-project/monero/blob/master/src/cryptonote_basic/cryptonote_basic.h#L308-L309 This isn't an issue for current transactions as from hf 12 Monero requires all inputs to have the same number of decoys but for transactions before that Monero would reject RCT txs with differing ring lengths. Monero would deserialize each inputs signature using the ring length of the first so the signatures for inputs other than the first would have a different (wrong) number of elements for that input meaning the signature is invalid. But as we are using the ring length of each input, which arguably is the *correct* way, we would approve of transactions with inputs differing in ring lengths. * Check that there is more than one ring member for MLSAG signatures. ac02af9286/src/ringct/rctSigs.cpp (L462)		2024-01-05 00:02:16 -05:00
..
bitcoin	Correct a couple years of accumulated typos	2023-12-17 02:06:51 -05:00
ethereum	Further expand clippy workspace lints	2023-12-17 00:04:49 -05:00
monero	Monero: use only the first input ring length for RCT deserialization. (#504)	2024-01-05 00:02:16 -05:00