← Back to Blog

Introducing Efficient Testnet Workflows

Replicate mainnet conditions with minimal setup using new in-place and multi-node features.

Danny Salman 1 min read

We are pleased to announce that the results of two completed bounties, in-place testnet creation and multi-node support, completed by likesToEatFish, have now been integrated into Ignite.

These new features deliver a testing environment that mirrors mainnet conditions with minimal setup. The Ignite CLI automates complex processes so builders can manage validator nodes and deploy realistic local testnets with ease. The updated commands open a direct path to high-fidelity testing. Builders can validate forked chain behavior, debug validator configurations, or experiment with network topologies that include additional validators—all without leaving the Ignite ecosystem or writing extensive custom logic.

Here's a glimpse of how they work:

In-Place Testnet Creation

In-place testnets apply state transitions automatically and remove the need for manual genesis file edits. This feature lets you replicate mainnet conditions using current validator definitions and keys. Updates in ignite/cmd/testnet_inplace.go and ignite/services/chain/testnet.go focus on the TestnetInPlace() routine, which loads chain data, retrieves keyring addresses, mints tokens, and reinitializes state.

Initialize your in-place testnet by running:

ignite testnet in-place

Multi-Node Testnet

Multi-node support organizes per-node logs and ports into discrete folders and eliminates the need for custom scripts or complicated configurations. As a result, you can spin up a testnet that accurately reflects mainnet conditions. A new subcommand in ignite/cmd/testnet_multi_node.go enables creation of multiple validator nodes in one pass. An interactive interface in ignite/cmd/bubblemodel/ displays real-time logs for each node and supports start, stop, and restart operations from a single terminal. Behind the scenes, chain.MultiNodeArgs and methods in ignite/pkg/chaincmd/in-place-testnet.go configure validator directories, ports, and logs to simplify the simulation of multi-validator networks.

Launch your multi-node testnet using:

ignite testnet multi-node

What's Next?

Check out the new App Challenge offering a bounty for extending Ignite to create new Ignite Apps. We invite builders to create Ignite Apps that expand the Ignite CLI’s functionality, with a reward for the first three submissions that fully meet the Challenge criteria.

Feb 19, 2025 - Last edited Feb 20, 2025