Tegro

QuillAuditsFiles named in the report

Audit · firm’s term: audit report

QuillAudits reviewed Tegro on 18 Mar 2024: 9 findings, 0 critical; 7 marked fixed, 2 open.

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

Report hosted on quillaudits.com.

Trustblock does not review code.

Findings9

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium001
Low206
LowA lower limit should be set for matchedAmountOpen

The transaction executor can be anyone who can enter the matchedAmount. The matchedAmount can be entered in the way where the calculated baseFeeAmount would be rounded down to 0.E.g While calculating fee on L207 if the feeAmount is 20 and matchedAmount is 499 then the calculation would be: 499 * 20 / 10000 = 0 (In solidity). The same can happen while calculating quoteFeeAmount using totalPrice. The above example shows that if the numerator is less than the denominator then the answer can be rounded down to 0 which will allow an executor to bypass the fees on a small portion of the amount. The successful attack depends on the amount of tokens that are getting sold/bought, but to perform this attack recursively to bypass the fee, it might not be feasible as every transaction would cost the gas (also depends on who pays the fee or who is executing the signed orders). But it would be good practice to add a lower limit for the amount so that if the matchedAmount is less than that specified limit then the transaction will revert.

LowNote regarding fee-on-transfer tokensOpen

While using fee-on-transfer tokens (as baseToken or quoteToken), the amount that will get actually transferred would be less than what is getting transferred because of fee deductions.This doesn’t create any security issues but can create confusion on the receiver side.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (2)

  • Settler.sol
  • TegroDEX.sol

Part of Tegro’s security record

Tegro
Audits2 audits by 2 firmsLast audit Mar 2024, by QuillAudits.
Critical findings1 open critical findingReported in “Tegro” by Cyberscope, Apr 2022. Not marked fixed in that report.
Open Tegro’s security record

Security firm

QuillAudits

350 projects reviewed · 459 reports · latest Apr 2025

See QuillAudits’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