Skip to main content
Version: Next

Mainnet Deployment Guidelines

In order to deploy your smart contracts to the mainnet, you need to register, fund, and setup a new account.

info

This account will be used for production purposes. Make sure you handle keys appropriately. Using a Key Management Service is the best practice.

Creating an Account​

There are two simple methods of creating an account on testnet. Interactive and Manual, both use the flow CLI. On mainnet you will have to fund your newly created account, there is no faucet. Make sure to install the Flow CLI. Flow CLI has a interactive mode for generating keys.

tip

Anyone can deploy and update contracts on mainnet. Audits are encouraged but not mandatory to deploying contracts to mainnet. Take every precauction to reduce issues and protect users.

Create and deploy a mainnet project​

  • Highly encouraged to test on Testnet, have strong smart contract test coverage and follow any additional guidelines set out here: Smart Contract Testing Guidelines.
  • Follow the Flow CLI instructions to Create a Project. You have the Flow CLI installed and ran flow init or flow setup in your project folder and generating a flow.json file
  • Mainnet account: You completed the mainnet account setup, (see above) and have your key pair and mainnet address ready.
  • Deploy your project, notice that your account now has contracts deployed on mainnet.
  • Deploy a contract to mainnet. You can deploy contracts individually using the account-add-contract command.
info

All your contract deployment addresses are stored in flow.json. Mainnet, Testnet and local (emulator) are stored as well.

Deploy updated contracts on mainnet​

Contracts can be updated and retain the contract address. You can use the Flow CLI contract update command to re-deploy an updated version of your contract:

warning

If you see Error Code: 1103, your new account does not have enough funds to complete the transaction. Make sure you have enough FLOW and your account is set up correctly, check account explorer to verify Getting Started.

Once all your contracts are deployed, you can visit flow-view-source or run the Flow CLI get account command to confirm the deployment.

Sporks​

Currently, historical event data is not migrated between sporks, so you'll need to design your application with this in mind. We recognize the usefulness of historical event data and plan on adding a means of accessing it in the near future. Past spork transactional data is available, See Previous Spork Access Node Info

More Information on Sporks