News · Release · November 16, 2026
White paper 3.0: every claim marked live, built or planned
Ghostdrive paper 3.0 marks each mechanism live, built or planned and lists its limits. Read it, check it against the network, tell us what is wrong.
DRIVE 369 DAO · 4 min read
White paper 3.0 is on the site and as a 21-page PDF. It is a rewrite, not an addendum: 17 sections, formulas, measurements and a status table. Every mechanism carries one of three marks, and every section ends with what the mechanism does not give you.
We are asking you to check it. If a mark is wrong, tell us.
Three marks
| Mark | What it means | In Table 10 |
|---|---|---|
| live | Deployed and in use | 28 mechanisms |
| built | In the main branch with tests; no deployment shown | 14 |
| planned | Design only | 4 |
The counts are from Table 10, which lists 46 mechanisms. The marks describe the state on 15 November 2026; two rows were corrected on 16 November and are named below.
What is in the paper
- Keys and identity. Keys are created on the device and never leave it. The operator cannot recover a vault.
- Storage. Files are sealed into blocks of at most 256 KiB and padded, so a storage node sees a size class and nothing else. Storage deals and proofs run on a testnet only.
- Sharing, mail and calls. Groups, sealed messages with a post-quantum envelope, mail on a customer's own domain, calls of up to 12 people with every frame sealed.
- Who can learn what. One table names each party that touches the system and what it can and cannot learn, relays and the project itself included.
- The ledger. A permissioned chain with five validators and a block every 2 seconds. It holds fingerprints only. You can read it at explorer.ghostdrive.com.
- Verifiable records. Proof of Origin, document signing and AI-use logs: what each proves, and what it does not.
- AI and agents. Local models, signed receipts from network AI, approval cards and four hard stops that no rule removes.
What changed since 2.3
- The ledger of record is the project's own permissioned chain and no longer a public one. Public checkpoints to Base are paused, and the paper says so.
- Verifiable records are specified as mechanisms with their exact claims.
- Token economics is removed. Supply, allocation and emission are outside the scope of this paper.
What the paper admits
The limits are written with the same weight as the mechanisms. Some of them:
- All five validators are run by the project's own team, so the ledger is not independent of the project today.
- No external audit of the contracts, the ledger or the applications has been done. None is claimed.
- An AI operator on the network reads the prompts it is sent in clear text.
- A relay sees addresses, sizes and timing.
- A read capability that was handed out cannot be withdrawn.
- Desktop builds are not signed by a developer certificate and there is no auto-updater.
Two rows corrected on 16 November
Sign. The paper said document signing was not yet released. It is released in the app, and on 16 November it ran end to end on the production relay and ledger for the first time, as our own test: one envelope, a member and a guest signer, six signed steps sealed in one ledger transaction in block 129960, and a checker that accepted the signed PDF and refused seven altered copies. The row stays built: no customer has used it, and delivery of the document to a signer over the storage network was not part of the run.
Paid storage plans. The paper said paid plans on a public main network were planned. The storage broker has offered them in USDC on Base since 15 November. No purchase has settled yet, so the row is built.
Find an error
Three ways to check a claim without trusting us:
- Open the explorer and use "Verify a record" on a block or a transaction.
- Read the open-source core at github.com/NeyraLabs/ghostdrive: the protocol, the node and the contracts.
- Compare a mark in Table 10 with what the app and the network do.
If something does not match, write to hello@ghostdrive.com with the subject "Paper 3.0", the section number and what you checked. We publish corrections with their date, as we did above.
Questions
- What do live, built and planned mean?
- Live means deployed and in use. Built means the code is in the main branch with tests and no deployment is shown. Planned means design only. Table 10 of the paper gives the state of 46 mechanisms.
- What changed since version 2.3?
- The ledger of record is now the project's own permissioned chain, not a public one. Verifiable records are specified with their exact claims. Token economics is removed from the paper.
- How do I report an error in the paper?
- Write to hello@ghostdrive.com with the subject "Paper 3.0", the section number and what you checked. Corrections are published with their date.