feat: MIMC security considerations

[Soleimani193]

feat: MIMC security considerations

[giuliop]

In their FAQ the MiMC authors comment against using a Miyaguchi-Preneel structure and add that if going that route they would recommend increasing the number of rounds.
The number of rounds in gnark's implementation matches the original paper and does not follow the recommendation to increase it with a Miyaguchi-Preneel structure.

What is the line of thinking followed to make these choices in gnark?

[ivokub]

I am not sure, I haven't been involved in the implementation, but I would assume the main reasoning would have been to have compatibility with alternative libraries. Length-extension attacks are somewhat mitigated as MiMC is mostly used for in-circuit hashing (and we have the native version in gnark-crypto for compatibility), where the input lengths are fixed.

But I do agree that the issue and I think it needs some consideration. There are several parallel lines of work regarding algebraic hashing:

• adding interfaces which are more natural to algebraic hashing #448
• adding Poseidon hash #494
• implementing SAFE API Consensys/gnark#1122
• MiMC parametrization #221
• etc

I would definitely add the points raised by @Soleimani193:

• The user should be warned about the use of MIMC hash based on Miyaguchi-Preneel structure.
• The implementation of MIMC based on Sponge structure would be very helpful