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 relevant chain that gets reviewed and its corresponding software repository. The document explaining these questions is here.
1. Are the smart contract addresses easy to find? (%)
Smart contract addresses cannot be found on the website. Addresses were found in the Discord through the Rose chat bot. A screenshot of the addresses can be found in the appendix.
2. How active is the primary contract? (%)
CoinWind's HECO contract address's on HecoInfo displays well over 10 transactions a day.
3. Does the protocol have a public software repository? (Y/N)
CoinWind's GitHub cannot be found within its documentation.
4. Is there a development history visible? (%)
CoinWind's GitHub cannot be found within its documentation.
5. Is the team public (not anonymous)?
The team operates under an anonymous persona.
This section looks at the software documentation. The document explaining these questions is here.
7. Is the protocol's software architecture documented? (Y/N)
There is no protocol software architecture documented within the GitBook of the protocol.
8. Does the software documentation fully cover the deployed contracts' source code? (%)
There is no protocol software architecture documented within the GitBook of the protocol.
9. Is it possible to trace the documented software to its implementation in the protocol's source code? (%)
There is no protocol software architecture documented within the GitBook of the protocol.
10. Has the protocol tested their deployed code? (%)
There is no evidence of testing within the protocol's deployed code as the software repo is not public.
11. How covered is the protocol's code? (%)
There is no evidence of code coverage of CoinWind's code.
12. Does the protocol provide scripts and instructions to run their tests? (Y/N)
There are no scripts nor instructions on how to run tests for CoinWind.
13. Is there a detailed report of the protocol's test results?(%)
There are no detailed reports available for the protocol's test results.
14. Has the protocol undergone Formal Verification? (Y/N)
This protocol has not undergone formal verification.
15. Were the smart contracts deployed to a testnet? (Y/N)
There are no evidences of smart contract testnet deployment available on CoinWind.
This section looks at the 3rd party software audits done. It is explained in this document.
16. Is the protocol sufficiently audited? (%)
The protocol displays three different audits with Fairyproof, Beosin and CertiK. All of them were done post-launch and no changes were necessary. This gives the protocol 80%. However, the reports could only be found through the Rose chatbot within Coinwind's Telegram.
17. Is the bounty value acceptably high (%)
There are no bug bounties available on CoinWind.
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.
18. Is the protocol's admin control information easy to find?
There are no admin control information available.
19. Are relevant contracts clearly labelled as upgradeable or immutable? (%)
There are no admin control information available.
20. Is the type of smart contract ownership clearly indicated? (%)
There are no admin control information available.
21. Are the protocol's smart contract change capabilities described? (%)
There are no smart contract change capabilities available for the protocol.
22. Is the protocol's admin control information easy to understand? (%)
There are no admin control information available.
23. Is there sufficient Pause Control documentation? (%)
There are no pause control documentations available for the protocol.
24. Is there sufficient Timelock documentation? (%)
There is no information available on Timelocks.
25. Is the Timelock of an adequate length? (Y/N)
There is no information available on Timelocks.
This section goes over the documentation that a protocol may or may not supply about their Oracle usage. Oracles are a fundamental part of DeFi as they are responsible for relaying tons of price data information to thousands of protocols using blockchain technology. Not only are they important for price feeds, but they are also an essential component of transaction verification and security. These questions are explained in this document.
26. Is the protocol's Oracle sufficiently documented? (%)
There are no Oracle documentation available for CoinWind.
27. Is front running mitigated by this protocol? (Y/N)
There are no evidence of front running mitigation by CoinWind.
28. Can flashloan attacks be applied to the protocol, and if so, are those flashloan attack risks mitigated? (Y/N)
There are no flashloan attack mitigation techniques described for the protocol.
1Enter appendix example code here