deploy-contracts

Deploy Contracts Skill

Overview

This skill guides safe deployment of Move contracts to Aptos networks. Always deploy to testnet before mainnet.

Pre-Deployment Checklist

Before deploying, verify ALL items:

Security Audit ⭐ CRITICAL - See SECURITY.md

• Security audit completed (use security-audit skill)
• All critical vulnerabilities fixed
• All security patterns verified (arithmetic safety, storage scoping, reference safety, business logic)
• Access control verified (signer checks, object ownership)
• Input validation implemented (minimum thresholds, fee validation)
• No unbounded iterations (per-user storage, not global vectors)
• Atomic operations (no front-running opportunities)
• Randomness security (if applicable - entry functions, gas balanced)

Testing

• 100% test coverage achieved: aptos move test --coverage
• All tests passing: aptos move test
• Coverage report shows 100.0%
• Edge cases tested

Code Quality

• Code compiles without errors: aptos move compile
• No hardcoded addresses (use named addresses)
• Error codes clearly defined
• Functions properly documented

Configuration

• Move.toml configured correctly
• Named addresses set up: my_addr = "_"
• Dependencies specified with correct versions
• Network URLs configured

Object Deployment (Modern Pattern)

CRITICAL: Use Correct Deployment Command

There are TWO ways to deploy contracts. For modern object-based contracts, use deploy-object:

✅ CORRECT: Object Deployment (Modern Pattern)

aptos move deploy-object \
    --address-name my_addr \
    --profile devnet \
    --assume-yes

What this does:

1. Creates an object to host your contract code
2. Deploys the package to that object's address
3. Returns the object address (deterministic, based on deployer + package name)
4. Object address becomes your contract address