On what chains are the smart contracts going to be deployed?

If you are integrating tokens, are you allowing only whitelisted tokens to work with the codebase or any complying with the standard? Are they assumed to have certain properties, e.g. be non-reentrant? Are there any types of weird tokens you want to integrate?

Are there any limitations on values set by admins (or other roles) in the codebase, including restrictions on array lengths?

Are there any limitations on values set by admins (or other roles) in protocols you integrate with, including restrictions on array lengths?

For permissioned functions, please list all checks and requirements that will be made before calling the function.

Is the codebase expected to comply with any EIPs? Can there be/are there any deviations from the specification?

Are there any off-chain mechanisms or off-chain procedures for the protocol (keeper bots, arbitrage bots, etc.)?

Are there any hardcoded values that you intend to change before (some) deployments?

If the codebase is to be deployed on an L2, what should be the behavior of the protocol in case of sequencer issues (if applicable)? Should Sherlock assume that the Sequencer won't misbehave, including going offline?

Should potential issues, like broken assumptions about function behavior, be reported if they could pose risks in future integrations, even if they might not be an issue in the context of the scope? If yes, can you elaborate on properties/invariants that should hold?

Please discuss any design choices you made.

Please list any known issues and explicitly state the acceptable risks for each known issue.

We will report issues where the core protocol functionality is inaccessible for at least 7 days. Would you like to override this value?

Please provide links to previous audits (if any).

Please list any relevant protocol resources.

Additional audit information.