Getting Started
Start building on NOXY: live testnet parameters, the public /v0 API, the faucet, the TypeScript SDK, and the browser wallet.
Getting Started
NOXY is a post-quantum Layer 1 blockchain. Accounts sign with ML-DSA-44 (FIPS 204), validator certificates use hybrid ML-DSA-44 + Ed25519, digests are BLAKE3 with domain prefixes, and state lives in a sparse Merkle tree over 256-bit BLAKE3 paths. Consensus combines DAG availability and ordering with checkpoint-certificate finality.
The core node repository is closed until mainnet, when it becomes source-available. You do not build or run a node to get started: everything on this page works against the live public testnet.
The live testnet
| Parameter | Value |
|---|---|
| chain_id | veylith-testnet-10 |
| protocol_version | 4 |
| release | 0.1.x |
| block_time_target_millis | 250 |
| validators | 4 |
| native asset | tNOXY |
What is public today
- The public HTTP API at
https://test.noxycore.io, all routes under/v0. See the RPC reference. - The faucet at /faucet for tNOXY.
- The TypeScript SDK,
@noxy/core: canonical transaction encoding, BIP-39 to ML-DSA-44 key derivation, and account-verifier word derivation. - The browser wallet.
First API calls
# Liveness
curl https://test.noxycore.io/v0/health
# Chain identity
curl https://test.noxycore.io/v0/node/identity
# {"chain_id":"veylith-testnet-10","protocol_version":4,...}
# Network stats
curl https://test.noxycore.io/v0/network/stats
Account state is read per account:
curl https://test.noxycore.io/v0/account/{account_id}
curl https://test.noxycore.io/v0/account/{account_id}/nonce
curl https://test.noxycore.io/v0/account/{account_id}/balance/{asset}
Transactions are submitted with POST /v0/tx/submit and looked up with GET /v0/tx/{hash}. The full route table, request shapes, and error semantics are in the RPC reference.
Get test funds
- Create an account with the browser wallet or the
@noxy/coreSDK. - Request tNOXY at /faucet.
- Confirm the balance with
GET /v0/account/{account_id}/balance/{asset}.
Running a node
Node operation is currently limited to the closed validator set that runs the testnet. A public validator program with signed binaries and a Docker image opens later.
Node startup is identity-bound: a node refuses to start against a mismatched chain_id or genesis hash, and refuses a database stamped by a different chain, so a misconfigured operator cannot silently join the wrong network.
Next steps
- Protocol architecture: consensus, transaction envelope, cryptography
- Wallets and keystores: key derivation and the keystore format
- RPC reference: full endpoint table with request and response shapes
- Run a validator: validator key roles and the current operator model