If you notice some outdated information please let us know!
FAIL
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.
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.
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 2023. Permission is given to copy in whole, retaining this copyright label.
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? (%)
Token addresses can be found in the Wonderland GitBooks, as seen in the Appendix.
2. Is the code actively being used? (%)
Activity is well over 10 transactions a day on contract TimeTreasury.sol, as indicated in the Appendix.
3. Is there a public software repository? (Y/N)
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"
4. Is there a development history visible? (%)
Wonderland's Contracts have 1 branch and 6 commits.
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).
5. Is the team public (not anonymous)? (Y/N)
Daniele Sesta is the co-founder of Wonderland, and is public at https://twitter.com/danielesesta.
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".
This section looks at the software documentation. The document explaining these questions is here.
7. Are the basic software functions documented? (Y/N)
There is no software function documentation.
8. Does the software function documentation fully (100%) cover the deployed contracts? (%)
There is no software function documentation.
9. Are there sufficiently detailed comments for all functions within the deployed contract code (%)
The Comments to Code (CtC) ratio is the primary metric for this score.
10. Is it possible to trace from software documentation to the implementation in code (%)
There is no software-focused documentation.
11. Full test suite (Covers all the deployed code) (%)
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.
12. Code coverage (Covers all the deployed lines of code, or explains misses) (%)
No evidence of testing or auditing, henceforth the code can be interpreted as fully uncovered.
13. Scripts and instructions to run the tests? (Y/N)
No scripts or instructions to run tests. No evidence of tests to be found either.
14. Report of the results (%)
No testing to report.
15. Formal Verification test done (%)
No evidence of formal verification.
16. Stress Testing environment (%)
No evidence of stress testing environment.
This section looks at the 3rd party software audits done. It is explained in this document.
17. Did 3rd Party audits take place? (%)
No evidence of audits.
18. Is the bug bounty acceptable high? (%)
There is no evidence of any bug bounty, nor an active program with ImmuneFi.
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 (%)
A governance framework was found in their Medium at https://medium.com/the-defi-wonderland/wonderland-governance-framework-25b8792ecc8.
20. Is the information clear and complete (%)
Information is not present.
21. Is the information in non-technical terms that pertain to the investments (%)
Information is not available.
22. Is there Pause Control documentation including records of tests (%)
No information on pause control available.
1// SPDX-License-Identifier: AGPL-3.0-or-later
2pragma solidity 0.7.5;
3
4library SafeMath {
5 /**
6 * @dev Returns the addition of two unsigned integers, reverting on
7 * overflow.
8 *
9 * Counterpart to Solidity's `+` operator.
10 *
11 * Requirements:
12 *
13 * - Addition cannot overflow.
14 */
15 function add(uint256 a, uint256 b) internal pure returns (uint256) {
16 uint256 c = a + b;
17 require(c >= a, "SafeMath: addition overflow");
18
19 return c;
20 }
21 function add32(uint32 a, uint32 b) internal pure returns (uint32) {
22 uint32 c = a + b;
23 require(c >= a, "SafeMath: addition overflow");
24
25 return c;
26 }
27
28 /**
29 * @dev Returns the subtraction of two unsigned integers, reverting on
30 * overflow (when the result is negative).
31 *
32 * Counterpart to Solidity's `-` operator.
33 *
34 * Requirements:
35 *
36 * - Subtraction cannot overflow.
37 */
38 function sub(uint256 a, uint256 b) internal pure returns (uint256) {
39 return sub(a, b, "SafeMath: subtraction overflow");
40 }
41
42 /**
43 * @dev Returns the subtraction of two unsigned integers, reverting with custom message on
44 * overflow (when the result is negative).
45 *
46 * Counterpart to Solidity's `-` operator.
47 *
48 * Requirements:
49 *
50 * - Subtraction cannot overflow.
51 */
52 function sub(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) {
53 require(b <= a, errorMessage);
54 uint256 c = a - b;
55
56 return c;
57 }
58
59 /**
60 * @dev Returns the multiplication of two unsigned integers, reverting on
61 * overflow.
62 *
63 * Counterpart to Solidity's `*` operator.
64 *
65 * Requirements:
66 *
67 * - Multiplication cannot overflow.
68 */
69 function mul(uint256 a, uint256 b) internal pure returns (uint256) {
70 // Gas optimization: this is cheaper than requiring 'a' not being zero, but the
71 // benefit is lost if 'b' is also tested.
72 // See: https://github.com/OpenZeppelin/openzeppelin-contracts/pull/522
73 if (a == 0) {
74 return 0;
75 }
76
77 uint256 c = a * b;
78 require(c / a == b, "SafeMath: multiplication overflow");
79
80 return c;
81 }
82
83 /**
84 * @dev Returns the integer division of two unsigned integers. Reverts on
85 * division by zero. The result is rounded towards zero.
86 *
87 * Counterpart to Solidity's `/` operator. Note: this function uses a
88 * `revert` opcode (which leaves remaining gas untouched) while Solidity
89 * uses an invalid opcode to revert (consuming all remaining gas).
90 *
91 * Requirements:
92 *
93 * - The divisor cannot be zero.
94 */
95 function div(uint256 a, uint256 b) internal pure returns (uint256) {
96 return div(a, b, "SafeMath: division by zero");
97 }
98
99 /**
100 * @dev Returns the integer division of two unsigned integers. Reverts with custom message on
101 * division by zero. The result is rounded towards zero.
102 *
103 * Counterpart to Solidity's `/` operator. Note: this function uses a
104 * `revert` opcode (which leaves remaining gas untouched) while Solidity
105 * uses an invalid opcode to revert (consuming all remaining gas).
106 *
107 * Requirements:
108 *
109 * - The divisor cannot be zero.
110 */
111 function div(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) {
112 require(b > 0, errorMessage);
113 uint256 c = a / b;
114 assert(a == b * c + a % b); // There is no case in which this doesn't hold
115
116 return c;
117 }
118}
119
120interface IERC20 {
121 function decimals() external view returns (uint8);
122 /**
123 * @dev Returns the amount of tokens in existence.
124 */
125 function totalSupply() external view returns (uint256);
126
127 /**
128 * @dev Returns the amount of tokens owned by `account`.
129 */
130 function balanceOf(address account) external view returns (uint256);
131
132 /**
133 * @dev Moves `amount` tokens from the caller's account to `recipient`.
134 *
135 * Returns a boolean value indicating whether the operation succeeded.
136 *
137 * Emits a {Transfer} event.
138 */
139 function transfer(address recipient, uint256 amount) external returns (bool);
140
141 /**
142 * @dev Returns the remaining number of tokens that `spender` will be
143 * allowed to spend on behalf of `owner` through {transferFrom}. This is
144 * zero by default.
145 *
146 * This value changes when {approve} or {transferFrom} are called.
147 */
148 function allowance(address owner, address spender) external view returns (uint256);
149
150 /**
151 * @dev Sets `amount` as the allowance of `spender` over the caller's tokens.
152 *
153 * Returns a boolean value indicating whether the operation succeeded.
154 *
155 * IMPORTANT: Beware that changing an allowance with this method brings the risk
156 * that someone may use both the old and the new allowance by unfortunate
157 * transaction ordering. One possible solution to mitigate this race
158 * condition is to first reduce the spender's allowance to 0 and set the
159 * desired value afterwards:
160 * https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729
161 *
162 * Emits an {Approval} event.
163 */
164 function approve(address spender, uint256 amount) external returns (bool);
165
166 /**
167 * @dev Moves `amount` tokens from `sender` to `recipient` using the
168 * allowance mechanism. `amount` is then deducted from the caller's
169 * allowance.
170 *
171 * Returns a boolean value indicating whether the operation succeeded.
172 *
173 * Emits a {Transfer} event.
174 */
175 function transferFrom(address sender, address recipient, uint256 amount) external returns (bool);
176
177 /*
178 * @dev Emitted when `value` tokens are moved from one account (`from`) to
179 * another (`to`).
180 *
181 * Note that `value` may be zero.
182 */
183 event Transfer(address indexed from, address indexed to, uint256 value);
184
185 /*
186 * @dev Emitted when the allowance of a `spender` for an `owner` is set by
187 * a call to {approve}. `value` is the new allowance.
188 */
189 event Approval(address indexed owner, address indexed spender, uint256 value);
190}
191
192library Address {
193 /**
194 * @dev Returns true if `account` is a contract.
195 *
196 * [IMPORTANT]
197 * ====
198 * It is unsafe to assume that an address for which this function returns
199 * false is an externally-owned account (EOA) and not a contract.
200 *
Comments to Code: 2182 / 4462 = 49 %