DAARX / Public Testnet

Public Testnet

Bring curiosity.
Leave real funds out.

The first public Testnet will be a place to run the software, find faults and help test recovery. Entry is not open yet.

CURRENT STAGE Public Testnet preparation
PARTICIPATION Not open
TEST COINS No monetary value

01

What you’ll be able to test.

The supported release will define exactly which platforms, chains and features are available. No participant package is published here yet.

RUN

A node or miner.

Verify a release, join the published network configuration, and test the supported mining and transaction paths. Hardware and operating-system support will be stated in the release.

USE

A test wallet.

Create a separate wallet, receive valueless test coins, send transactions and exercise the supported backup and recovery flow. A test balance is not a mainnet allocation.

BREAK & REPORT

Find the rough edges.

Record reproducible failures within the published test scope. Public Testnet participation and a paid security bounty are different programs.

02 / BEFORE ENTRY OPENS

You should have
the whole starting kit.

  1. Verify what you download.

    Exact version, supported source, hashes, signatures and build instructions.

  2. Know which network you are joining.

    Configuration, bootstrap peers, test-coin access and observation tools.

  3. Know how to recover.

    Wallet backup, installation, restart, incident and reset instructions.

  4. Know where reports go.

    Published scope, reporting route, known issues and support boundaries.

03 / EXPECTATIONS

Things will break.
That’s why we test.

Test networks can reset. Software can lose state, fail or change format. Use separate test wallets and never put an existing seed, mainnet key, real funds or sensitive personal data into a test workflow.

Offline cash, games, mobile apps, hardware and reward programs will only be included when separately supported. Their existence in development is not a public availability claim.

There is no Testnet signup form on this page. Hardware interest is kept separate.