Milkyway Celestia Restaking audit

Oak SecurityCode version: not recorded (see the report)

Oak Security reviewed MilkyWay (Milkyway Celestia Restaking audit) on 16 Dec 2024: 9 findings, 4 critical; all marked fixed.

4 critical findings, fixed
Open the reportOpen MilkyWay’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings9

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

SeverityOpenAcknowledgedFixed
Critical004
High002
Medium000
Low003
CriticalExcess funds are credited to the user’s treasury fundFixed

The report gives no description here.

CriticalIncorrect rounding direction when decreasing insurance fundFixed

The report gives no description here.

CriticalMalicious chains can send malicious packets to steal insurance fundsFixed

The report gives no description here.

CriticalVesting tokens will not be burnt if the user performs full undelegationFixed

The report gives no description here.

HighMsgDepositInsurance will fail due to blacklisted module addressFixed

The report gives no description here.

HighNon-atomic execution between SignAndBroadcastMsgExec and database operationsFixed

The report gives no description here.

LowImproper error handling in GetValidatorCommissionsInRangeFixed

The report gives no description here.

LowStorage writes to KVStore while an iterator existsFixed

The report gives no description here.

LowUpdating insurance percentages causes unintended behaviorsFixed

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

MilkyWay
Audits1 audit by 1 firmLast audit Dec 2024, by Oak Security.
Critical findingsNo open critical findingsIn that report, 4 critical findings were reported. Each is marked fixed by the firm that reported it.
Open MilkyWay’s security record

Security firm

Oak Security

33 projects reviewed · 60 reports · latest May 2026

See Oak 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