EOS Contract Audit

FAQ

• 

  What is the difference between “smart” penetration testing and regular penetration testing?

  “Smart” penetration testing does not provide for performing SQL since DApps, unlike traditional apps, do not have any database. That is why no SQL is required. However, some DApps may have a combined nature (combination of smart contract and backend with the database), so, in this case, traditional penetration testing is performed.
• 

  What are the key activities performed during a DApp security review?

  The DApp security review performed by Hacken experts provides for estimating the security of the back-end and front-end. The back-end security is tested through the conduct of a smart contract audit while front-end security is tested by performing penetration testing.
• 

  What are the key security risks attributable to EOS smart contracts?

  EOS smart contracts inherit most of the parameters attributable to the smart contract model. However, the quality of their implementation may vary among projects and there is always a risk that unexpected logic flow may create conditions enabling malicious actors to steal crypto assets.
• 

  What components does the Hacken security audit include?

  The Hacken security audit provides for performing functional analysis and manual review of the code to check the logic of the contract. The results of the audit are described in the report written in the client-friendly language. As a result, clients can prevent the deployment of vulnerabilities.