DESCRIPCIÓN
The target of this audit is the private code repository of launchpad-arc of Peach. The launchpad-arc is a non-upgradeable token launch protocol deployed on Arc, an EVM chain. Each launch deploys one fixed-supply launch token and one dedicated bonding curve via CREATE2, with the entire supply minted to that curve. Trading runs on a constant product curve with a phantom quote reserve. Once the sellable supply is exhausted, the launch graduates permissionlessly into a Uniswap V4 pool, with the full-range position locked permanently. Fees are split among the platform, creators, and partners. Launches may optionally enable buyback, routing a portion of the creator share into launch tokens that vest in contract BuybackVault over five years. One factory serves multiple approved quote tokens and captures each launch’s economics at creation. Therefore, later governance changes affect only future launches.
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.
HALLAZGOS CLAVE
En total encontramos 3 posibles incidencias en el smart contract. Añadimos además 6 recomendaciones y 7 notas, como se detalla a continuación:
| ID | Severity | Description | Status |
|---|---|---|---|
| 1 | Medium | Unexpected graduation behaviors under extreme configurations | Fixed |
| 2 | Low | Potential overwrite of a valid recipient | Fixed |
| 3 | Low | Inconsistent fee calculation between exact-input and exact-output swaps | Fixed |
| 4 | - | Add validations in function validateCombination() |
Confirmed |
| 5 | - | Align comments with implementation | Fixed |
| 6 | - | Validate liquidity in function _validateSeed() |
Fixed |
| 7 | - | Remove redundant computation in the function buyExactIn() |
Confirmed |
| 8 | - | Revise misleading variable names | Fixed |
| 9 | - | Allow disabled partners to claim previously accrued fees | Fixed |
| 10 | - | Potential centralization risk | - |
| 11 | - | Ensure a correct slippage bound | - |
| 12 | - | Different fee rates across launch phases | - |
| 13 | - | Careful configuration of the partner share cap | - |
| 14 | - | Fee sweep requires settlement of all partners | - |
| 15 | - | Ensure off-chain validation of launch configurations | - |
| 16 | - | Refactoring and new features are outside the audit scope | - |
Encontrarás más detalles en el informe de auditoría.