Launch with Proof: internally reviewed by RugWard
Reviewed on 28 October 2026. This is RugWard's own review, not an independent one, and no review can rule out every bug. The launchpad is in a BNB Chain testnet preview. An external scan and, before the 50 BNB cap is raised, an external audit are still to come.
What we checked
- Static analysis with Slither and Aderyn. Every result was checked by hand.
- Fork tests on BNB Chain mainnet and testnet state, using the real Chainlink feed, WBNB and PancakeSwap, including a trading pair created early by someone else.
- Fuzz tests (10,000 random cases each) covering every parameter limit, every time boundary and up to 1,000× oversubscription, plus a sale with 10,000 buyers.
- Stateful invariant tests: 500,000 random calls in 5,000 sequences of commits, finalizing, claims, refunds, team claims, LP release, outsider calls and time jumps.
- A line-by-line read of every function that moves BNB, tokens or LP.
- Live runs on BNB Chain testnet: an oversubscribed sale that went live and a sale that missed its soft cap and refunded.
What always holds in the tests
- The sale contract can always pay every claim and every refund.
- If the soft cap is missed, or nobody finalizes within 7 days after the end, every buyer gets back exactly what they committed, and the creator gets back the listing fee.
- RugWard is paid only when a sale succeeds: the flat fee plus 2% of the raise, taken from the team share and never from the liquidity.
- When oversubscribed, everyone gets the same price and the unused BNB back.
- Liquidity is created in the same transaction as the token, and LP tokens stay locked until the unlock time (then they can only go to the LP receiver), or are burned.
- The team never receives more tokens than have vested.
- Outsiders never succeeded in moving anyone's funds. A buyer contract that re-enters or refuses BNB cannot block the others.
- The contracts have no owner and no admin switch. Nobody, including RugWard, can change a sale after it is created.
Findings
No critical, high or medium issue was found in the reviewed version.
| ID | Severity | Issue | Status |
|---|---|---|---|
| D-01 | Low | During development the factory was too large to deploy on-chain (over the 24,576-byte limit). | Fixed before any deployment: smaller error codes and storage set once in the constructor. Nothing became changeable. |
| I-01 | Info | Up to 1 wei per buyer of rounding dust stays in the sale contract. | Accepted. Rounding always favours solvency, so every claim and refund can be paid. |
| I-02 | Info | Bots can buy at the listing price right after the sale is finalized. | Disclosed. Normal for any new pool. |
| I-03 | Info | Per-wallet limits can be bypassed with many wallets (there is no KYC). | Disclosed. |
| I-04 | Info | “Insiders cannot commit” only blocks the creator and team wallets. | Disclosed. Other insider wallets cannot be proven on-chain. |
| I-05 | Info | The no-sell and LP-held promises are monitored, not enforced by code. | Shown as “monitored” on every Launch Passport, separate from the enforced items. |
| I-06 | Info | If the Chainlink price feed stops, new launches cannot be created. | Commits, finalize and refunds never use the feed. |
Remaining risks
- The review was done by the team that wrote the code.
- The contracts rely on PancakeSwap V2, WBNB and Chainlink working as deployed.
- A token's price can fall. Enforced rules say nothing about the project or its team. Claimed promises are the team's own words.
The site only uses a BNB Chain launch factory whose runtime code hash is 0xbbcdf6abcefd72aec1b83f6e2abaafe02890d2d9c4da8d745f891460cc01cc30 (testnet: 0x4a911d2e773c396bbd5ec94807b6ca65b9c7e34d10f2add7844b9165f5950bba).