Security & audits
Security on a launchpad is mostly what the code makes impossible, not what a team promises. This page says which guarantees are structural, exactly how each contract stack was reviewed before it touched real money - and by whom - which documents exist, how tokens are verified, and what still waits on an external audit.
How we approach security
The design rule is that the most important protections should hold even if degen.zone disappeared tomorrow. Where a guarantee can be made by the absence of code, it is.
- Liquidity is burned or locked by construction. On the direct-to-pool chains (Robinhood, BSC, Base, Ethereum, Arc) the full supply goes single-sided into the hooked pool at launch and the liquidity position is burned to
0xdead. No contract holds a key that could withdraw it - including ours. Scanners such as GMGN read the burn directly. - Tokens are ownerless. A launched token has a fixed supply, no mint function, no pause and no owner powers. The economic settings chosen at launch - swap fee tier, reward or burn model, payout asset - are fixed in the transaction that creates the token and cannot be raised or changed later by anyone, admins included.
- Fees are computed on-chain. The fee hook charges the creator’s chosen swap fee and the platform + referral add-on inside the swap itself; the split is a contract constant, not a server setting. Reward escrows accrue and pay out on-chain and the keeper can only trigger what the contract already allows.
- Every deploy is fork-proven first. Before a launcher, hook or router goes to mainnet, the exact bytecode is exercised end to end on a fork of that mainnet - launch, dev buy, bundle, trade, payout - and cast-verified afterwards against the live deployment (constants, owner, hook registration).
- Everything the UI shows is read live from chain. Launch fees, bundle fees, pool fees, payout catalogues and balances are read from the contracts at render time and shown before you sign; nothing is a hard-coded promise in the interface.
- Fee setters are capped. Every launcher’s flat-fee setters are capped on-chain:
0.5 BNBon the PancakeSwap Infinity stack,0.5 ETHon the Uniswap V4 direct and pair launchers (Robinhood, Base, Ethereum, BSC) and50 USDCon Arc, where the native coin is the dollar - so a launch or bundle fee can never be set absurdly high, even by mistake or by a compromised key. - The interface refuses unsafe states. Chains and features are gated by honesty flags that flip on only after a watched live run; while the Terms gate is open no on-chain write is sent; quotes carry slippage protection on every trade.
An audit - internal or external - lowers risk, it does not remove it. Tokens launched here are extremely volatile and most go to zero. Third-party tokens used as pairs or payouts (tokenized stocks, stablecoins) are issued and controlled by their issuers, not by degen.zone. Nothing in these docs is financial advice.
Audit posture per stack
Honest wording matters more than a badge here. Every stack below was reviewed by the team in an adversarial, multi-reviewer process before it went live, with reports published in the repository. No external audit firm has signed off the current stacks. The earlier external engagement’s scope documents exist (see the list below), and the stock-conversion features remain gated on a fresh external audit.
Uniswap V4 direct-launch stack (Robinhood, BSC V4 venue, Base, Ethereum, Arc)
Live The hook, launchers, bundlers, pair suite, reward escrows, buyback-and-burn, custom fee recipient and the PONS bundler have each been through adversarial audit rounds before their mainnet step: the internal pre-mainnet audit (2026-08-19), the reward-escrow audit (2026-08-30), and a dedicated review of every later addition before it was deployed. Findings were fixed, re-tested and fork-proven against the live PoolManager before each deploy. Base, Ethereum, Arc and BSC’s V4 venue run this stack with zero Solidity changes, so they inherit the same review - Ethereum most literally of all, since canonical Uniswap V4 is the deployment the stack was written against in the first place.
PancakeSwap Infinity stack (BSC)
Live The Infinity port was audited in-house on 2026-09-19 with an adversarial multi-reviewer process: two independent slices - A (fee hook + swap router) and B (launcher + launch library + bundler) - each producing executable proof-of-concept tests and a written report, followed by a coordinator verification pass. Result: 0 critical, 0 high, 0 medium, 4 low, all fixed before deploy:
- L-1 - the protocol fee is folded into the pool fee the UI displays, so the shown rate equals what a swap actually pays.
- L-2 - the pool shape is pinned at registration, so a token cannot later be served against a differently shaped pool than the one its launch created.
- B-L1 - creator-bound vanity salts: every non-zero
CREATE2salt must carry the creator’s address in its first 20 bytes, so a pre-announced vanity address cannot be hijacked by another deployer. - B-L2 - the flat-fee setters are capped at
0.5 BNB.
The suite behind the report: 316 hermetic tests plus 21 tests on a BSC mainnet fork; the five deployed contracts compile GPL-free. Report: docs/audit/infinity-2026-09-19/README.md (with A-hook-router.md and B-launcher-lib-bundler.md) in the repository.
Solana programs
Live The Meteora DBC launch path, the fee-router program and the Solana buyback-and-burn program went through two internal audit rounds before mainnet (2026-09-14). The deployed program hash is verified against the published source, so the bytes on-chain are the bytes that were reviewed.
Every audit document
All review documents live in the degen.zone repository under docs/ and docs/audit/. The repository is private, so nothing here links out; the paths name the files exactly, and any report is made available on request.
| Date | Path | Scope |
|---|---|---|
2026-08-19 | docs/audit-internal-2026-08-19.md | Internal pre-mainnet security audit of the full contract set (about 12k lines) by six reviewers; every critical and high finding re-verified by the lead before close. |
2026-08-23 | docs/audit/SCOPE.md, PRE-AUDIT-REVIEW.md, COVERAGE.md, CHECKLIST.md | Scope freeze, self-review, test-coverage map and readiness checklist prepared for an external EVM contract audit (default, v4, infinity, lz and katana build profiles). |
2026-08-25 | docs/evm-reaudit-scope.md | Re-audit scope for the bundler recipient cap and related changes ahead of the Robinhood and Base mainnet gate. |
2026-08-30 | docs/reward-escrow-audit.md | Internal adversarial audit of the Robinhood reward-escrow (holder reward) feature by four parallel reviewers. |
2026-09-03 | docs/reliability-audit-2026-09-03.md | Read-only reliability audit of the indexer and the three keepers (written in German). |
2026-09-13 | docs/launch-readiness-audit-2026-09-13.md | Public launch readiness review: recovery paths, accounting under load, worker failover. |
2026-09-19 | docs/audit-scope-2026-09-19.md | Scope for package A (flat opening-bundle fee on the fused launch paths, Robinhood and Base) and package B (the PancakeSwap Infinity direct stack on BSC). |
2026-09-19 | docs/audit/infinity-2026-09-19/README.md, A-hook-router.md, B-launcher-lib-bundler.md | The PancakeSwap Infinity self-audit: two independent slices (hook + router; launcher + launch library + bundler) with executable proof-of-concept tests, plus the coordinator verification pass. 0 critical, 0 high, 0 medium, 4 low (all fixed before deploy). |
Contract verification
Every launched token is verified automatically, so explorers and scanners can read its source and show the “verified” and “renounced” badges without anyone submitting anything:
| Chain | Primary rail | Explorer |
|---|---|---|
| Robinhood Chain | Sourcify | Blockscout (robinhoodchain.blockscout.com) |
| Arc | Sourcify | arcscan (Blockscout) |
| Base | Sourcify | Basescan (Etherscan V2 API) |
| BNB Smart Chain | Sourcify | BscScan (Etherscan V2 API) |
| Solana | Program hash verified against source | - |
The platform contracts themselves (launchers, hooks, routers, escrow factories) are verified the same way, and each deploy is cast-verified afterwards - constants, owner, treasury and hook registration checked against the live chain. GoPlus and GMGN read the explorer and Sourcify records for their badges.
What still needs an external audit
The pay-fees-in-stock rail and the related stock-conversion features on Robinhood Chain are built and tested but stay off until a fresh external security audit signs them off. Converting fee streams into tokenized equities touches third-party issuer contracts and price feeds, which is exactly where an outside review earns its cost. See Tokenized equities and Status & availability.
Everything else that is live has been through the team-run reviews above. When an external firm reviews a stack, its report will be added to the document list on this page.
Reporting an issue
If you find a vulnerability or a discrepancy between these docs and what the contracts do, email team@degen.zone. That mailbox reaches the team directly and is the right channel for anything you would not want to post in public; X and Telegram work for everything else, and if you have access, an issue in the repository is fine too. Please include the chain, the contract or token address, a transaction hash where relevant, and enough detail to reproduce. Reports about live funds are treated as urgent; please give the team a reasonable window to fix before publishing details.