Skip to main content
The init command creates project-local scaffolding for Erst debugging workflows.

​
Usage

erst init [directory]

​
Description

This command generates:
  • erst.toml configuration file
  • .gitignore entries for local artifacts
  • Directory structure for traces, snapshots, overrides, and WASM files
When run in an interactive terminal, it launches a setup wizard to configure the preferred RPC URL and network passphrase.

​
Examples

erst init

​
Flags

​
--force
boolean
default:"false"
Overwrite existing configuration files
​
--network
string
default:"public"
Network to configure: public, testnet, futurenet, or standalone
​
--rpc
string
Custom RPC URL to use
​
--network-passphrase
string
Custom network passphrase
​
--interactive
boolean
default:"true"
Run interactive setup wizard (auto-detects terminal)Alias: -i

​
Interactive wizard

When run in an interactive terminal, erst init launches a setup wizard that guides you through:
1

Select network

Choose from public, testnet, futurenet, or standalone
2

Configure RPC URL

Enter custom RPC endpoint or use network defaults
3

Set network passphrase

Optionally specify custom network passphrase
4

Confirm settings

Review and confirm configuration before creating files

​
Generated structure

After running erst init, your project will contain: 
.
├── erst.toml           # Main configuration file
├── .gitignore          # Updated with erst artifacts
└── .erst/
    ├── traces/         # Saved execution traces
    ├── snapshots/      # Ledger state snapshots
    ├── overrides/      # Custom state overrides
    └── wasm/           # Local contract WASM files

​
Configuration file

The generated erst.toml includes: 
# Network configuration
network = "testnet"
rpc_url = "https://soroban-testnet.stellar.org"

# Simulator settings
[simulator]
max_cpu_insns = 100000000
max_memory_bytes = 41943040

# Cache settings
[cache]
enabled = true
max_size_mb = 500
  • doctor - Verify Erst environment setup
  • upgrade - Simulate contract upgrades