Following the pivot away from Poseidon for L1, I have been trying to work out from public material which byte-oriented hash leanVM is heading toward, and I could not.
What I can see from the repos:
leanVM exposes POSEIDON, DOT_PRODUCT and MULTILINEAR_EVAL. No SHA or BLAKE instruction.leanVM-b is a 192-bit binary field on WHIR/Ligerito and already carries BLAKE2S, benchmarked at 434,176 compressions/s.
Two questions:
- Which hash or hashes are expected to become instructions in leanVM?
- Is
leanVM-b the intended path, or an experiment running alongside leanVM? Byte-oriented hashes are cheap in a binary field and expensive over Koala-Bear, so from the outside these look like the same question, but I would rather ask than assume.
Happy to help with implementation or spec work on whichever hashes end up in scope.
Following the pivot away from Poseidon for L1, I have been trying to work out from public material which byte-oriented hash leanVM is heading toward, and I could not.
What I can see from the repos:
leanVMexposesPOSEIDON,DOT_PRODUCTandMULTILINEAR_EVAL. No SHA or BLAKE instruction.leanVM-bis a 192-bit binary field on WHIR/Ligerito and already carriesBLAKE2S, benchmarked at 434,176 compressions/s.Two questions:
leanVM-bthe intended path, or an experiment running alongsideleanVM? Byte-oriented hashes are cheap in a binary field and expensive over Koala-Bear, so from the outside these look like the same question, but I would rather ask than assume.Happy to help with implementation or spec work on whichever hashes end up in scope.