Generation & audit
Contract generation, compilation, and the three-layer audit.
Once you approve the spec, Token Launcher generates the contract, compiles it, and runs a three-layer audit, all before deploy is available. On-chain bugs are permanent, so review stands between the spec and mainnet by design.
This page covers the EVM path. Solana launches have no contract to write or compile; pump.fun and SPL launches run through Solana's existing, audited token programs. See Launching on Solana.
Generation
Modus writes the Solidity contract from your spec using launch-pattern templates and OpenZeppelin imports, applying your taxes, limits, trading toggle, and any blacklist/whitelist controls. The source is written to the workspace and shown in the file panel. (Constructors use msg.sender as the owner, not a passed-in address.)
Compile
The contract is compiled in the container. If it fails, Modus fixes and recompiles; on a clean compile, the ABI and bytecode are saved.
The three-layer audit
Every contract is audited across three independent layers before deploy:
| Layer | Tool | Checks |
|---|---|---|
| Static | Pattern analysis over known vulnerability classes (SWC rules) | Reentrancy, tx.origin auth, and other common Solidity pitfalls |
| Semantic | AI review | Logic errors, comparison vs similar projects |
| Conformance | Rule engine | Token controls match the spec |
Findings are merged and de-duplicated, then summarized by severity (critical / high / medium / low / info) in the file panel.
The gate before deploy
Deploy doesn't unlock on a clean compile alone. Before a contract can go on-chain, Modus checks that it actually implements every feature in your approved spec, compiles it, runs its tests, and requires every critical or high audit finding to be fixed. You can't waive that with "just deploy"; the gate holds until the findings are resolved.
Stale detection
Each audit records a hash of the source. If the contract changes afterward, the audit is marked potentially out of date and Modus re-audits rather than trusting a stale result.
Live guidance chips
As your spec changes, Modus surfaces warning chips:
| Rule | Condition | Severity |
|---|---|---|
| Snipe risk | Trading enabled at deploy with no liquidity plan | danger |
| High tax | Over 5% | warn |
| Very high tax | Over 10% | danger |
| Comparables | Similar projects exist | compare |
Click a chip and Modus walks you through the issue in chat. Change the spec to resolve it and the chip clears; you can also dismiss one.