Mainnet Readiness

Mainnet deployment is a release process, not a single transaction. Contracts, scripts, UI constants, backend services, Cloudflare configuration, and docs must all point to the same production state.

Must Pass

• All Solidity tests pass under the intended Foundry profiles.
• BSC fork simulations pass for launchpad, Mine, lending, and revenue routing.
• Static analysis findings are resolved or explicitly accepted.
• Deployment scripts are idempotent where practical and fail loudly on missing configuration.
• Verification scripts confirm owners, dependencies, oracle feeds, fees, LTVs, penalties, hooks, routers, and recipient addresses.
• UI contract constants and generated ABIs match final deployed contracts.
• Backend services are live on the production domain and return JSON health responses.
• Cloudflare Pages builds pass from GitHub on every push.

Deployment Hygiene

• Use a dedicated deployer key.
• Keep enough BNB available for deployment, verification, and retry gas.
• Confirm every external BSC address immediately before broadcast.
• Run scripts first against a fork using the final environment values.
• Save deployment outputs and transaction hashes.
• Update documentation in the same release as contract or address changes.

Post-Deploy Checks

• Read all deployed contract configuration from chain.
• Connect the UI to the deployed addresses and run a production dry run.
• Verify mint quotes, borrow limits, launch previews, claim actions, and admin pages.
• Confirm revenue routing permissions and redirect rules.
• Confirm monitoring, RPC fallback, and backend restart behavior.