Platform
Frequently Asked Questions
Short answers grounded in the current public documentation. Planned architecture remains planned, and unknowns remain explicit.
- Source / verification
- Existing public ByteShares.org documentation and evidence boundaries
- Document version
- 0.9 RC1
- Last reviewed
- 7 October 2026
Questions and answers
01Is ByteShares.org a live blockchain or DLT network?
No. ByteShares.org is a public technical-information and documentation site. No ByteShares DLT, node, explorer data source, wallet, token, payment rail, API or SDK is presented as operational.
02Where do membership, cooperative governance, login and payments belong?
They belong to ByteShares.dk, the separate cooperative site. ByteShares.org has no member accounts, payment feature or member-data function.
03What do the maturity labels mean?
They describe documentation or development maturity. Documented means a written model exists; Planned means future intent; Awaiting approval means reviewable but not accepted. A label never proves operation or verification.
04Has Proposed Canon & Protocol Invariants v0.1 been adopted?
No. It is a normative-design candidate dated 8 October 2026, marked Proposed / Awaiting owner acceptance and Proposed / Non-operational.
05What does Covered mean in the Coverage Registry?
Covered means the stated conceptual documentation scope is substantively represented. It does not mean verified, implemented, secure, legally accepted, published as a specification or operational.
06What is known about historical VPLedger work?
Owner-reported inspection and recorded archive provenance support historical documented designs, development effort and concept lineage. They do not independently verify current code, operation, benchmarks, security, token issuance or complete legal title.
07What are eIDspot, VPLedger and AI City?
eIDspot is the proposed identity/access layer; identity does not itself grant authority. VPLedger is the documented proof, evidence and audit model; AI City is a planned family of modular applications. None is presented as an operating deployment.
08Is PreDAO → Memo → Epoch an operating DAO process?
No. It is a proposed conceptual lifecycle for defining scope, recording an authorized memo and closing a bounded epoch with required evidence. Exact authority, timing, closure and exception rules remain unresolved.
09Are the technical papers published specifications?
No. They are claim-traced documentation review manuscripts marked Draft / Awaiting approval. No individual author, paper version, publication date, DOI, download or endorsement is assigned.
10Why are some private sources summarized but not linked?
Only limited, owner-cleared architectural concepts and source metadata are used. Private institutional text, financial material, personal data and confidential legal or commercial records are not included in public assets.
Need the evidence behind an answer?
Review the Coverage Registry, the claim-traced manuscripts or the Glossary. The documentation Q&A can answer from a curated excerpt set, but it does not replace source review.