← Back to rupix.network  ·  Forge guide  ·  Español

How to join the Rupix testnet

Connect your node to the test network. You don't need to be an expert — just follow the steps.
Why run your node?
A node is your computer keeping a live copy of Rupix and talking to the others. Every running node checks that nobody lies, that the rules are followed and that the network stays up. The node isn't a detail: it's what makes Rupix really exist.

You don't need to leave it on 24 hours a day. Whenever you use your computer, start your node — make it a habit: turn on the computer, turn on your node. The more active nodes, the stronger and harder to take down the network becomes.

If you believe in this project, support it by running your node. One more day online is one more pillar standing.
Rupix testnet is a TEST network. Testnet coins (RUPIX) have NO real value. It's for testing, learning and helping strengthen the network before mainnet. Thanks for joining!
⚠️ Windows vs Linux/Mac: the commands use ./ (Linux/Mac). In Windows PowerShell, use .\ instead of ./, for example: .\rupixd.exe. Without ./ or .\, the system can't find the program. (Thanks to JC for the tip! 🙌)

Step 1 — Download Rupix

Go to the official downloads: github.com/rupixnet/rupixd/releases/latest (always the latest version — don't use older ones)

Download the file for your system:

Unzip it. Inside there are 4 programs: rupixd (the node), rupixctl (control), rupixwallet (wallet), rupixminer (miner).

Step 2 — Start your node and connect

Open a terminal in the folder where you unzipped Rupix and run:

Linux / Mac:

./rupixd --testnet --utxoindex --addpeer=178.104.69.148:17211

Windows:

.\rupixd.exe --testnet --utxoindex --addpeer=178.104.69.148:17211

Your node will connect to the seed node and start syncing. You'll see lots of messages — that's normal. When it catches up with the latest block, you're on the network! 🎉

Step 3 — Check that you're connected

In ANOTHER terminal (leave the node running), run:

./rupixctl --testnet GetBlockDagInfo

You should see networkName: "rupix-testnet" and blockCount going up. Compare it with the official explorer. When they're close, you're up to date.

Step 4 (optional) — Mine Rupix

About mining: Rupix uses RupixHeavyHash, its own algorithm derived from Kaspa's engine (kHeavyHash; Rupix is a fork of kaspad) with its own seed. You can mine with your CPU or GPU, and on testnet your computer can win blocks. What matters most right now is running your node (steps 2-3); mining is an extra that also helps the network.

RupixHeavyHash stops the industrial machines built for Kaspa from mining Rupix — a fair start so everyone begins on equal footing. Honestly: it's an advantage of months, not an eternal barrier; an FPGA can be reprogrammed.

Create your wallet (only once):

./rupixwallet --testnet create

Start the daemon and leave it running in its own window:

./rupixwallet --testnet start-daemon

In another window, create your address:

./rupixwallet --testnet new-address
About the keys file: if you start the daemon with --keys-file=PATH, the send command must also use the same --keys-file=PATH (it signs locally with those keys). The other commands (new-address, balance, gems, forge) do NOT take it: they ask the daemon. If you don't use --keys-file anywhere, everything uses the default file and there's nothing to worry about.

Copy your address (it starts with rupixtest:...) and start the miner:

./rupixminer --testnet --miningaddr=YOUR_ADDRESS_HERE

Problems?

Don't trust. Verify — from genesis.
rupix.network · github · explorer