For example, the encoder version is outdated, does not follow the constructor, return, event standards, common problems such as false recharge
For example, authorization function competition, loop consumption, loop security risks, etc.
For example, arithmetic overflow, casting overflow, reentrancy vulnerability, call injection, permission control and other problems that are easily attacked
Check key function points, such as address initialization, transfer, balance judgment, external calls and other design defects
Code-level line-by-line checks, such as syntax features, data privacy and reliability, logging, gas consumption optimization, permissions, etc.
Smart contracts are visible to all users on the blockchain, including but not limited to resources marked as private, or may cause privacy information leakage.
Due to the constraints of the smart contract itself, such as conditional competition, transaction sequence dependence, etc., transaction overflows and exceptions are caused.
Abnormal behaviors caused by unreasonable fault handling mechanisms that may exist in the smart contract code.
The risk of denial of service due to various reasons.
Sensitive functions inherit permission detection and function call permission detection.
To invalidate the contract and delete the address code.
Check the stack height limit, whether the stack is exhausted.
Too many requests result in contract denial of service.
He has pre-researched more than one hundred smart contract applications, is familiar with the code writing rules of various smart contracts, and can accurately find code-level vulnerabilities.
The professional security research team has accumulated for a long time and is committed to the research of blockchain security ecology.
Good project quality control, strict control of project links, safety experts online throughout the process, answering user questions in real time.