Torah

CertiK1 address on Polygon (POS)

CertiK reviewed Torah on 23 Sep 2022: 8 findings, 0 critical; 1 acknowledged, 7 open.

No open critical findings
Open the reportOpen Torah’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings8

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High010
Medium000
Low700
Low`_burnFrom()` function is never usedOpen

`_burnFrom()` function is never used.

Low`_msgData()` return value can be declared as `calOpen

`msg.data` is stored in `calldata`. To avoid unnecessary copying to `memory`, it can be returned as `calldata`.

LowErrors in commentsOpen

`_owner` argument is mentioned as `owner` in comments. `msg.sender` is mentioned but `_msgSender()` used. `account` argument is mentioned as `to`.

LowImproper Usage of `public` and `external` TypeOpen

`public` functions that are never called by the contract could be declared as `external`. `external` functions are more efficient than `public` functions.

LowInconsistent target chainOpen

The 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`.

LowUser-Defined GettersOpen

The 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.

LowVariables That Could Be Declared as `immutable`Open

The 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.

Contracts in scope1

AddressChainSource code
0xf46cb10e8c5fb9368bbf497a3176b80c0af66d44Chain: Polygon (POS)Source code: Verified source

Part of Torah’s security record

Torah
Audits1 audit by 1 firmLast audit Sep 2022, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open Torah’s security record

Security firm

CertiK

1,045 projects reviewed · 1,376 reports · latest May 2025

See CertiK’s audits

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