EthereumCommonwealth / Auditing Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nexo #285
Comments
|
Auditing time 1 day |
|
@MrCrambo assigned |
|
Auditing time: 1 day |
|
@RideSolo assigned |
|
Auditing time: 1 day. |
|
@danbogd assigned |
|
Audit paused. |
|
My report is finished. |
|
My report is finished |
Nexo Security Audit Report1. SummaryNexo smart contract security audit report performed by Callisto Security Audit Department 2. In scopeСommit hash 3571169b3365adfc92c5bd743cc75b5184a2172a. 3. FindingsIn total, 3 issues were reported including:
No critical security issues were found. 3.1. Known vulnerabilities of ERC-20 tokenSeverity: lowDescriptionIt is possible to double withdrawal attack. More details here. 3.2. Owner PrivilegesSeverity: owner previligesDescriptionOwner allows himself to call Code snippethttps://github.com/nexofinance/NEXO-Token/blob/master/contracts/NexoToken.sol#L103 3.3. Address is not correct.Severity: noteDescriptionDon't forget to change addresses before deploy contract. Code snippet4. ConclusionThe audited smart contract can be deployed. Only low severity issues were found during the audit. 5. Revealing audit reportshttps://gist.github.com/yuriy77k/2bf5ef25e14b3c8fe974092f082e73ef https://gist.github.com/yuriy77k/35cb280c011e56ae697b72d5dd0c379e https://gist.github.com/yuriy77k/c8775b71c10309e21c343bd1400f965c |
Audit request
Nexo is the most advanced and trusted instant crypto lending provider on a global scale, servicing 40+ currencies across more than 200 jurisdictions.
https://nexo.io/
Source code
https://github.com/nexofinance/NEXO-Token/blob/master/contracts/NexoToken.sol
Disclosure policy
info@nexo.io
Platform
Eth
Number of lines:
164
The text was updated successfully, but these errors were encountered: