logo
bg_imgbg_imgbg_imgbg_img
exclamation mark iconReport an issue

If you notice some outdated information please let us know!

close icon
Name
Email
Your message
arrow-left

Pickle Finance V2

66%

Previous versions

Process Quality Review (0.7)

Pickle Finance V2

Final score:66%
Date:14 Jun 2021
Audit Process:version 0.7
Author:Nick of DeFiSafety
PQR Score:66%

FAIL

Hack History

Date:21 Nov 2020
Details: $19.7m DAI was taken.
Reference Linklink

Scoring Appendix

The final review score is indicated as a percentage. The percentage is calculated as Achieved Points due to MAX Possible Points. For each element the answer can be either Yes/No or a percentage. For a detailed breakdown of the individual weights of each question, please consult this document.

The blockchain used by this protocol
Ethereum
Polygon
#QuestionAnswer
70%
1.100%
2.100%
3.Yes
4.100%
5.No
48%
6.Yes
7.Yes
8.20%
9.75%
10.0%
47%
11.80%
12.50%
13.Yes
14.0%
15.0%
16.0%
94%
17.100%
18.50%
49%
19.100%
20.90%
21.30%
22.0%
Total:66%

Very simply, the audit looks for the following declarations from the developer's site. With these declarations, it is reasonable to trust the smart contracts.

  • Here is my smart contract on the blockchain
  • You can see it matches a software repository used to develop the code
  • Here is the documentation that explains what my smart contract does
  • Here are the tests I ran to verify my smart contract
  • Here are the audit(s) performed to review my code by third party experts

This report is for informational purposes only and does not constitute investment advice of any kind, nor does it constitute an offer to provide investment advisory or other services. Nothing in this report shall be considered a solicitation or offer to buy or sell any security, token, future, option or other financial instrument or to offer or provide any investment advice or service to any person in any jurisdiction. Nothing contained in this report constitutes investment advice or offers any opinion with respect to the suitability of any security, and the views expressed in this report should not be taken as advice to buy, sell or hold any security. The information in this report should not be relied upon for the purpose of investing. In preparing the information contained in this report, we have not taken into account the investment needs, objectives and financial circumstances of any particular investor. This information has no regard to the specific investment objectives, financial situation and particular needs of any specific recipient of this information and investments discussed may not be suitable for all investors.

Any views expressed in this report by us were prepared based upon the information available to us at the time such views were written. The views expressed within this report are limited to DeFiSafety and the author and do not reflect those of any additional or third party and are strictly based upon DeFiSafety, its authors, interpretations and evaluation of relevant data. Changed or additional information could cause such views to change. All information is subject to possible correction. Information may quickly become unreliable for various reasons, including changes in market conditions or economic circumstances.

This completed report is copyright (c) DeFiSafety 2021. Permission is given to copy in whole, retaining this copyright label.

Code And Team

70%

This section looks at the code deployed on the Mainnet that gets reviewed and its corresponding software repository. The document explaining these questions is here.

1. Are the executing code addresses readily available? (%)

Answer: 100%

They are available at website https://github.com/pickle-finance/contracts as indicated in the Appendix.

Percentage Score Guidance:
100%
Clearly labelled and on website, docs or repo, quick to find
70%
Clearly labelled and on website, docs or repo but takes a bit of looking
40%
Addresses in mainnet.json, in discord or sub graph, etc
20%
Address found but labeling not clear or easy to find
0%
Executing addresses could not be found

2. Is the code actively being used? (%)

Answer: 100%

Activity is 800 transactions a day on contract MasterChefV2, as indicated in the Appendix.​

Percentage Score Guidance:
100%
More than 10 transactions a day
70%
More than 10 transactions a week
40%
More than 10 transactions a month
10%
Less than 10 transactions a month
0%
No activity

3. Is there a public software repository? (Y/N)

Answer: Yes

Is there a public software repository with the code at a minimum, but also normally test and scripts. Even if the repository was created just to hold the files and has just 1 transaction, it gets a "Yes". For teams with private repositories, this answer is "No"

