As of 3 Nov 2026, The Sharp Token has 1 audit report on Trustblock, by QuillAudits, dated 5 Sep 2023. That report lists no open critical findings.
Record last updated . It holds audits, findings and contracts up to Nov 2026, and incidents up to Oct 2026. Trustblock does not review code.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| The Sharp Token(TT10) | Security firm: QuillAudits | Date: | Scope: Files named in the report | No open critical findings | Open · quillaudits.com |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 1 |
| Low | 1 | 0 | 4 |
The ability of the contract owner to regulate the use of the token with the use of the Pausable library shows the centralization power centered on the contract owner. The owner of the contract can pause the contract and users will no longer be able to use these tokens again unless the owner unpauses the contract. When the contract is paused, the “beforeTransfer()” created in the Pausable returns the state of _paused variable. This is called in the following functions:• transfer • transferFrom • decreaseAllowance Also, with the presence of the TransferOwnership function in the token contract, it shows that the contract owner can transfer not just the ownership of the contract, but transfer the tokens present in the former contract address to the new contract address.
Open the reportthe beforeTransfer() function is a view function that returns a boolean and this is called in the require check of some critical function. The issue arises with comparing the returned value to the “false” constant.
Open the reportaccording to the contract, the beforeTransfer function is used to pause critical functionalities such as transfer, transferFrom, and decreaseAllowance. However, this was not included in some other critical functions, like for instance, the direct opposite to the decreaseAllowance function, increaseAllowance, do not have the beforeTransfer check. This implies that when the contract is paused, users can still increase allowances of the approved addresses but they cannot decrease the allowances. Also another function is the approved function, this poses that token holders can still approve tokens to addresses. There is no essence of approving tokens that cannot be transferred.
Open the reportContracts should be deployed with the same compiler version and flags that they have been tested with thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using, for example, an outdated compiler version that might introduce bugs that affect the contract system negatively.
Open the reportThe codebase has comments on each of the functions. However, it fails to prototype the Natspec code comment format that details the functions more appropriately. With the use of the Natspec format, it is easier to cite the expected function inputs and explain them. This makes for easy comprehension of the codebase and is often recommended as the conventional way to comment solidity smart contracts.
Open the reportThe reports name a repository or files. Open a report to see its scope.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="the-sharp-token"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us