Chiliz Chain

Resonance SecurityFiles named in the report

Resonance Security reviewed Chiliz (Chiliz Chain) on 20 Aug 2025: 14 findings, 0 critical; 13 marked fixed, 1 open.

No open critical findings
Open the reportOpen Chiliz’s security record
Report stored on IPFS. Content hash QmeStSagkKWN6iarSnhSzD2rTjebwwygT8fhETVn4YB8Uh

Trustblock does not review code.

Findings14

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

SeverityOpenAcknowledgedFixed
Critical000
High100
Medium002
Low0011
HighCooldown For Stakes Can Be Bypassed Or IncreasedOpen

The protocol adds a feature where tokens can have different cooldown periods. This may mean that in some cases, users can bypass this period by swapping tokens.It is possible that the new token will have a lower cooldown than the old token, thus allowing previously unstaked tokens to have a shorter cooldown period.These are the steps to replicate this issue:Stake old tokens (asuming 1000 seconds of locking period).Wait less time than unstakePeriodPerToken of the old token and unstake them.Swap tokens.The lock time for your position has decreased depending on the unstakePeriodPerToken of the new token. For example, if this value is 1 second, then the remaining time is bypassed.

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

  • src/interfaces/IFTSwapEvents.sol
  • src/interfaces/IMintableFT.sol
  • src/FTSwap.sol
  • src/interfaces/IFTSwap.sol
  • src/Staking3.sol

Part of Chiliz’s security record

Chiliz
Audits8 audits by 3 firmsLast audit Jan 2026, by Halborn.
Critical findingsNo open critical findingsAcross the 8 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open Chiliz’s security record

Security firm

Resonance Security

18 projects reviewed · 25 reports · latest Aug 2025

See Resonance Security’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