ByteShares.org — Technical information & documentation

These are claim categories, not a single readiness score. Availability of documentation does not demonstrate an operating protocol.

Verified available

The public ByteShares.org documentation site and its public indexing configuration. Cooperative membership belongs to the separate ByteShares.dk site.

Public-site controls

Documented historical

Owner-reported historical VPLedger text inspection and recorded concept lineage. Earlier proposals are not evidence of delivered functionality, current code or legal title.

Historical source comparison

Proposed / not adopted

Proposed Canon v0.1 and conceptual architecture models; review manuscripts remain Draft / Awaiting approval. No DLT operation is asserted.

Review proposed canon

Awaiting evidence

Independent specifications, source acceptance, implementation, consensus/finality and operating evidence remain unresolved. Documentation coverage is not verification.

Independent evidence blockers

Requires owner/legal/security approval

Canon acceptance, permitted disclosure, IP/licensing disposition and legal/security review are separate gates. No approval follows from this preview update.

Review acceptance gates

Documentation: 45 Covered / 8 Partial / 0 Missing. Source verification: 4 Verified / 25 Owner-asserted / 11 Unverified / 13 No source. These independent registry totals have not been upgraded.

Version

0.9 RC1

Last reviewed

7 October 2026

Status

Evidence and owner-approval gates in progress

Scope

Documentation only — not a DLT, software or network release. The public site remains available at https://byteshares.org; this correction is source/preview only.

This site explains the intended technical architecture in plain language and keeps deeper specifications and readiness records available for review. Maturity labels distinguish documented ideas from planned work; they do not mean an implementation exists.

The documentation site is public; the planned DLT described here must not be read as a running system. There are no DLT endpoints, accepted source repositories, software releases, audits, node counts, uptime figures or adoption numbers on this platform, and none will be added until a source is verified and the owner approves it.

The two are deliberately kept apart. Cooperative decisions and money movement belong to ByteShares.dk. Technical description belongs here.

These roles describe the intended system, not services available on this site.

eIDspot Documented architecture

Identity and scoped access: who may act and under what authority.

VPLedger Documented architecture

Proof, evidence and audit history. Source provenance review remains open; no ledger is operating.

ByteShares DLT Planned

The proposed digital infrastructure. No blockchain, nodes, wallets or tokens are live here.

AI City Planned

ByteShares' intended long-term end-product family: an extensible environment with expandable white-label modules for different organisations, sectors and markets. No deployment is claimed.

Boesing Consult is an independent customer-facing problem-to-solution platform, not AI City. The footer lists the four ecosystem destinations; a link does not mean that planned infrastructure is operating.

• Protocol ArchitectureDocumented architectureLayered description of the intended protocol stack.
• Documentation RoadmapDocumented architectureCurrent documentation, owner-decision and evidence gates without delivery promises.
• Frequently Asked QuestionsDocumented architectureEvidence-bounded answers about scope, maturity, lineage and approval status.
• Canon & InvariantsAwaiting approvalProposed Canon & Protocol Invariants v0.1 — draft awaiting owner acceptance.
• Identity Layer / eIDspotDocumented architectureIdentity and verifiable-credential concept, named eIDspot.
• VPLedgerDocumented architecturePlanned proof and audit ledger model; no operating ledger.
• Governance LayerDocumented architectureTechnical governance objects: proposals, roles, thresholds.
• Node ArchitectureDocumented architectureNode roles and topology as described on paper.
• DLT ExplorerPlannedA future explorer surface. No chain data exists to display.
• Developers / API / SDKPlannedIntended developer surface. No endpoints or packages published.
• Ask the documentationDocumented architectureAsk questions grounded in cited, owner-directed technical documentation.
• Standards / Sig-56, Web4 & F.I.P.Documented architectureConceptual positioning for Sig-56, Web4 and FAWN Identity Protocol.
• Technical PapersAwaiting approvalPaper register. Documents are listed only once sources verify.
• GlossaryDocumented architectureCanonical terminology used across the technical documentation.
• SecurityDocumented architectureSecurity model intentions and disclosure posture.
• Readiness & AcceptanceDocumented architectureDocumentation RC1 evidence gates, acceptance matrix and public-site records.
• Release ControlDocumented architecturePublic-site indexing and domain records, separate from source and operational approval.
• Coverage RegistryDocumented architectureInternal control tracking canon coverage and source verification.
• Network StatusPlannedNo network is running, so no status can be reported.
• GitHubAwaiting approvalSource-code publication awaiting owner approval.

Archive evidence recorded by the owner in the 7 October 2026 canon. A later owner-reported inspection of two historical VPLedger texts is summarized separately on Technical Papers; neither record establishes legal title, source acceptance or current implementation.

• Ronny_Boesing_IP_Provenance_Dossier_2026.docx
• Ronny_Boesing_IP_Concept_Evolution_Register_2026.docx
• Ronny_Boesing_Chain_of_Title_Matrix_2026.docx
• Ronny_Boesing_2026_IP_Foundation_Clean_Title_Record.docx

The archive records support founder/originator and chronology evidence for VPLedger and a coherent conceptual lineage into the 2026 modular trust architecture. Documented provenance and concept lineage are not proof of exclusive ownership of all historical software. Complete legal chain of title remains unresolved for some contractor and collaboration elements, including missing assignments, transfers or agreements. Repository acceptance and licensing remain separate and incomplete.