Zook : Parameter Selection

[ocdbytes]

Changes :

• Added proper param selection.
  • All paths for param selection are protected using type safety.
  • Any individual config cannot be modified within param selection.
  • Added analytical bit helper for each sub protocol param selection which also accounts for security bits.
  • Derived bounds for our modfied params can be found here : Derived Bounds.
  • All the bounds are verified by @WizardOfMenlo
• Added Mode enum for each sub protocol for cleaner branching of the execution flow.
• POW Grinding added for all the sub protocols.
• Added getters instead of pub access of config fields for safety.

Tests :

• Added proptests for each param selection path and protocol.

This PR was squashed from 47 commits during conflict resolution against PR #251 (merged to main)
Commit history maintained in personal fork.

[shreyas-londhe]

@ocdbytes Can you please resolve the merge conflicts on this PR? I'm reviewing it and we are planning to merge it by this week.

[zkfriendly]

Hey @shreyas-londhe, this branch did not have any conflicts with main before merging buffer abstraction. I opened a PR to this branch here ocdbytes#11, which adds buffer abstraction. Merging it will make this branch conflict free again. cc @ocdbytes

[ocdbytes]

Thanks @zkfriendly I have merged your PR now there are no conflicts. I skimmed through the changes will go through them properly tomorrow to see if there is anything to be changed.
cc @shreyas-londhe

[codspeed-hq]

Merging this PR will not alter performance

✅ 10 untouched benchmarks
⏩ 22 skipped benchmarks¹

---

_{Comparing ocdbytes:aj/zk-whir-3-3 (3f019f1) with main (10aa7d0)}

Footnotes

1. 22 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[BornPsych]

Can ProtocolConfig derive Serialize/Deserialize? It's #[derive(Clone, Debug)] today, so nothing downstream can embed it in a serialized scheme.

Context for why I'm asking: ProveKit builds its Fiat-Shamir domain separator by serializing the whole scheme (WHIR config included) and hashing that. whir::Config already handles it, with Serialize/Deserialize and #[serde(bound = "")] for the embedding generic. Once this stack has a prover/verifier runtime and replaces whir::Config as what schemes carry, ProtocolConfig will need the same.

It's not a one-liner though. RoundConfig, RoundMode, MaskOracleConfig, BasecasePlan in this file, plus Solved and CodeSwitchConfig, all need it too, and none of them derive it yet (SecuritySpec and TuningSpec already do). The embedding-generic ones want #[serde(bound = "")] like whir::Config.

[ocdbytes]

Hey @BornPsych
I have added these derives in wiring PR (next PR). Ig missed it here in this PR