AUDIT

  • safe

    Code For Programming Standardization Vulnerability

    The bad programming habits may cause some unexpected transactions, such as wrong authority declaration, redundant implementation of callback function, predictable random numbers, etc.

  • safe

    Code Logical Vulnerability

    The difference between smart contract code and functional requirements may lead to some logical vulnerability of smart contract code.

  • safe

    Function Call Vulnerability

    The wrong call of functions, such as call, delegatecall, selfdestruct, will bring about some unpredictably logical security vulnerability.

  • safe

    Help Us Renew Our Brand! ETH for the Winner!

    Integer overflow and underflow will lead to the illegal transactions, which causes a great loss of property .

  • safe

    Reentrancy Attack Vulnerability

    The wrong call of reentrant function may lead to the failure of transactions or uncontrollable transfer behavior.

  • safe

    Execution-Ordering Dependency Vulnerability

    The wrong execution-ordering may bypass exception detection and increase the risks of wrong transfer behavior.

  • safe

    Timestamp Dependency Vulnerability

    The execution results of timestamp-depended smart contracts may be manipulated illegally, which causes some incorrect business logical errors.

  • safe

    Platform Interface Misuse Vulnerability

    The wrong usage of functional code provided by platform may cause loss of property. For example, using tx.origin for identity authentication.