Score Guidance:
Yes
There is a public software repository with the code at a minimum, but also normally test and scripts. Even if the repository was created just to hold the files and has just 1 transaction.
No
For teams with private repositories.

4. Is there a development history visible? (%)

Answer: 100%

With 255 commits and 25 branches, this is a very healthy repository.

This metric checks if the software repository demonstrates a strong steady history. This is normally demonstrated by commits, branches and releases in a software repository. A healthy history demonstrates a history of more than a month (at a minimum).

Percentage Score Guidance:
100%
Any one of 100+ commits, 10+branches
70%
Any one of 70+ commits, 7+branches
50%
Any one of 50+ commits, 5+branches
30%
Any one of 30+ commits, 3+branches
0%
Less than 2 branches or less than 30 commits

5. Is the team public (not anonymous)? (Y/N)

Answer: No

Team is anonymous.

For a "Yes" in this question, the real names of some team members must be public on the website or other documentation (LinkedIn, etc). If the team is anonymous, then this question is a "No".

Documentation

48%

This section looks at the software documentation. The document explaining these questions is here.

6. Is there a whitepaper? (Y/N)

Answer: Yes

7. Are the basic software functions documented? (Y/N)

Answer: Yes

Basic capability and requirements are documented at https://docs.pickle.finance/farms/farms. This document mentions some basic functions, but does not describe them fully.

8. Does the software function documentation fully (100%) cover the deployed contracts? (%)

Answer: 20%

Only top level requirements are documented at https://docs.pickle.finance/farms/farms so a 20% overall score is given.

Percentage Score Guidance:
100%
All contracts and functions documented
80%
Only the major functions documented
79 - 1%
Estimate of the level of software documentation
0%
No software documentation

9. Are there sufficiently detailed comments for all functions within the deployed contract code (%)

Answer: 75%

While the CtC is 28%, reading MasterChef shows excellent quality. Score adapted to 75%

The Comments to Code (CtC) ratio is the primary metric for this score.

Percentage Score Guidance:
100%
CtC > 100 Useful comments consistently on all code
90 - 70%
CtC > 70 Useful comment on most code
60 - 20%
CtC > 20 Some useful commenting
0%
CtC < 20 No useful commenting

10. Is it possible to trace from software documentation to the implementation in code (%)

Answer: 0%

Some traceability in https://docs.pickle.finance/jars/strategies, but not much traceability anywhere else.

Percentage Score Guidance:
100%
Clear explicit traceability between code and documentation at a requirement level for all code
60%
Clear association between code and documents via non explicit traceability
40%
Documentation lists all the functions and describes their functions
0%
No connection between documentation and code

Testing

47%

11. Full test suite (Covers all the deployed code) (%)

Answer: 80%

Code examples are in the Appendix. As per the SLOC, there is 90% testing to code (TtC).

This score is guided by the Test to Code ratio (TtC). Generally a good test to code ratio is over 100%. However the reviewers best judgement is the final deciding factor.

Percentage Score Guidance:
100%
TtC > 120% Both unit and system test visible
80%
TtC > 80% Both unit and system test visible
40%
TtC < 80% Some tests visible
0%
No tests obvious

12. Code coverage (Covers all the deployed lines of code, or explains misses) (%)

Answer: 50%

No code coverage tests or reports found in their repo, but there are clearly a robust set of tests.

Percentage Score Guidance:
100%
Documented full coverage
99 - 51%
Value of test coverage from documented results
50%
No indication of code coverage but clearly there is a reasonably complete set of tests
30%
Some tests evident but not complete
0%
No test for coverage seen

13. Scripts and instructions to run the tests? (Y/N)

Answer: Yes

Scripts and instructions to run tests can be found at https://github.com/pickle-finance/protocol.

14. Report of the results (%)

Answer: 0%

There are no apparent test reports in their software repository.

Percentage Score Guidance:
100%
Detailed test report as described below
70%
GitHub code coverage report visible
0%
No test report evident

15. Formal Verification test done (%)

Answer: 0%

No evidence of a formal verification for Pickle Finance.

16. Stress Testing environment (%)

Answer: 0%

I could not find any test-net smart contract addresses.

