Pareto Credit
Pareto is a private credit marketplace that connects institutional lenders and borrowers, providing scalable, yield-generating opportunities and bridging institutional capital on-chain.
PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
For Credit Vaults contract marked in the description as “Queue” should be considered out of scope while for USP “Queue” contract is in scope. . Paused contracts and contract market as Deprecated/Decommissioned in doc are not considered in scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Miner-extractable value (MEV) if can freeze funds or cause protocol insolvency
Protocol insolvency
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Smart contract unable to operate due to lack of token funds
Temporary freezing of funds
Out of scope
- Best practice critiques
- Freezing of Funds after a borrower defaults
- Attacks the are considering either the manager or the owner a malicious actor
- Everything acknowledged on previous audits
Only Senior Best Yield contracts will be considered in scope for the Best Yield. Governance and Utilities and ERC-4626 wrappers contracts are not covered under this bug bounty program. Paused contracts and contract market as Deprecated/Decommissioned in doc are not considered in scope
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers