Torah has 1 public audit report from CertiK; dated 23 Sep 2022; no critical findings reported. It also holds 1 deployed contract on 1 chain.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
8 findings are still open or acknowledged in the firms’ reports: 1 high, 7 low (7 open, 1 acknowledged).
Centralization Risks in ERC20VP.sol
Torah · CertiK · 23 Sep 2022 · Report ↗
`_burnFrom()` function is never used
Torah · CertiK · 23 Sep 2022 · Report ↗
`_msgData()` return value can be declared as `cal
Torah · CertiK · 23 Sep 2022 · Report ↗
Errors in comments
Torah · CertiK · 23 Sep 2022 · Report ↗
Improper Usage of `public` and `external` Type
Torah · CertiK · 23 Sep 2022 · Report ↗
Inconsistent target chain
Torah · CertiK · 23 Sep 2022 · Report ↗
User-Defined Getters
Torah · CertiK · 23 Sep 2022 · Report ↗
Variables That Could Be Declared as `immutable`
Torah · CertiK · 23 Sep 2022 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Torah | Security firm: CertiK | Date: | Scope: 1 address on Polygon (POS) | None open | Findings: 1 high · 7 low 1 acknowledged · 7 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 1 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 7 | 0 | 0 |
`_burnFrom()` function is never used.
Open the report`msg.data` is stored in `calldata`. To avoid unnecessary copying to `memory`, it can be returned as `calldata`.
Open the report`_owner` argument is mentioned as `owner` in comments. `msg.sender` is mentioned but `_msgSender()` used. `account` argument is mentioned as `to`.
Open the report`public` functions that are never called by the contract could be declared as `external`. `external` functions are more efficient than `public` functions.
Open the reportThe comment says the contract source was submitted at bscscan.com. The interface `ITRC20` is used, referring to Tron chain. The contract audited is deployed on Polygon. `getOwner()` comment refers to `bep token`. `EIPs` are mentioned in `approve()` comments. Main contract name is `ERC20VP` referring to Ethereum chain. Other comments are referring to `TRC20`.
Open the reportThe linked functions are equivalent to the compiler-generated getter functions for the respective variables. `public` state field names should not begin with `_` to comply with the Solidity naming convention.
Open the reportThe linked variables 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. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0xf46c…6d440xf46cb10e8c5fb9368bbf497a3176b80c0af66d44 | Chain: Polygon (POS) | Source code: Verified source |
Trustblock holds 1 public audit report for Torah, dated 23 Sep 2022. The latest is by CertiK (“Torah”).
CertiK wrote the report Trustblock holds for Torah.
8 findings are still open or acknowledged in the firms’ reports: 1 high, 7 low (7 open, 1 acknowledged). No critical finding is reported. Statuses are the security firms’ own.
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="torah"></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