Docs
Virtual environmentsHow to

How to create a virtual network

Learn how to create a simulator network or localnet with project wallets using Studio or the CLI

Available since: Acton 1.2

Create an isolated network for scripts and application integration tests.

Prerequisites

Create the network

Start Studio from the project root:

acton studio
  1. Open Virtual environmentsCreate environment.
  2. Select Simulator or Localnet and enter a name.
  3. For a simulator, keep Clean network or choose a public-network fork.
  4. Select project wallets under Startup accounts, or clear the selection for no startup wallets.
  5. Select Create environment and wait for readiness. Open the resulting environment.

Studio preselects [localnet].accounts, but initializes only the wallets submitted in the form. Each selected wallet starts with 100 GRAM.

Studio environment creation and startup account selection

Start a persistent network on port 5411:

acton simulator start --port 5411 --db-path .acton/simulator.sqlite --accounts deployer

The deployer must be a configured wallet. Omit --accounts to use [localnet].accounts, or pass --accounts "" to select none. Keep this terminal open.

In another terminal, inspect readiness:

acton simulator status --port 5411 --json

Configure defaults in Acton.toml; explicit flags override them.

Create a named network and leave it running in the background:

acton localnet start dev --port-base 19000 --accounts deployer --detach
acton localnet status dev --json

The command waits for readiness and prints endpoint URLs.

Without --detach, a newly launched service stays in the foreground and Ctrl+C would stop it.

The deployer must be a configured wallet. Omit --accounts to use [localnet].accounts, or pass --accounts "" for no project wallets.

The port range 1900019004 must be free. Omit --port-base to let Acton choose a range.

These options apply to new networks. Resume an existing network without creation options.

Verify and continue

  • In the Studio, confirm the environment is running and open Home.
  • From the CLI, confirm running: true for the simulator or status: "running" for localnet.

Next, connect scripts and applications using the reported URLs.

Last updated on

On this page