News · Testnet · November 13, 2026

369 Ledger: our private chain is live, and you can watch it

A private Besu chain with five validators, a block every 2 seconds, zero gas. What it records, who runs it, and what it does not prove.

DRIVE 369 DAO · 5 min read

369 Ledger is a private blockchain that Ghostdrive now runs next to its public testnet records: five validators, a block every 2 seconds, zero gas and no native coin. It holds fingerprints and one test credits service for a pilot, never files or messages, and anyone can watch it at explorer.ghostdrive.com. It is a pilot, run by us, and this page says what it proves and what it does not. Figures below were read from the explorer on November 13 and 14, 2026.

Update, November 14: the network now has five validators, not four, and needs 4 of 5 signatures to commit a block. All five are still run by the 369 team. We also corrected our first version, which said the chain had no token and only two kinds of record: it also hosts a test service-credits contract for the IndoDrive pilot. The table below shows the November 14 reading.

What it is

It runs on Hyperledger Besu, an open-source Ethereum client, with the QBFT consensus protocol: validators take turns proposing a block, and a block is final once enough of them sign it. The explorer shows the live state:

The explorer itself is read-only. It follows the chain block by block and never sends a transaction.

What goes on it

Only fingerprints, apart from one test service described below. Two kinds of fingerprint record exist today:

• Origin anchors. The Proof of Origin log, where people register the fingerprint of a file with their Ghost ID, writes its checkpoint to the ledger. Nobody needs gas or an account: you sign a claim, the relay anchors the log. How Proof of Origin works.
• Vault seals. The signed, hash-chained log of what an AI was allowed to use is folded into one fingerprint and written to the chain, only when your own node has been set up with a ledger account. The log stays in your vault; the chain holds only the fingerprint, so a log rewritten later no longer matches it.

The one other thing on the chain is a test service-credits contract for the IndoDrive pilot. Its credits are an accounting unit for the pilot, not a currency, and most of the explorer's transactions are that pilot, run from test accounts of the 369 team. It is not the traffic of outside users.

No file, message or log entry ever goes on the chain. Privacy still comes from the encryption on your device. A record on the ledger can show that it matches what was written, not what it says, and only the Base checkpoints make a later rewrite visible.

Who can read it and who can write

• Read: anyone. The explorer shows blocks and records, with a "verify a record" check that asks the chain live whether a record is on it and whether a quorum signed its block. A read-only window serves block and transaction reads, limited per visitor. The relay's own window also caps reads per address range and for everyone. Sending and admin calls never reach the node.
• Write: only accounts admitted by name. The relay holds one admitted key. A person's node can also be admitted, with a key derived from its identity, so it is never stored.

Checked against a public chain

Every 10 minutes a separate checkpoint service, with a key held by the 369 team, writes a checkpoint of the network to Base Sepolia, the public testnet. The block's hash sits in the Base transaction, so a later rewrite of earlier blocks shows when anyone compares the two chains. On November 14 the explorer showed 130 checkpoints, the last covering block 44,561.

What it does not prove

• It is not decentralised. All five validators are ours. If we all agreed to rewrite history, the validators could. The Base checkpoints are what makes that visible, not impossible.
• The checkpoint key is ours too, and its address is published on the explorer so anyone can watch it.
• Checkpoints cover history up to their block. Blocks after the last one are not covered, and a rewrite made before the first checkpoint was written would not have shown.
• A record on the chain is not a truth. A Proof of Origin entry shows that a Ghost ID signed a fingerprint no later than the moment the log accepted it. It does not show authorship, ownership or copyright.
• It is a day old and a testnet-stage pilot. The explorer's own uptime figure covers one day. Its fingerprint records are plain data in transactions to an inert address, not contract calls (only the pilot's credits use a contract), and it has had no external audit. The contracts on Base Sepolia keep their audit pending, and mainnet is planned for 6 March 2027 after an external audit (status).

Why a private chain at all

Some organisations want a record kept by validators they know and can name, with no fees and no native coin, and checked on their own node. For them there is 369 Ledger today as a pilot, and a ledger of an organisation's own, under its own validators, is planned. The open network still anchors on Base, which anyone can check. You pick which chain your app checks in Settings › Proof network, and the wallet, DRIVE and the DAO stay on Base either way.

Open the explorer · What goes on a chain, and what never does · Security and audits