ByteShares.org — Technical information & documentation

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.

Nothing shown here should be read as a running system. There are no endpoints, repositories, 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.
• 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 architectureAggregated gate chain, acceptance matrix, runbook and launch checklist.
• Release ControlDocumented architectureSeparate preview, indexing, GitHub, domain and owner-approval gates.
• 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.

The working target for documentation readiness is 29 September 2026. This is not a blockchain launch date. Unverified claims keep their maturity labels; official publication requires the intended custom domain and Ronny's explicit release approval.