Question 1

What is Ravelnonce?

Accepted Answer

Ravelnonce is a proof-of-work project. This app delivers one hosted HTTP testnet node with an append-only chain, signed transactions, spendable UTXOs, a miner demo, and public explorer and status pages. It is not a peer-to-peer network or production mainnet.

Question 2

Which protocol rules are implemented?

Accepted Answer

The checked-in issuance schedule is preserved. For testnet v1, the implementation chooses the ravelnonce-testnet-v1 chain ID, a fixed zero-reward genesis block, SHA-256d IDs and merkle nodes, Ed25519 spends, canonical big-endian encodings, a checksummed rvtest1 address, and a bounded proof-of-work retarget. These choices make this testnet reproducible; they do not establish approved production or mainnet rules.

Question 3

What issuance schedule does Ravelnonce use?

Accepted Answer

The target block interval is 2.5 minutes. Mined block heights start at 1. The initial subsidy is 12.5 Ravelnonce (1,250,000,000 atoms), one Ravelnonce is 100,000,000 atoms, and the subsidy halves every 840,000 mined blocks with flooring to whole atoms. Height 0 has no subsidy. There is no tail emission; the scheduled total is 2,099,999,990,760,000 atoms (20,999,999.9076 Ravelnonce).

Question 4

How can I mine and submit a test block?

Accepted Answer

Use a disposable PostgreSQL database, apply the schema with npx prisma db push, start the app with npm run dev, then run node scripts/ravelnonce-testnet.mjs demo --base-url http://localhost:3000. The CLI creates ephemeral keys, mines a valid block, submits a signed transaction and block, and demonstrates rejected spends and blocks. It does not print or save private key material.

Question 5

Can I create or recover a wallet in the browser?

Accepted Answer

No. Browser key generation remains disabled. The local CLI creates ephemeral Ed25519 test keys only; this app defines no recovery phrase, derivation path, wallet backup, script, or multisig format. Do not use the demo keys for funds or production.

Question 6

Does the node connect to other nodes?

Accepted Answer

No. It maintains a single append-only canonical chain and rejects stale, competing, and side-branch blocks. It does not provide peer discovery, P2P transport, synchronization, fork choice, or reorganizations. Its status page reports this app node, not network-wide health.

Question 7

Does the faucet send testnet funds?

Accepted Answer

No. The existing faucet records pending requests and exposes their history, but it has no delivery or confirmation source. A recorded request does not mean that funds were sent.

Question 8

How do I validate the implementation?

Accepted Answer

Run npm run test for rule and route unit tests. With the app running against a disposable PostgreSQL database, run BASE_URL=http://localhost:3000 npm run test:e2e to exercise real block, transaction, explorer, and status flows. The full setup is documented at /docs/mining and in tests/README.md.