As of 3 Nov 2026, LiteDex has 1 audit report on Trustblock, by CertiK, dated 24 Jan 2023. That report lists no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Litedex audit 3 | Security firm: CertiK | Date: | Scope: Files named in the report | 1 critical finding, fixed | Open · skynet.certik.com |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 1 | 0 | 3 |
| Medium | 0 | 0 | 0 |
| Low | 1 | 0 | 10 |
In the contract `LitedexFarmer` the role `_owner` has authority over the functions shown in the diagram below.  --- In the contract `LitedexStakePool.BEP20` the role `_owner` has authority over the functions shown in the diagram below.  In the contract `LitedexStakePool.Litedex` the role `_owner` has authority over the functions shown in the diagram below.  In the contract `LitedexStakePool.LitedexSP` the role `_owner` has authority over the functions shown in the diagram below.  --- In the contract `LitedexSmartStakeFactory.LitedexSmartStake` the role `SMART_STAKE_FACTORY` has authority over the functions shown in the diagram below.  In the contract `LitedexSmartStakeFactory.LitedexSmartStake` the role `_owner` has authority over the functions shown in the diagram below.  In the contract `LitedexSmartStakeFactory` the role `_owner` has authority over the functions shown in the diagram below.  --- In the contract `LitedexVault` the role `_owner` has authority over the functions shown in the diagram below.  In the contract `LitedexVault` the role `admin` has authority over the functions shown in the diagram below.  Any compromise to the privileged account may allow the hacker to take advantage of this authority and update the sensitive settings and execute sensitive functions of the project.
Open the reportThe LitedexFarmer contract operates as the main entry for interaction with staking users. The staking users deposit LP tokens into the Litedex pool and in return get a proportionate share of the pool’s rewards. Later on, the staking users can withdraw their assets from the pool. In this procedure, `deposit()` and `withdraw()` are involved in transferring users’ assets into (or out of) the Litedex protocol. When transferring standard ERC20 deflationary tokens, the input amount may not be equal to the received amount due to the charged (and burned) transaction fee. As a result, this may not meet the assumption behind these low-level asset-transferring routines and will bring unexpected balance inconsistencies.
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="litedex"></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