Ravelnonce logo featuring a gold network emblem and wordmark
Single-hosted testnet / v1

Ravelnonce, with signal.

Ravelnonce runs hosted HTTP testnet nodes with signed transactions, spendable UTXOs, proof-of-work block checks, and public explorer and status reads. Separately configured nodes can discover and authenticate HTTPS peers that submit validated block batches; higher-tip announcements trigger bounded block catch-up, while fork choice and production mainnet behavior remain out of scope.

Testnet v1 rules are implementation choices, not approved mainnet parameters.

Concept diagramRNV / 01
Illustrative Ravelnonce testnet peer connectivity and validated block batchesMINERNODEWALLETROUTETXBLOCKSETTLE
Concept illustration · authenticated peer links and validated block batches
01Proof of work
02Public settlement
03Fee design goal
Proof-of-work design
Public settlement direction
Predictable fees goal

01 / Participation

Choose a place to start.

Each hosted testnet node validates proof-of-work blocks and signed UTXO spends on its own append-only chain. Authenticated higher-tip announcements trigger bounded requests for missing canonical blocks; nodes do not choose forks or reorganize. Predictable fees remain a design goal, not a guarantee. The protocol page separates checked-in issuance facts from testnet implementation choices.

01

For users

Use the network

Look up confirmed testnet UTXOs by public address. This browser wallet is read-only and never handles private keys.

Check a wallet balance
02

For miners

Mine

Run the local CPU miner demo with ephemeral keys held in memory and a disposable PostgreSQL database. It mines locally and submits signed spends to the single hosted testnet node.

Read the mining guide
03

For developers

Build with the API

Use strict JSON endpoints to read persisted testnet state and submit signed transactions and candidate blocks to the single hosted testnet node.

Open the API reference

02 / Public resources

What is available today.

The explorer reads this node's persisted chain, while status also reports recent authenticated peer handshakes. Connected peers can submit contiguous validated block batches, and the local CLI can mine blocks and submit signed spends against a disposable PostgreSQL database. Nodes do not relay transactions, request missing ranges, store side branches, or reorganize.

Predictable fees remain a design goal
01

Testnet protocol

Checked-in issuance facts and explicit v1 testnet rules with byte-level vectors.

Read testnet rules
02

Explorer

Read persisted blocks, signed transactions, and confirmed address UTXOs from this node.

Open explorer
03

Network analytics

Read the latest validated block and scoped fees from confirmed regular transactions in explorer activity.

View analytics
04

Network status

View this node’s active tip, fee rule, and measured peer handshakes.

View network status
05

Read-only wallet

Look up a checksummed testnet address balance. Browser key generation remains disabled.

Open wallet
06

Testnet faucet

Record a testnet-funds request and check its pending history. Submission does not confirm a transfer.

Request testnet funds
07

Local miner demo

Run the CLI with ephemeral keys against a disposable database and exercise accepted and rejected requests.

Run the demo
08

Payment request composer

Create a shareable link with a Ravelnonce address, amount, and optional memo. The link does not send or collect payment.

Compose a payment request

03 / Questions

Follow what is documented.

The public protocol page separates checked-in issuance facts from the testnet choices needed to make this node reproducible. Start with the rule vectors or run the demo.

Read the public specification
Review the v1 byte layouts, transaction and block rules, target calculation, and preserved issuance schedule.Read the FAQ
Talk protocol
Bring a use case, a mining perspective, or a developer question. The next useful conversation starts here.ravelnonce@polsia.app

Open channel

Ask about the published direction.

Contact Ravelnonce