Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.solidscipt.zoracle.xyz/llms.txt

Use this file to discover all available pages before exploring further.

The secure-deploy command is the recommended production path. It runs the full verification pipeline — fuzz harnesses, SMTChecker, Slither, invariant tests, and pattern checks — and only proceeds to deployment if every required gate passes. If any gate fails, the process exits with a nonzero status and no transaction is sent. Use it whenever you deploy to a network where a bad deployment has real consequences. 
solidscript secure-deploy <input> -c <contract> -n <network>

​
Arguments

ArgumentDescription
<input>Path to the directory containing your TypeScript contract files

​
Options

FlagDescription
-c, --contract <name>Name of the contract to deploy after all verification gates pass
-n, --network <name>Target network for deployment
-a, --args <args...>Constructor arguments
--artifacts <dir>Custom artifacts directory
--no-fuzzSkip auto-generated fuzz harnesses
--no-smtSkip the SMTChecker gate
--no-slitherSkip Slither static analysis
--no-invariantsSkip invariant tests
--no-patternsSkip the pattern library check

​
Examples

# Full secure deployment to Base Sepolia
npx solidscript secure-deploy contracts -c Counter -n base-sepolia

# Deploy with a constructor argument
npx solidscript secure-deploy contracts -c MyToken -n base-sepolia -a 1000000
Skipping gates with --no-* flags reduces your security coverage. Only omit gates during development iteration — never skip them for a production deployment.