0xc64500dd7b0f1794807e67802f8abbf5f8ffb054
As of 21 Nov 2026, Trustblock’s record holds 0xc64500dd7b0f1794807e67802f8abbf5f8ffb054 on Ethereum as a contract of LOCUS CHAIN. 1 audit report on Trustblock lists this address: CertiK, 1 Dec 2022. 14 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on Ethereum.
| Audit | Security firm | Date | Commit named in the report | Report |
|---|---|---|---|---|
| Locus Chain - Audit | CertiK | Not recorded (see the report) | Open |
1 High, 13 Low. In the firm’s own words; statuses are the firm’s, from each report.
All `LOCUS` tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute `LOCUS` tokens without the consensus of the community.
The audit on Trustblock · Open the reportThe function `transferFrom` deviate from the `ERC20` standard and does not emit `Approval` event for the changed allowance.
The audit on Trustblock · Open the reportTwo declarations do not conform to the [Solidity style guide](https://solidity.readthedocs.io/en/v0.7.3/style-guide.html#naming-conventions) with regards to its naming convention. Particularly: - `camelCase`: Should be applied to function names, argument names, local and state variable names, modifiers - `UPPER_CASE`: Should be applied to `constant` variables - `CapWords`: Should be applied to contract names, struct names, event names and enums
The audit on Trustblock · Open the reportThe functions which are never called internally within the contract should have external visibility for gas optimization.
The audit on Trustblock · Open the report```solidity=67 function approveAndCall(address _spender, uint _value, bytes _extraData) public returns(bool) { ``` - The function `approveAndCall` implicitly returns a default value.
The audit on Trustblock · Open the reportFunctions that update state variables should emit relevant events as notifications.
The audit on Trustblock · Open the reportThe **require** statement can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.
The audit on Trustblock · Open the reportThe cited address input is missing a check that it is not `address(0)`.
The audit on Trustblock · Open the reportCurrent Locus implementation is vulnerable to [a known ERC20 race condition issue](https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729), which could lead to token theft. When a user calls `approve()` for a second time on a spender that has already been allowed, the spender could call `transferFrom()` to transfer the previous value and still receive the authorization to transfer the new value. Exploit scenario: 1. Alice calls `approve(Bob, 100)` to allow Bob to spend 100 tokens. 2. Alice changes her mind and calls `approve(Bob, 50)`. 3. Bob observes the second `approve(Bob, 50)` function call and calls `transferFrom(Alice, Bob, 100)` before the second `approve(Bob, 50)` call. 4. The above scenario can be achieved by front-running. In this case, Bob can transfer another 50 tokens from Alice and in total, he transferred 150 tokens from Alice.
The audit on Trustblock · Open the reportThe highlighted `if` statement will always equal `true` because the `approve()` function either reverts or returns true.
The audit on Trustblock · Open the reportLiterals with many digits are difficult to read and review. ```solidity=15 uint internal constant initialSupply = 7000000000 * (10 ** uint(decimals)); ```
The audit on Trustblock · Open the reportThe contracts cited have an unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to differing compiler version numbers. This can lead to ambiguity when debugging, as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one. Furthermore, the versions of Solidity allowed by the pragma statement are not recommended as they are considered old (0.4.x).
The audit on Trustblock · Open the reportThe linked functions are equivalent to the compiler-generated getter functions for the respective variables.
The audit on Trustblock · Open the reportThe variable `tokenOwner` assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation, but will remain constant throughout the lifetime of a deployed contract. An advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they are not located in storage. Please note that `immutable` state variables were introduced in later Solidity releases. Therefore, in order to make use of it, a greater version of Solidity should be used.
The audit on Trustblock · Open the reportThe LOCUS CHAIN security record · Every LOCUS CHAIN address · This address on the explorer