LERN360

CredShields7 Nov 2025Code version: not recorded (see the report)

CredShields reviewed LERNToken (LERN360) (LERN360) on 7 Nov 2025: 29 findings, 6 critical; 22 marked fixed, 7 acknowledged.

6 critical findings, fixed

Open the report Open LERNToken (LERN360)’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings33

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

Severity	Open	Acknowledged	Fixed
Critical	0	0	6
High	0	4	6
Medium	0	3	5
Low	0	0	5

HighEIP-7702 EOAs Can Stake But Cannot Withdraw Or ClaimAcknowledged

The report gives no description here.

HighInconsistent userLastClaimTime Update and Unconditional canUserClaim Check in Non-APY ModeAcknowledged

The report gives no description here.

HighMisuse of canUserClaimAfterStake and Missing Cooldown Enforcement Leading to Potential Reward Bypass and Staking RestrictionsAcknowledged

The report gives no description here.

HighUser Can Replay Signature To Bypass AuthorizationAcknowledged

The report gives no description here.

MediumFirst vault consistently receives the remainder, causing unfair distributionAcknowledged

The report gives no description here.

MediumUnclaimed Rewards Lost on Unstake Due to Missing Claim EnforcementAcknowledged

The report gives no description here.

MediumUser can reuse one signature to call many actionsAcknowledged

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 LERNToken (LERN360)’s security record

LERNToken (LERN360)

Audits1 audit by 1 firmLast audit Nov 2025, by CredShields.

Critical findingsNo open critical findingsIn that report, 6 critical findings were reported. Each is marked fixed by the firm that reported it.

Open LERNToken (LERN360)’s security record

Security firm

CredShields

45 projects reviewed · 58 reports · latest Oct 2026

See CredShields’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.