See the audit catalog for published professional and AI reports, source revisions, findings and planned reviews. Planned reviews do not establish coverage.

The FullRange source uses explicit two-sided launch seeds, fungible LP shares and a team-selected swap fee from 0.01% to 10%, permanent for each wrapper. Protocol fees are 30% of collected swap fees when enabled; team destinations receive the remainder. The Veridise report below covers the earlier V2 release and excludes these Launchpad, FullRange and token changes. The AI and internal reviews in the audit catalog each name the exact source revision they reviewed, and most predate the October 2026 FullRange changes; they are not professional audits. Check which revision a review covers before relying on it.

Veridise completed a security review and delivered the updated Coin Launchpad V2 report on September 17, 2026. You can read the complete report on the GlazeCorp website, including its findings, responses and limitations. The reader also offers the original PDF.

What was reviewed

The report identifies an initial source revision beginning af56858 and records the informational fix at revision 741d05b0. Its scope lists 12 core Solidity files. Use that scope table as the authority for coverage: the report title does not mean every launch, periphery contract, interface or later code change was audited.

The report uses some earlier contract names, including IndexCoin and Strategy. These docs use the current repository names, Coin and Auction. A naming match alone is not proof that deployed bytecode matches the reviewed code.

Findings and their status

The report lists no critical, high or medium findings. Acknowledged means the behavior was accepted, not fixed. An audit does not guarantee the absence of other vulnerabilities or economic risks.

An auction's maximum payment and epoch checks do not supply a minimum USDG output. Its USDG balance can also include direct donations, so sale volume alone does not prove earned mining revenue. Read the report for the exact affected code and auditor reasoning.

Check the version you use

These docs and the generated API reference describe repository source. A live deployment may use a different revision, and code changed after the reviewed scope needs separate assessment.

Check the configured deployed addresses, verified contract source and deployment revision. Check the live Mine revenue destination, fee settings and controller owner as well: team controls can change the destination of future mining payments, and the recipients of swap fees including unclaimed ones, without changing the token address.

See Authority after launch and Risks and mechanics before participating. The current deployment's network and mock-asset disclosures remain applicable independently of the audit.