Skip to content

Deploying Contracts

Deploying a Neo N3 smart contract requires two artifacts produced by neo-solc:

  • <contract>.nef -- the NeoVM bytecode
  • <contract>.manifest.json -- the ABI, permissions, and metadata

This page covers the Neo N3 deployment model, local deployment with Neo-Express, constructor arguments, contract upgrades, and production deployment considerations.

Sections

Section
Neo N3 Deployment Model
Local Deployment with Neo-Express
Constructor Arguments
Contract Upgrade Lifecycle
Manifest Verification Before Deploy
TestNet Deployment
MainNet Considerations
Common Deployment Errors
Automated Smoke Tests
Related Pages

MIT Licensed