https://github.com/code-423n4/2023-10-party/blob/b23c65d62a20921c709582b0b76b387f2bb9ebb5/contracts/signature-validators/OffChainSignatureValidator.sol#L72
When called to validate a signature off-chain, OffchainSignatureValidator checks for a pre-configured threshold in a party to threshold map in storage:
Since map values are zero by default, and a Party can change this default only through a governance action, it is possible that this logic acts more permissively than it needs to, for extended periods of time.
This seems a permissive by default, strict by option behavior, whereas one would rather expect it to be strict by default, permissive by option.
Consider defaulting thresholdBps to a reasonably high value i.e. the Partys passThresholdBps; an additional magic value can be accommodated within the uint96 range to allow the Party to opt-in for the every token holder can sign behavior through an ArbitraryCallsProposal.