Security

94%

This section looks at the 3rd party software audits done. It is explained in this document.

17. Did 3rd Party audits take place? (%)

Answer: 100%

Pickle was audited four times before and after launch.​

Percentage Score Guidance:
100%
Multiple Audits performed before deployment and results public and implemented or not required
90%
Single audit performed before deployment and results public and implemented or not required
70%
Audit(s) performed after deployment and no changes required. Audit report is public
50%
Audit(s) performed after deployment and changes needed but not implemented
20%
No audit performed
0%
Audit Performed after deployment, existence is public, report is not public and no improvements deployed OR smart contract address not found, (where question 1 is 0%)
Deduct 25% if code is in a private repo and no note from auditors that audit is applicable to deployed code.

18. Is the bug bounty acceptable high? (%)

Answer: 50%

Percentage Score Guidance:
100%
Bounty is 10% TVL or at least $1M AND active program (see below)
90%
Bounty is 5% TVL or at least 500k AND active program
80%
Bounty is 5% TVL or at least 500k
70%
Bounty is 100k or over AND active program
60%
Bounty is 100k or over
50%
Bounty is 50k or over AND active program
40%
Bounty is 50k or over
20%
Bug bounty program bounty is less than 50k
0%
No bug bounty program offered
An active program means that a third party (such as Immunefi) is actively driving hackers to the site. An inactive program would be static mentions on the docs.

Access Controls

49%

This section covers the documentation of special access controls for a DeFi protocol. The admin access controls are the contracts that allow updating contracts or coefficients in the protocol. Since these contracts can allow the protocol admins to "change the rules", complete disclosure of capabilities is vital for user's transparency. It is explained in this document.

19. Can a user clearly and quickly find the status of the access controls (%)

Answer: 100%

Percentage Score Guidance:
100%
Clearly labelled and on website, docs or repo, quick to find
70%
Clearly labelled and on website, docs or repo but takes a bit of looking
40%
Access control docs in multiple places and not well labelled
20%
Access control docs in multiple places and not labelled
0%
Admin Control information could not be found

20. Is the information clear and complete (%)

Answer: 90%
  • The general DAO and voting system of Pickle Finance indicates the capabilities of contract upgradeability.  - Voting roles and MultiSig roles are clearly defined  - Masterchef details admin change capabilities.

Percentage Score Guidance:
All the contracts are immutable -- 100% OR
a) All contracts are clearly labelled as upgradeable (or not) -- 30% AND
b) The type of ownership is clearly indicated (OnlyOwner / MultiSig / Defined Roles) -- 30% AND
c) The capabilities for change in the contracts are described -- 30%

21. Is the information in non-technical terms that pertain to the investments (%)

Answer: 30%

It's basically written in code, and code commenting, as they link their MasterChef contract for a description of admin control capabilities.

Percentage Score Guidance:
100%
All the contracts are immutable
90%
Description relates to investments safety and updates in clear, complete non-software language
30%
Description all in software specific language
0%
No admin control information could be found

22. Is there Pause Control documentation including records of tests (%)

Answer: 0%

No Pause Control documentation or test were found.

Percentage Score Guidance:
100%
All the contracts are immutable or no pause control needed and this is explained OR Pause control(s) are clearly documented and there is records of at least one test within 3 months
80%
Pause control(s) explained clearly but no evidence of regular tests
40%
Pause controls mentioned with no detail on capability or tests
0%
Pause control not documented or explained

Appendices

 The author of this review is Rex of DeFi Safety.

Email: rex@defisafety.com
Twitter: @defisafety

I started with Ethereum just before the DAO and that was a wonderful education.  It showed the importance of code quality. The second Parity hack also showed the importance of good process.  Here my aviation background offers some value. Aerospace knows how to make reliable code using quality processes.
I was coaxed to go to EthDenver 2018 and there I started SecuEth.org with Bryant and Roman. We created guidelines on good processes for blockchain code development. We got EthFoundation funding to assist in their development Process Quality Reviews are an extension of the SecurEth guidelines that will further increase the quality processes in Solidity and Vyper development. DeFiSafety is my full time gig and we are working on funding vehicles for a permanent staff.

