AIDAv2

CertiKFiles named in the report

CertiK reviewed AIDAv2 on 9 Jan 2025: 39 findings, 1 critical; 36 marked fixed, 3 open.

1 critical finding, fixed
Open the reportOpen AIDAv2’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings39

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

SeverityOpenAcknowledgedFixed
Critical001
High004
Medium009
Low3022
LowMissing Zero Address ValidationOpen

The cited address input is missing a check that it is not `address(0)`.

LowUnclear `bindInviter()` logicOpen

The `bindInviter()` function allows any user to register as a valid member and assign an address as an `inviter`. However, this function lacks restrictions and safeguards: - Anyone can call the function, enabling any address to register as a valid member without checks or prerequisites. - It allows any address to be set as an `inviter`, including invalid addresses such as the zero address, the contract's own address, or the caller's own address, which could undermine the intended purpose of tracking valid invite relationships. - Although the `member.inviter` field is set when this function is called, it is not utilized elsewhere in the contract, making its purpose unclear and potentially redundant.

LowUnclear `deposit()` LogicOpen

The `deposit()` function allows any user to deposit `AID` or `USDT` tokens into the contract. However, the function does not update any state variables or store information related to the deposit. This behavior is unusual because functions named `deposit()` typically involve increasing a balance, tracking deposits, or granting some form of credit or acknowledgment to the depositor. The absence of such updates raises questions about the intended purpose of this function, as it seems to lack meaningful functionality and fails to provide expected behaviors associated with deposits.

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 (1)

  • contracts/aidav2.sol

Part of AIDAv2’s security record

AIDAv2
Audits1 audit by 1 firmLast audit Jan 2025, by CertiK.
Critical findingsNo open critical findingsIn that report, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open AIDAv2’s security record

Security firm

CertiK

1,044 projects reviewed · 1,375 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