Mainnet deployment

Launch your Stacks dApp on mainnet with stacksdapp deploy — production checklists, fee estimation, and safe Clarity smart contract deployment.

Deploy your production dApp to Stacks mainnet.

Mainnet deployments are permanent and costly. Test thoroughly on testnet first.

Contents

• Requirements
• Security checklist
• Configure mainnet settings
• SIP token mainnet requirements
• Deploy to mainnet
• Start production frontend
• Post-deployment
• Emergency procedures
• Costs

Requirements

Requirement	Notes
Mainnet STX	Deployment and transaction fees
Mainnet sBTC	Only if your contracts use it
Deployer mnemonic	In contracts/settings/Mainnet.toml

Security checklist

• Comprehensive testnet testing completed
• All contracts audited (recommended)
• Emergency functions implemented
• Upgrade mechanisms planned
• Sufficient STX for fees
• Real mnemonics never committed to git (pre-commit hook enabled)

Configure mainnet settings

Add your mainnet mnemonic to Mainnet.toml:

[accounts.deployer]
mnemonic = "your mainnet seed phrase"
derivation = "m/44'/5757'/0'/0/0"

Store production keys in a secrets manager or gitignored file when possible. The bundled pre-commit hook blocks likely seed phrases in tracked settings files.

SIP token mainnet requirements

For SIP-010 and SIP-009 tokens created with stacksdapp add --template sip010|sip009, uncomment the (impl-trait …) line in the contract before mainnet deploy:

Standard	Mainnet impl-trait
SIP-010	'SP3FBR2AGK5H9QBDH3EEN6DF8EK8JY7RX8QJ5SVTE.sip-010-trait-ft-standard.sip-010-trait
SIP-009	'SP2PABAF9FTAJYNFZH93XENAJ8FVY99RRM50D2JG9.nft-trait

Templates ship without impl-trait so testnet deploy succeeds. Mainnet requires it for wallet listing.

Deploy to mainnet

stacksdapp check && stacksdapp generate && stacksdapp test
stacksdapp deploy --network mainnet --yes

Review fees and contract list first:

stacksdapp deploy --network mainnet --dry-run

Monitor deployment on Stacks Explorer.

Start production frontend

stacksdapp dev --network mainnet

Post-deployment

• Update frontend with mainnet addresses
• Monitor contract interactions
• Plan for future upgrades

Emergency procedures

If issues arise:

1. Pause contract functions (if implemented)
2. Assess impact
3. Deploy fixes as new contract versions
4. Communicate with users

Costs

• Deployment: ~0.1-1 STX per contract
• Function calls: variable based on complexity
• Storage: paid by contract owner initially

Monitor fees on Stacks Explorer.