You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse every top-level command and its most important flags. For wallet, template, and transaction details see also API_REFERENCE.md.
Global options
Flag
Description
-q, --quiet
Suppress banner and decorative output
--log-format human|json
Structured log format (default: human)
--log-dir <PATH>
Optional rotating log directory
--correlation-id <ID>
Tie every log line of this invocation together (8–64 chars of [A-Za-z0-9_-]); defaults to $STARFORGE_CORRELATION_ID or a generated value — see CORRELATION_IDS.md
Create and store a keypair (--fund, --encrypt, --mnemonic)
list
List saved wallets
show <NAME>
Show wallet metadata and balance (--reveal)
fund <NAME>
Fund via Friendbot when configured
remove <NAME>
Delete a saved wallet
rename <OLD> <NEW>
Rename a wallet entry
merge
Account merge (--from, --to, --yes)
rotate <NAME>
Rotate keys in place (--fund, --encrypt, --mem, --iterations)
export <NAME> --output <FILE>
Export backup JSON
import
Import from file or --mnemonic
sign
Sign a payload with a saved wallet
multisig
Multisig helpers (create, add-signer, submit)
import --file accepts a plaintext backup JSON or an encrypted bundle, detected
automatically. See WALLET_IMPORT_SECURITY.md for the
limits enforced on untrusted backup files.
multisig
Subcommand
Purpose
wizard
Interactive transaction proposal builder
create
Create a proposal with threshold, signers, metadata, and optional transaction XDR
status <FILE>
Show visual signature collection progress
verify <FILE>
Validate signatures, duplicates, pending signers, and threshold readiness
notify <FILE>
Queue signature request notifications for pending signers
export <FILE> / import <FILE>
Share proposal JSON between signers
templates / from-template
Use common scenarios like escrow, company treasury, DAO, vault, and payment
--simulate and --dry-run print the simulated CPU, memory, and ledger
footprint alongside the minimum resource fee and a recommended fee that
includes a safety margin. See SIMULATION_RESOURCES.md.
JSON/TOML contract test suite with fixtures, mocks, and assertions
--source <FILE>
Contract source used for generated tests or coverage
--coverage
Include source coverage summary
--coverage-out <FILE>
Write a dedicated coverage report
--coverage-format html|json|markdown|text
Format for --coverage-out
--coverage-goal <PCT>
Minimum overall coverage percentage
--function-coverage-goal <PCT>
Minimum function coverage percentage
--line-coverage-goal <PCT>
Minimum line coverage percentage
--branch-coverage-goal <PCT>
Minimum branch coverage percentage
--coverage-ci
Fail when configured coverage goals are missed
--coverage-ci-workflow-out <FILE>
Generate a GitHub Actions coverage workflow
--report html|json|junit
Write a test report (junit is available for fixture suites)
--testnet
Validate Soroban testnet integration for the run
--testnet-dry-run
Validate testnet configuration without probing RPC health
starforge test --wasm ./target/contract.wasm \
--fixture ./contract-tests.json --coverage --source ./src/lib.rs --report html
starforge test --wasm ./target/contract.wasm --source ./src/lib.rs \
--coverage --coverage-out coverage.html --coverage-format html \
--coverage-ci --coverage-goal 85 --branch-coverage-goal 70
starforge test --wasm ./target/contract.wasm --source ./src/lib.rs \
--coverage-ci-workflow-out .github/workflows/starforge-coverage.yml
starforge test --wasm ./target/contract.wasm \
--fixture ./contract-tests.toml --testnet --testnet-dry-run
Fixture suites support named storage fixtures, mocked contract calls, and assertions such as state_equals, state_exists, return_equals, event_emitted, fee_at_most, and mock_called.
Coverage analysis tracks Soroban contract functions, line spans, branch paths, uncovered functions, threshold goals, and HTML/JSON/Markdown/text reports.
The artifact profiler reports estimated execution time, memory usage, bottlenecks,
baseline regression detection, comparison deltas, and a dashboard summary.
docs
AI-assisted documentation generation for Soroban contracts (issue #499).
Subcommand
Purpose
docs generate <CONTRACT> --source <FILE.rs>
Generate comprehensive Markdown docs from rustdoc + AI enrichment
External tools are optional. StarForge runs built-in Soroban heuristics every time and records whether Slither/Mythril were completed, failed, skipped, or unavailable.
upgrade
Subcommand
Purpose
upgrade prepare
Validate upgrade WASM (--contract-id, --wasm)
upgrade auto compat
Compare old/new WASM ABI and storage layout (--old-wasm, --new-wasm)
upgrade auto plan
Generate compatibility-aware upgrade plan and migration template
upgrade propose
Create governance proposal
upgrade list / status
List pending proposals
upgrade approve
Approve proposal
upgrade execute
Execute approved upgrade
upgrade rollback
Roll back contract version
upgrade history
Show upgrade history
governance
Contract upgrade governance with voting, timelock, audit trail, and emergency upgrades.
Event stores use JSON Lines. Replay skips malformed records and deduplicates events by
network, contract ID, and Soroban event ID. Triggers inherit event metadata through
STARFORGE_NETWORK, STARFORGE_CONTRACT_ID, STARFORGE_EVENT_ID,
STARFORGE_EVENT_LEDGER, STARFORGE_EVENT_TYPE, STARFORGE_EVENT_TOPIC, and
STARFORGE_EVENT_VALUE. Treat trigger commands as trusted local code; they are disabled
unless --allow-triggers is explicitly provided.