Vesq Presale
- Completed
Paladin Rush
-
Audit Report
Commissioned
06 Nov 2021
Completed
01 Dec 2021
Contracts Audited
VSQPresale ...b1a4C8A0 VSQTokenRedeem VSQTokenRedeem.sol Source https://github.com/VESQHQ/vesq-contracts/tree/7f09297c85060aa8b16e4cbf78bee4a0c33aa091 The client wishes to do a stealth launch so we have redacted the contract address. Users should verify that the last 8 characters of the token contract matches the one we have audited here.
View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High
0 – – – Medium
1 1 – – Low
2 2 – – Informational
8 8 – – Total 11 11 – – When using this protocol, the main risks you want to look out for are:
- Ensuring that the contracts you are interacting with matches the one we audited. This can be done by comparing the addresses with the one present in the contracts page in our audit.
- Our audits only cover code-related risks. Users will have to do their own due diligence on other aspects of the protocol such as the reputation of the team, the protocol’s tokenomics, and other aspects of the project that might be relevant.