TermMax V2

ABDK ConsultingCode version: not recorded (see the report)

ABDK Consulting reviewed TermMax (TermMax V2) on 8 Oct 2025: 4 findings, 0 critical; 2 marked fixed, 2 acknowledged.

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

Report hosted on GitHub.

Trustblock does not review code.

Findings30

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium022
Low000

Marked Recommendations by the firm. Not counted as findings.

RecommendationsConsider specifying as "^0.8.0" unless there is something special regarding this particular version.Acknowledged

The report gives no description here.

RecommendationsEvents are usually named via nous (TermMax4626Factory.sol)Acknowledged

The report gives no description here.

RecommendationsEvents are usually named via nous, such as "SequencerUptimeFeed".Acknowledged

The report gives no description here.

RecommendationsIt would be more efficient to pass a single array of structs with two fields, rather than two parallel arrays.Acknowledged

The report gives no description here.

RecommendationsThe return type should be "TermMaxConstantPriceFeed".Acknowledged

The report gives no description here.

RecommendationsThe return type should be more specific. (TermMaxConstantPriceFeed.sol)Acknowledged

The report gives no description here.

RecommendationsThe semantics of the returned values is unclear. (OracleAggregatorV2.sol)Acknowledged

The report gives no description here.

RecommendationsThe semantics of the returned values is unclear. (OracleAggregatorWithSequencerV2.sol)Acknowledged

The report gives no description here.

RecommendationsThe semantics of the returned values is unclear. (TermMaxERC4626PriceFeed.sol)Acknowledged

The report gives no description here.

RecommendationsThe type for the "_sequencerUptimeFeed" argument should be "AggregatorV3Interface".Acknowledged

The report gives no description here.

Show 10 more
RecommendationsThe type for the "_underlyingPriceFeed" argument should be "AggregatorV3Interface".Acknowledged

The report gives no description here.

RecommendationsThe type for the "_vault" argument should be more specific.Acknowledged

The report gives no description here.

RecommendationsThe type for the "aavePool" argument should be more specific.Acknowledged

The report gives no description here.

RecommendationsThe type for the "asset" argument should be more specific.Acknowledged

The report gives no description here.

RecommendationsThe type for the "order" argument should be more specific.Acknowledged

The report gives no description here.

RecommendationsThe type for the "sequencerUptimeFeed" parameter should be "AggregatorV3Interface".Acknowledged

The report gives no description here.

RecommendationsThe type for the "thirdPool" argument should be more specific.Acknowledged

The report gives no description here.

RecommendationsThe type for the "underlying" argument should be more specific.Acknowledged

The report gives no description here.

RecommendationsThe type for this variable should be "StableERC4626for4626".Acknowledged

The report gives no description here.

RecommendationsThe type for this variable should be "StableERC4626ForAave".Acknowledged

The report gives no description here.

Show 6 more
RecommendationsThe type for this variable should be "VariableERC4626ForAave".Acknowledged

The report gives no description here.

RecommendationsThis error could be made more useful by adding certain parameters into it.Acknowledged

The report gives no description here.

RecommendationsWe didn't review this file. (MakerHelper.sol)Acknowledged

The report gives no description here.

RecommendationsWe didn't review this file. (TermMaxRouterV2.sol)Acknowledged

The report gives no description here.

RecommendationsWe didn't review this file. (TermMaxSwapAdapter.sol)Acknowledged

The report gives no description here.

RecommendationsThis variable is redundant, as "msg.sender" is cheaper to access, then a local variable.Fixed

The report gives no description here.

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.

Part of TermMax’s security record

TermMax
Audits2 audits by 1 firmLast audit Dec 2025, by ABDK Consulting.
Critical findingsNo open critical findingsAcross the 2 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open TermMax’s security record

Security firm

ABDK Consulting

34 projects reviewed · 73 reports · latest Jun 2026

See ABDK Consulting’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