DESCRIPTION
The target of this audit is the private code repository of Bridge Contract of Pacifica. Bridge Contract is a cross-chain bridge protocol on Solana designed to facilitate transfers of SOL and SPL tokens across different chains. The protocol operates by emitting on-chain logs that are observed and processed by an off-chain relayer service, which coordinates and executes corresponding actions on the destination chain. The system is composed of two dedicated programs: sol-bridge, which handles native SOL bridging, and spl-bridge, which manages SPL token registration and transfers. This separation allows for clearer responsibility boundaries and more flexible handling of different asset types within the bridging workflow.
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.
KEY FINDINGS
In total, we find 3 potential issues in the smart contract. We also have 2 recommendations and 2 notes, as follows:
| ID | Severity | Description | Status |
|---|---|---|---|
| 1 | Medium | Potential fund lock due to lack of check in function remove_token() |
Fixed |
| 2 | Low | Lack of DefaultAccountState extension check |
Fixed |
| 3 | Low | Lack of minimum deposit amount validation | Confirm |
| 4 | - | Reject empty withdrawals in function batch_withdraw() |
Fixed |
| 5 | - | Improper check in function batch_withdraw() |
Fixed |
| 6 | - | Potential centralization risks | - |
| 7 | - | Ensure the off-chain event monitoring matches on-chain event definitions | - |
More details are provided in the audit report.