dkales / picnic_m4 Goto Github PK

Hello, while I was trying to integrate your version of Picnic3-L1 in a project, using STM32Cube IDE, I noticed a mismatch on the Stack Memory that my IDE reports and the one that is reported on your bencharmks-gregz-may27.md here. It actually reports the same memory for opt and for opt-mem variants.

I found out that on your README.md file you are stating:

opt-mem: similar to opt, but makes some tradeoffs to reduce memory even further, such as not storing the whole Merkle tree in memory, and recomputing it as needed. Currently, only signing is optimized to use less RAM, verification is the same as opt. None of the changes break compatibility with the Picnic specification.

So it makes sense on the bencharmks-gregz-may27.md, the Memory Evaluation of opt and opt-mem to be the same except the signing operation.

In bencharmks-gregz-may27.md we see that the Sign operation reports less memory BUT we see the same on the Verify operation too:

Signature Schemes

Scheme	Implementation	Key Generation [bytes]	Sign [bytes]	Verify [bytes]
picnic3l1	opt	820	69,228	87,812
picnic3l1	opt-mem	828	24,676	32,436

Is this a typo or is there an actual memory optimization on the Verify operation that I am missing?

Thank you in advance,
George