background
logo

Security Audit Report for PopDEX's PopDEX Bridge

BESCHREIBUNG

The target of this audit is the private code repository of PopDEX Bridge of PopDEX. The current update introduces additional safeguards to limit the impact of hot verifier key compromise. Regular verifier set updates now require cold verifier signatures on Spoke chains and, when governance hardening is enabled, on Hub, together with restrictions on authorized submitters. Spoke contracts introduce system candidate lists and enforce mutually exclusive verifier, Finalizer, and Locker roles. Governance messages relayed through the hot verifier path may only disable Finalizers or enable Lockers, while reverse changes require coldsigned authorization. Additional controls include per-token withdrawal limits tracked through hourly buckets, a cold-managed receiver whitelist, restrictions on increasing the Locker pause threshold, and tighter verifier update timelock bounds. The update also introduces a featuregated pending deposit workflow on Hub. Following deposit processing, an additional callback records the pending deposit. A separate finalizeDeposit entry point verifies hot verifier signatures and the recorded deposit parameters before submitting a Hub finalization command and registering a callback to complete pending deposit processing.

Please refer to the report for the detailed audit scope.

Our audit methodology employs automated vulnerability scans, manual verification, and business logic analysis to uncover potential security issues coupled with gas and code quality optimization recommendations.

In summary, we did not find any critical issues within the audited codebase. However, we have identified some non-critical issues that should be addressed. Additionally, we have put forth recommendations and notes that should be taken into consideration. It is important to note that the scope of our audit was strictly limited to the specific code versions mentioned in the report. Any updates made subsequent to our review would require a re-evaluation.

WICHTIGSTE FESTSTELLUNGEN

Insgesamt haben wir 1 potenzielle Probleme im Smart Contract festgestellt. Darüber hinaus geben wir 4 Empfehlungen und 2 Hinweise. Diese sind nachfolgend aufgeführt:

Hohes Risiko: 0
Mittleres Risiko: 0
Geringes Risiko: 1
Empfehlung: 4
Hinweis: 2
ID Severity Description Status
1 Low Lack of role conflict checks in function finalizeVerifierUpdate() Fixed
2 - Align custody-chain timing bounds between Hub and Spoke Fixed
3 - Add Locker availability checks in function _setLockerBatch() Fixed
4 - Reject the zero address in system candidate updates Fixed
5 - Ensure withdrawals remain counted for the full 24-hour window Confirm
6 - Potential centralization risks -
7 - Out of scope dependencies and external logic -

Weitere Einzelheiten finden Sie im Auditbericht.

Machen Sie den ersten Schritt in eine sichere Zukunft

Kontaktieren Sie uns jetzt für die fachkundigen Code-Audits von BlockSec und erhöhen Sie die Sicherheit Ihres Protokolls, bevor es live geht!