RTNC Testnet & Regtest Setup Guide

How to configure and use RTNC Testnet and Regtest environments in a safe, non-production context.

1. Overview

RTNC provides multiple network modes for learning, experimentation, development, and safe testing. These environments behave similarly to mainnet but do not reflect real-world conditions.

Units in these networks are:

  • for testing only
  • not intended for external use
  • separate from mainnet operation

This guide explains how to configure, run, and interact with Testnet and Regtest environments.

2. Types of Networks

Mainnet (Permanent Network)

The live RTNC network. All activity is irreversible once confirmed.

Use only after becoming comfortable with Testnet and Regtest.

Testnet (Public Testing Network)

A public environment designed to replicate mainnet behavior while allowing safe experimentation.

Typical uses include:

  • testing wallet behavior
  • multi-node interactions
  • transaction propagation
  • mining configuration and software checks
  • instant block generation
  • reproducible scenarios
  • isolated testing
  • ideal for automation and script development

Testnet units exist solely for testing and do not interact with external platforms.

Regtest (Local Development Network)

A private, controlled environment running entirely on your own machine.

Benefits include:

Regtest units are for local experimentation only.

3. Enabling Testnet or Regtest

RTNC Core uses the configuration file rtnc.conf.

Edit or create the file in:

  • Windows: %APPDATA%\RTNC\rtnc.conf
  • macOS/Linux: ~/.rtnc/rtnc.conf

To enable Testnet:

testnet=1

To enable Regtest:

regtest=1

Restart rtncd after updating configuration.

4. Obtaining Testnet Units

Testnet units are used only for experimentation.

Common methods:

4.1 Testnet Faucet

Public faucets may provide small amounts of test units for development.

These units function only within the Testnet environment.

4.2 Mining on Testnet

Mining on Testnet is useful for learning how mining software behaves.

To view node mining info:

rtnc-cli getmininginfo

4.3 Viewing Balances

rtnc-cli getwalletinfo

5. Working With Regtest

Regtest allows complete control over block creation.

5.1 Generating Blocks

To generate one block:

rtnc-cli generatetoaddress 1 <youraddress>

To generate 101 blocks:

rtnc-cli generatetoaddress 101 <youraddress>

These commands:

  • create blocks locally
  • advance the chain immediately
  • assign resulting regtest units to the provided address

This is useful for development, testing transactions, and simulating confirmations.

6. Switching Between Networks

Each network maintains its own data directory.

It is recommended to keep environments separate.

Example configuration directories:

  • Mainnet: ~/.rtnc/
  • Testnet: ~/.rtnc/testnet3/
  • Regtest: ~/.rtnc/regtest/

Switch networks by adjusting rtnc.conf and restarting the node.

7. Troubleshooting

Node not starting?

Check configuration for conflicting parameters.

No peers on Testnet?

Ensure outbound connections are allowed.

Cannot generate blocks on Regtest?

Verify regtest=1 is enabled.

Wallet not showing units?

Ensure you are checking the correct network environment.

8. Summary

Testnet and Regtest allow safe, predictable experimentation with RTNC.

Use Regtest for rapid, isolated development and Testnet for real-world-like behavior.

Move to mainnet only after gaining confidence in your setup and understanding of the protocol.