The NuChain — Blockchain, in Plain Talk

You don't need a computer-science degree to verify Our economy. This guide walks You through what a "blockchain" actually is, how everyone else uses one, and how We built Ours differently on purpose. By the end, You'll be able to look at any QN settlement entry and confirm with Your own eyes that no one has rewritten the past.

The 1-Minute Version

How A "Regular" Blockchain Works

Picture a public ledger that everyone on the network keeps a copy of. Every block in the chain has three pieces:

1. A bundle of transactions — "Alice paid Bob 1 BTC", etc.
2. A hash — a fingerprint computed from all of those transactions plus a few extras.
3. The previous block's hash — so each block is literally bolted to the one before it.

Anyone who wants to add a new block must prove they did the work to mint it. On Bitcoin this is called Proof of Work: computers race to guess a number that, when mashed together with the block, produces a hash starting with a bunch of zeros. The race is hard on purpose. The winner gets to add the block AND collect a reward.

Once the block is added, every other computer checks the math and adds the block to their copy. To rewrite history, an attacker would have to redo the work of every block since the one they want to change, on more than half the machines in the network — practically impossible.

How The NuChain Works (Ours)

We kept the part that matters — the fingerprinting — and threw away the parts that don't.

Every time something economically meaningful happens on the platform (a deposit, a withdrawal, a P2P QN transfer, a tCL-Rights mint, a sovereign vote), Our backend writes one row to a MongoDB collection called audit_chain. Each row contains:

{
  "seq":        1428,                           // strictly increasing
  "kind":       "qn_settlement_deposit",        // what happened
  "ref_id":     "3cc96d39-da57-…",              // pointer to the source record
  "prev_hash":  "16d80927b06a5732726d…",        // fingerprint of seq 1427
  "this_hash":  "dd990c110d397ede95ec…",        // fingerprint of THIS row
  "created_at": "2026-06-20T11:54:24Z"
}

The this_hash is a SHA-256 fingerprint of (prev_hash + canonical-payload). If anyone changed even one character of an old row, every this_hash from that row to the end would have to be recomputed in lock-step — and the very latest tip (which we publish openly) wouldn't match anymore.

Why no miners?

We don't need miners because the threat model is different. Bitcoin assumes attackers can be anywhere on the open Internet and own thousands of write-capable nodes. The NuChain is operated under sovereign community governance: the writers are accountable Council roles, the readers are the entire world. So instead of paying for trustless writes with electricity, We pay for it with transparent read endpoints and inviting anyone to download the chain and verify it themselves.

What goes into the chain?

• Every /api/qinote/settlement/* event — deposits, withdrawals, transfers.
• Every tCL-Rights Merkle root publication.
• Every Sovereign Vote outcome.
• Every promotion/demotion of an admin role.

What does NOT go on-chain (intentionally): private messages, password hashes, draft posts. Privacy first; only economically- and governance-significant facts are bolted into the chain.

Side-by-Side: Theirs vs Ours

How to Verify Any Entry Yourself

You don't need any special software. Open Your browser's DevTools (right-click → Inspect → Console) and paste this:

// 1. Pull the public chain tip
const tip = await fetch('/api/qinote/settlement/reserve-attestation').then(r => r.json());
console.log('Current tip hash:', tip.audit_chain_tip);

// 2. Pull the last 100 settlement entries
const ledger = await fetch('/api/qinote/settlement/ledger?limit=100').then(r => r.json());

// 3. Walk backwards — each row's prev_hash must equal the row before's this_hash
let ok = true;
for (let i = 0; i < ledger.entries.length - 1; i++) {
  if (ledger.entries[i].prev_hash !== ledger.entries[i + 1].this_hash) {
    ok = false; console.error('MISMATCH at index', i, ledger.entries[i]); break;
  }
}
console.log(ok ? '✅ Chain is intact' : '⚠ Chain has been tampered — sound the alarm');

For the full universal audit chain (covering tCL-Rights, votes, role changes — not just settlement), use the deeper endpoints:

// Full chain integrity over the most recent N entries
fetch('/api/audit-chain/verify-chain?limit=500').then(r => r.json()).then(console.log);

// Per-record inclusion proof — proves a specific event is in the chain
fetch('/api/tcl-audit/public/inclusion-proof/<entry_id>').then(r => r.json()).then(console.log);

Walk-Through: A Real Settlement, Verified

Glossary Cheat Sheet