Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0
Why this matters
The fuzz crate (fuzz/Cargo.toml) declares targets for lending_pool, loan_manager, and remittance_nft but lists no governance dependency or target, and multisig_governance is not even a dependency of the fuzz crate. The governance contract in multisig_governance/src/lib.rs has a non-trivial state machine (propose/approve/finalize/cancel/expire with timelock, threshold, reproposal cooldown, TTL) well suited to property fuzzing.
Acceptance criteria
Files to touch
- fuzz/Cargo.toml
- multisig_governance/src/lib.rs
Out of scope
- Cross-contract finalize against a real target contract
- CI fuzz orchestration
Why this matters
The fuzz crate (fuzz/Cargo.toml) declares targets for lending_pool, loan_manager, and remittance_nft but lists no governance dependency or target, and multisig_governance is not even a dependency of the fuzz crate. The governance contract in multisig_governance/src/lib.rs has a non-trivial state machine (propose/approve/finalize/cancel/expire with timelock, threshold, reproposal cooldown, TTL) well suited to property fuzzing.
Acceptance criteria
Files to touch
Out of scope