API mismatch

[bomanaps]

Commit 825c1fc fails to compile due to API mismatch with the fiat-shamir crate.

Error

error[E0107]: struct takes 2 generic arguments but 3 generic arguments were supplied
--> crates/utils/src/wrappers.rs:17:76
|
17 | pub fn build_prover_state<EF: ...>(padding: bool) -> ProverState<KoalaBear, EF, MyChallenger>
| ^^^^^^^^^^^ expected 2 generic arguments

Root Cause

The fiat-shamir crate changed its API in commit fb6168e (Dec 13, 2025):

• Old: ProverState<F, EF, Challenger> with new(challenger, padding)
• New: ProverState<EF, P> with new(permutation)

The wrappers.rs file still uses the old API.

Affected File

crates/utils/src/wrappers.rs - lines 7-24

[bomanaps]

Hello @Kayden-ML I think this is also the reason why your ci is failing?

[TomWambsgans]

Hi! Is it fixed now? (Kayden told me his issue was now solved)

[MegaRedHand]

I had this issue too in lambdaclass/ethlambda#42, when trying to add leanMultisig as a dependency. I'm still trying to fix it.

[bomanaps]

I had this issue too in lambdaclass/ethlambda#42, when trying to add leanMultisig as a dependency. I'm still trying to fix it.

Please let me know if you’re able to as am still seeing this and I also traced the broken code which is this https://github.com/leanEthereum/leanMultisig/blob/825c1fc22bad0bfbdb3a656d209944f38d8733fa/crates/utils/src/wrappers.rs#L7-L25

And the this https://github.com/leanEthereum/fiat-shamir/blob/d80da40a76c00aaa6d35fe5e51c3bf31eaf8fe17/src/prover.rs#L15

So far this is my findings the commit hash but am getting an error from this commit 825c1fc devnet2 branch uses multilinear-toolkit from lean-vm-simple, which has fiat-shamir with 2-param ProverState. But wrappers.rs still has 3-param code.

Please @TomWambsgans if you can please clarify me on this, thank you

[Kayden-ML]

Hi! Is it fixed now? (Kayden told me his issue was now solved)

Ya this issue we where having in ream has been resolved

[MegaRedHand]

@Kayden-ML Just a heads-up, but even though ream's master branch compiles, running cargo update && cargo check --workspace fails. This issue seems to be due to an unpinned dependency not following semver, so that cargo doesn't know how to correctly resolve the version. Any new user of leanMultisig will see the compilation errors, since they don't yet have a lockfile with the correct versions in place.

[Kayden-ML]

@Kayden-ML Just a heads-up, but even though ream's master branch compiles, running cargo update && cargo check --workspace fails. This issue seems to be due to an unpinned dependency not following semver, so that cargo doesn't know how to correctly resolve the version. Any new user of leanMultisig will see the compilation errors, since they don't yet have a lockfile with the correct versions in place.

Ok thank you for the heads up

[MegaRedHand]

I managed to make it compile by replacing our lockfile with leanMultisig's. In case anyone else needs a fix for this.

I'm not sure how the dependencies changed, so I didn't attempt to fix the compilation issues. The errors can be reproduced in leanMultisig by running cargo update followed by cargo check.

[TomWambsgans]

@Kayden-ML Just a heads-up, but even though ream's master branch compiles, running cargo update && cargo check --workspace fails. This issue seems to be due to an unpinned dependency not following semver, so that cargo doesn't know how to correctly resolve the version. Any new user of leanMultisig will see the compilation errors, since they don't yet have a lockfile with the correct versions in place.

You're right, my mad. After merging some branches in the other repositories leanMultisig depends on, I don't see this issue anymore. If you confirm that's also fixed for you I will close this issue.

[bomanaps]

@Kayden-ML Just a heads-up, but even though ream's master branch compiles, running cargo update && cargo check --workspace fails. This issue seems to be due to an unpinned dependency not following semver, so that cargo doesn't know how to correctly resolve the version. Any new user of leanMultisig will see the compilation errors, since they don't yet have a lockfile with the correct versions in place.

You're right, my mad. After merging some branches in the other repositories leanMultisig depends on, I don't see this issue anymore. If you confirm that's also fixed for you I will close this issue.

please can i get the commit hash for this cause our ci is failing because of this - is this the right has 483bff0 ?

[TomWambsgans]

Could you please try with the latest one (from the devnet2 branch): e447413

[bomanaps]

Could you please try with the latest one (from the devnet2 branch): e447413

Okay will do that should I also update the pm repo with this so all other clients are aware?

[TomWambsgans]

I believe it's already up to date. Is your issue 100% resolved now?