# Testnet Commands

In addition to the commands for running a node, the `blockxd` binary also includes a `testnet` command that allows you to start a simulated test network in-process or to initialize files for a simulated test network that runs in a separate process.

### Initialize Files <a href="#initialize-files" id="initialize-files"></a>

The `init-files` subcommand initializes the necessary files to run a test network in a separate process (i.e. using a Docker container). Running this command is not a prerequisite for the `start` subcommand.

This is similar to the `init` command when initializing a single node, but in this case we are initializing multiple nodes, generating the genesis transactions for each node, and then collecting those transactions.

In order to initialize the files for a test network, run the following command:

```bash
blockxd testnet init-files
```

You should see the following output in your terminal:

```
Successfully initialized 4 node directories
```

The default output directory is a relative `.testnets` directory. Let's take a look at the files created within the `.testnets` directory.

### Gentxs <a href="#gentxs" id="gentxs"></a>

The `gentxs` directory includes a genesis transaction for each validator node. Each file includes a JSON encoded genesis transaction used to register a validator node at the time of genesis. The genesis transactions are added to the `genesis.json` file within each node directory during the initialization process.

### Nodes <a href="#nodes" id="nodes"></a>

A node directory is created for each validator node. Within each node directory is a `blockxd` directory. The `blockxd` directory is the home directory for each node, which includes the configuration and data files for that node (i.e. the same files included in the default `~/.blockxd` directory when running a single node).

### Start Testnet <a href="#start-testnet" id="start-testnet"></a>

The `start` subcommand both initializes and starts an in-process test network. This is the fastest way to spin up a local test network for testing purposes.

You can start the local test network by running the following command:

```bash
blockxd testnet start
```

You should see something similar to the following:

```
acquiring test network lock
preparing test network with chain-id "blockx_1276974-1"


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++       THIS MNEMONIC IS FOR TESTING PURPOSES ONLY        ++
++                DO NOT USE IN PRODUCTION                 ++
++                                                         ++
++  sustain know debris minute gate hybrid stereo custom   ++
++  divorce cross spoon machine latin vibrant term oblige  ++
++   moment beauty laundry repeat grab game bronze truly   ++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


starting test network...
started test network
press the Enter Key to terminate
```

The first validator node is now running in-process, which means the test network will terminate once you either close the terminal window or you press the Enter key.&#x20;

In the output, the mnemonic phrase for the first validator node is provided for testing purposes. The validator node is using the same default addresses being used when initializing and starting a single node (no need to provide a `--node` flag).

Check the status of the first validator node:

```bash
blockxd status
```

Import the key from the provided mnemonic:

```bash
blockxd keys add test --recover
```

Check the balance of the account address:

```bash
blockxd q bank balances [address]
```

Use this test account to manually test against the test network.

### Testnet Options <a href="#testnet-options" id="testnet-options"></a>

You can customize the configuration of the test network with flags. In order to see all flag options, append the `--help` flag to each command.