Algem LiquidCrowdLoan smart contract audit

HashlockCode version: not recorded (see the report)

Hashlock reviewed Algem (Algem LiquidCrowdLoan smart contract audit) on 1 Mar 2024: 8 findings, 0 critical; 6 marked fixed, 2 acknowledged.

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

Report hosted on GitHub.

Trustblock does not review code.

Findings8

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

SeverityOpenAcknowledgedFixed
Critical000
High004
Medium001
Low021
HighLiquidCrowdloan,ALGMVesting#claimRewards,revokeVesting - The manager can revoke vesting at any point in time, and don't send rewards to users.Fixed

The report gives no description here.

HighLiquidCrowdloan#claimOwnership - Change Ownership of the contract will always set the owner as address 0. This will lead to a loss of control of LiquidCrowdloan.Fixed

The report gives no description here.

HighLiquidCrowdloan#claimRewards - Different users can't call claimRewards() function simultaneously, because there is a risk of insolvency and some users will not receive rewards.Fixed

The report gives no description here.

HighLiquidCrowdloan#claimRewards - Side case where H1, results in an unresolved Bug.Fixed

The report gives no description here.

MediumLiquidCrowdloan#unstake,withdraw - Temporary impossibility for the user, to withdraw ASTR Tokens staked initially.Fixed

The report gives no description here.

LowALGMVesting#withdrawStuck - Update references for token interactions as this function consistently interacts with the IALGM Interface. Any modifications to ALGM token functions could result in unforesFixed

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 Algem’s security record

Algem
Audits3 audits by 1 firmLast audit Dec 2024, by Hashlock.
Critical findingsNo open critical findingsAcross 3 reports.
Open Algem’s security record

Security firm

Hashlock

198 projects reviewed · 279 reports · latest Jul 2026

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