1pragma solidity 0.6.7;
23import "../lib/enumerableSet.sol";
4import "../lib/safe-math.sol";
5import "../lib/erc20.sol";
6import "../lib/ownable.sol";
7import "./pickle-token.sol";
89// MasterChef was the master of pickle. He now governs over PICKLES. He can make Pickles and he is a fair guy.
10//
11// Note that it's ownable and the owner wields tremendous power. The ownership
12// will be transferred to a governance smart contract once PICKLES is sufficiently
13// distributed and the community can show to govern itself.
14//
15// Have fun reading it. Hopefully it's bug-free. God bless.
16contract MasterChef is Ownable {
17    using SafeMath for uint256;
18    using SafeERC20 for IERC20;
1920    // Info of each user.
21    struct UserInfo {
22        uint256 amount; // How many LP tokens the user has provided.
23        uint256 rewardDebt; // Reward debt. See explanation below.
24        //
25        // We do some fancy math here. Basically, any point in time, the amount of PICKLEs
26        // entitled to a user but is pending to be distributed is:
27        //
28        //   pending reward = (user.amount * pool.accPicklePerShare) - user.rewardDebt
29        //
30        // Whenever a user deposits or withdraws LP tokens to a pool. Here's what happens:
31        //   1. The pool's `accPicklePerShare` (and `lastRewardBlock`) gets updated.
32        //   2. User receives the pending reward sent to his/her address.
33        /   3. User's `amount` gets updated.
34        /   4. User's `rewardDebt` gets updated.
35    }
3637    // Info of each pool.
38    struct PoolInfo {
39        IERC20 lpToken; // Address of LP token contract.
40        uint256 allocPoint; // How many allocation points assigned to this pool. PICKLEs to distribute per block.
41        uint256 lastRewardBlock; // Last block number that PICKLEs distribution occurs.
42        uint256 accPicklePerShare; // Accumulated PICKLEs per share, times 1e12. See below.
43    }
4445    // The PICKLE TOKEN!
46    PickleToken public pickle;
47    // Dev fund (2%, initially)
48    uint256 public devFundDivRate = 50;
49    // Dev address.
50    address public devaddr;
51    // Block number when bonus PICKLE period ends.
52    uint256 public bonusEndBlock;
53    // PICKLE tokens created per block.
54    uint256 public picklePerBlock;
55    // Bonus muliplier for early pickle makers.
56    uint256 public constant BONUS_MULTIPLIER = 10;
5758    // Info of each pool.
59    PoolInfo[] public poolInfo;
60    // Info of each user that stakes LP tokens.
61    mapping(uint256 => mapping(address => UserInfo)) public userInfo;
62    // Total allocation points. Must be the sum of all allocation points in all pools.
63    uint256 public totalAllocPoint = 0;
64    // The block number when PICKLE mining starts.
65    uint256 public startBlock;
6667    // Events
68    event Recovered(address token, uint256 amount);
69    event Deposit(address indexed user, uint256 indexed pid, uint256 amount);
70    event Withdraw(address indexed user, uint256 indexed pid, uint256 amount);
71    event EmergencyWithdraw(
72        address indexed user,
73        uint256 indexed pid,
74        uint256 amount
75    );
7677    constructor(
78        PickleToken _pickle,
79        address _devaddr,
80        uint256 _picklePerBlock,
81        uint256 _startBlock,
82        uint256 _bonusEndBlock
83    ) public {
84        pickle = _pickle;
85        devaddr = _devaddr;
86        picklePerBlock = _picklePerBlock;
87        bonusEndBlock = _bonusEndBlock;
88        startBlock = _startBlock;
89    }

Solidity Contracts

Language
Files
Lines
Blanks
Comments
Code
Complexity
Solidity
107
10677
1825
1919
6933
615

Comments to Code: 1919 / 6933 =  28 %

JavaScript Tests

Language
Files
Lines
Blanks
Comments
Code
Complexity
JavaScript
63
8156
1567
329
6260
97

Tests to Code: 6260 / 6933 = 90 %