Pico is an open-source, modular, and efficient zkVM that enables developers to generate zero-knowledge proofs for Rust programs. This contest focuses on identifying and eliminating potential security vulnerabilities or bugs to ensure Pico’s robustness before it is adopted in production by other projects.
Scope
On what chains are the smart contracts going to be deployed?
N/A
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?
N/A
Are there any limitations on values set by admins (or other roles) in the codebase, including restrictions on array lengths?
N/A
Are there any limitations on values set by admins (or other roles) in protocols you integrate with, including restrictions on array lengths?
N/A
Is the codebase expected to comply with any specific EIPs?
No.
Are there any off-chain mechanisms involved in the protocol (e.g., keeper bots, arbitrage bots, etc.)? We assume these mechanisms will not misbehave, delay, or go offline unless otherwise specified.
No.
What properties/invariants do you want to hold even if breaking them has a low/unknown impact?
No.
Please discuss any design choices you made.
N/A
Please provide links to previous audits (if any) and all the known issues or acceptable risks.
N/A
Please list any relevant protocol resources.
Pico docs: https://docs.brevis.network/
Additional audit information.
N/A
Total Rewards
Contest Pool
Lead Senior Watson
Lead Judge
51,200 USDC
25,200 USDC
12,000 USDC
Status
Scope
Start Time
End Time
Judging Rules