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

PEAKDEFI PQ

41%

Process Quality Review (0.7)

PEAKDEFI PQ

Final score:41%
Date:10 May 2021
Audit Process:version 0.7
Author:Rex
PQR Score:41%

FAIL

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
BnB Smart Chain
Ethereum
#QuestionAnswer
50%
1.70%
2.100%
3.Yes
4.20%
5.No
22%
6.Yes
7.No
8.0%
9.100%
10.0%
17%
11.28%
12.58%
13.No
14.0%
15.0%
16.0%
79%
17.90%
18.0%
0%
19.0%
20.0%
21.0%
22.0%
Total:41%

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

50%

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: 70%

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 labelling not clear or easy to find  0% Executing addresses could not be found

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 30 transactions a day on contract PeakStaking, 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: 20%

With 24 commits and 1 branch, this is clearly not a healthy software 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

There is not any evidence of any public team members.

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

22%

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: No

There are no evident documentations of basic software functions.

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

Answer: 0%

There are no evident documentations of basic software functions.

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: 100%

Code examples are in the Appendix. As per the SLOC, there is 110% commenting to code (CtC).

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%

There are no evident documentations of basic software functions, and therefore no links with code implementation.

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

17%

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

Answer: 28%

With TtC of 28%, they do not have a barely adequate test suite.

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: 58%

Code coverage is indicated by the Quantstamp security audit.

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: No

There are no evident signs of script or testing instructions.

14. Report of the results (%)

Answer: 0%

There are result reports indicated by the Quantstamp security audit.

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%

16. Stress Testing environment (%)

Answer: 0%

Security

79%

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

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

Answer: 90%

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: 0%

There is no evident bug bounty.

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

0%

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: 0%

There is no evident documentation that reveals the status of the admin controls.

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: 0%

There is no evident documentation that reveals the status of the admin controls.

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: 0%

There is no evident documentation that reveals the status of the admin controls.

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%

There is no evident documentation that reveals the status of the admin controls.

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.5.17;
23import "@openzeppelin/contracts/ownership/Ownable.sol";
4import "../interfaces/Comptroller.sol";
5import "../interfaces/PriceOracle.sol";
6import "../interfaces/CERC20.sol";
7import "../interfaces/CEther.sol";
8import "../Utils.sol";
910contract CompoundOrder is Utils(address(0), address(0), address(0)), Ownable {
11  // Constants
12  uint256 internal constant NEGLIGIBLE_DEBT = 100; // we don't care about debts below 10^-4 USDC (0.1 cent)
13  uint256 internal constant MAX_REPAY_STEPS = 3; // Max number of times we attempt to repay remaining debt
14  uint256 internal constant DEFAULT_LIQUIDITY_SLIPPAGE = 10 ** 12; // 1e-6 slippage for redeeming liquidity when selling order
15  uint256 internal constant FALLBACK_LIQUIDITY_SLIPPAGE = 10 ** 15; // 0.1% slippage for redeeming liquidity when selling order
16  uint256 internal constant MAX_LIQUIDITY_SLIPPAGE = 10 ** 17; // 10% max slippage for redeeming liquidity when selling order
1718  // Contract instances
19  Comptroller public COMPTROLLER; // The Compound comptroller
20  PriceOracle public ORACLE; // The Compound price oracle
21  CERC20 public CUSDC; // The Compound USDC market token
22  address public CETH_ADDR;
2324  / Instance variables
25  uint256 public stake;
26  uint256 public collateralAmountInUSDC;
27  uint256 public loanAmountInUSDC;
28  uint256 public cycleNumber;
29  uint256 public buyTime; // Timestamp for order execution
30  uint256 public outputAmount; // Records the total output USDC after order is sold
31  address public compoundTokenAddr;
32  bool public isSold;
33  bool public orderType; // True for shorting, false for longing
34  bool internal initialized;
353637  constructor() public {}
3839  function init(
40    address _compoundTokenAddr,
41    uint256 _cycleNumber,
42    uint256 _stake,
43    uint256 _collateralAmountInUSDC,
44    uint256 _loanAmountInUSDC,
45    bool _orderType,
46    address _usdcAddr,
47    address payable _kyberAddr,
48    address _comptrollerAddr,
49    address _priceOracleAddr,
50    address _cUSDCAddr,
51    address _cETHAddr
52  ) public {
53    require(!initialized);
54    initialized = true;
5556    / Initialize details of order
57    require(_compoundTokenAddr != _cUSDCAddr);
58    require(_stake > 0 && _collateralAmountInUSDC > 0 && _loanAmountInUSDC > 0); // Validate inputs
59    stake = _stake;
60    collateralAmountInUSDC = _collateralAmountInUSDC;
61    loanAmountInUSDC = _loanAmountInUSDC;
62    cycleNumber = _cycleNumber;
63    compoundTokenAddr = _compoundTokenAddr;
64    orderType = _orderType;
6566    COMPTROLLER = Comptroller(_comptrollerAddr);
67    ORACLE = PriceOracle(_priceOracleAddr);
68    CUSDC = CERC20(_cUSDCAddr);
69    CETH_ADDR = _cETHAddr;
70    USDC_ADDR = _usdcAddr;
71    KYBER_ADDR = _kyberAddr;
72    usdc = ERC20Detailed(_usdcAddr);
73    kyber = KyberNetwork(_kyberAddr);
7475    // transfer ownership to msg.sender
76    _transferOwnership(msg.sender);
77  }
7879  /**
80   * @notice Executes the Compound order
81   * @param _minPrice the minimum token price
82   * @param _maxPrice the maximum token price
83   */

Solidity Contracts

Language
Files
Lines
Blanks
Comments
Code
Complexity
Solidity
9
752
113
335
304
20

Comments to Code: 335 / 304 =  110 %

JavaScript Tests

Language
Files
Lines
Blanks
Comments
Code
Complexity
JavaScript
1
105
21
0
84
0

Tests to Code: 84 / 304 = 28 %