Docs/Environments

Creating an Environment

Provision an isolated environment with the accounts, assets, and network behavior you need.

Environments are created from a declarative specification. You can write the specification by hand, generate it from a template, or derive it from an existing environment's snapshot.

Minimal specification

nome.env.yamlyaml

name: checkout-flow
chain: evm
network:
  blockTime: 2s
  baseFee: 12 gwei
accounts:
  - id: deployer
    balance: 1000 ether
  - id: user_1
    balance: 250 ether
  - id: user_2
    balance: 250 ether

terminalbash

nome env create --spec nome.env.yaml

From a template

Templates capture common starting points: a plain EVM chain, a DeFi-style setup with reference assets and a router, or a minimal account set for contract unit tests.

terminalbash

nome env create --template defi-basic --name "pricing-tests"

From a snapshot

Any snapshot can seed a new environment. This is the recommended way to branch: keep a canonical baseline and fork it for each experiment.

terminalbash

nome env create --from snap_9a1e --name "experiment-42"

Lifecycle

Status	Meaning
provisioning	The environment is being materialized from its specification.
ready	Accepting operations.
running	A run is currently executing.
paused	Frozen; no operations accepted until resumed.
archived	Snapshots retained; compute released.

TipEnvironments idle for longer than your plan's retention window are archived automatically. Snapshots are retained and the environment can be restored on demand. See Limits.