If you notice some outdated information please let us know!
Process Quality Review (0.9)
Meso Finance
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.
Very simply, the review looks for the following declarations from the developer's site. With these declarations, it is reasonable to trust the smart contracts.
- Here are my smart contract on the blockchain(s)
- Here is the documentation that explains what my smart contracts do
- Here are the tests I ran to verify my smart contracts
- Here are all the security steps I took to safeguard these contracts
- Here is an explanation of the control I have to change these smart contracts
- Here is how these smart contracts get information from outside the blockchain (if applicable)
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.
Code and Team
13%
This section looks at the code deployed on the relevant chains and team aspects. The document explaining these questions is here.
1. Are the smart contract addresses easy to find? (%)
No smart contract addresses could be found.
2. Does the protocol have a public software repository? (Y/N)
No software repository could be found from the website data.
3. Is the team public (not anonymous)?
No team information was available.
4. How responsive are the devs when we present our initial report?
Devs responded with 48 hours, then said nothing. Score 75%
Code Documentation
0%
This section looks at the software documentation. The document explaining these questions is here.
5. Is there a whitepaper? (Y/N)
We could not find a white paper.
6. Is the protocol's software architecture documented? (%)
No software documentation of any kind, including software architecture, was found.
7. Does the software documentation fully cover the deployed contracts' source code? (%)
No software documentation was found.
8. Is it possible to trace the documented software to its implementation in the protocol's source code? (%)
No software documentation was found. From that, there can be no traceability.
9. Is the documentation organized to ensure information availability and clarity? (%)
No software documentation of any kind could be found. No comment on organization could be made. Score 0%.
Testing
0%
This section covers the testing process of the protocol’s smart contract code previous to its deployment on the mainnet. The document explaining these questions is here.
10. Has the protocol tested their deployed code? (%)
With no software documentation, no software repository, no contract addresses that there is no indication of blockchain software at all. Therefore, no test score is available. Default score 0%.
11. How covered is the protocol's code? (%)
With no tests evident, no score for coverage is possible. Score 0%.
12. Is there a detailed report of the protocol's test results?(%)
No test report was evident.
13. Has the protocol undergone Formal Verification? (Y/N)
No evidence of a formal verification.
Security
6%
This section looks at the 3rd party software audits done. It is explained in this document.
14. Is the protocol sufficiently audited? (%)
There is an audit done on software by OtterSec. The audit appears complete and indicates that falls were rectified. The audit has some links to GitHub directories. However these directories are either private or unavailable. Because there is no indication of the software that is being executed by this protocol (as there are no smart contract addresses or software repository) no score for this audit is possible. And auditor audited code, but I have no evidence that this code is being executed by this protocol. As such, no credit for this audit is possible. Score 0%. This is as per our guidance.
15. Is there a matrix of audit applicability on deployed code (%)? Please refer to the example doc for reference.
As there is just one audit, the score defaults to 100%.
16. Is the bug bounty value acceptably high (%)
No bug bounty information could be found. Score 0%.
17. Is there documented protocol monitoring (%)?
No details protocol monitoring information was found.
18. Is there documented protocol front-end monitoring (%)?
No front-end monitoring information could be found. Score 0%.
Admin 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. Is the protocol code immutable or upgradeable? (%)
As no information on the software or its upgradability is available, this defaults to a score of 0%.
20. Is the protocol's code upgradeability clearly explained in non technical terms? (%)
There is no documentation on upgradability of the code (or immutability) available. Score 0%.
21. Are the admin addresses, roles and capabilities clearly explained? (%)
There is no information on administration or admin addresses available. As such, this question defaults to 0%.
22. Are the signers of the admin addresses clearly listed and provably distinct humans? (%)
There is no information on administrative addresses or signers. Score 0%.
23. Is there a robust documented transaction signing policy? Please refer to the Example doc for reference.(%)
No information about the website, it's administration or a transaction signing policy was available. Score 0%.