Skip to content

Preview · not officially published. Technical information only; the planned DLT is not live.

ByteShares.org

Builders

Technical Papers

Awaiting approval

A register of the papers this platform intends to publish. No document is downloadable. Where a web summary of the material already exists on this site, it is linked; where it does not, the entry says so plainly rather than offering a link that leads nowhere.

Not live

The paper library is not operating. Nothing on this page reports real activity, and no operational figures are shown, because no verified operational data source exists yet.

Titles below describe intended documents. A title is not evidence that a finished paper exists.

Source / verification
Register owner-asserted; no document inspected
Document version
No paper has a version assigned
Last reviewed
19 September 2026

Paper register

  • VPLedger historical whitepaper

    Awaiting approval
    Purpose
    Record where the ledger model came from and how it changed.
    Scope
    Historical provenance and evolution of the VPLedger model.
    Source / verification
    Source provenance audit ongoing
    Document
    Document pending; web summary available

    Web summary: VPLedger

  • ByteShares technical whitepaper

    Planned
    Purpose
    State the canonical architecture in one citable document.
    Scope
    System flow, architecture principles, layers and modules.
    Source / verification
    Document not supplied
    Document
    Document pending; web summary available

    Web summary: Protocol Architecture

  • Sig-56 specification

    Planned
    Purpose
    Make authorized actions verifiable by third parties.
    Scope
    Signature and signalling model for identity, authority and intent.
    Source / verification
    Specification not supplied
    Document
    Document pending; conceptual summary only

    Web summary: Standards

  • F.I.P. specification

    Planned
    Purpose
    Define accountable identity for AI agents.
    Scope
    AI identity, curation, memory, behaviour and authority boundaries.
    Source / verification
    Concept only; specification not supplied
    Document
    Document pending; conceptual summary only

    Web summary: Standards

  • Governance architecture

    Planned
    Purpose
    Describe how authority is granted, exercised and closed out.
    Scope
    Authority domains, lifecycle, exceptions, reversals and disputes.
    Source / verification
    Document not supplied
    Document
    Document pending; web summary available

    Web summary: Governance Layer

  • Storage and data sovereignty

    Planned
    Purpose
    Separate what is committed publicly from what stays in custody.
    Scope
    Anchors, off-chain evidence, custody, retention and storage rails.
    Source / verification
    Document not supplied
    Document
    Document pending; web summary available

    Web summary: VPLedger

  • Security and threat model

    Planned
    Purpose
    State what the design defends against and what it does not.
    Scope
    Trust boundaries, threats, mitigations, invariants and residual risk.
    Source / verification
    Threat model not completed
    Document
    Document pending; web summary available

    Web summary: Security

  • Protocol invariants

    Planned
    Purpose
    Fix the constraints an implementation may never break.
    Scope
    Deterministic execution, authority, accounting and auditability.
    Source / verification
    Document not supplied
    Document
    Document pending; web summary available

    Web summary: Protocol Architecture

  • Node operations specification

    Planned
    Purpose
    Define what running a node obliges an operator to do.
    Scope
    Roles, lifecycle, retention obligations and operational evidence.
    Source / verification
    Document not supplied
    Document
    Document pending; web summary available

    Web summary: Node Architecture

Release conditions

  1. The document exists in a reviewable, complete draft.
  2. Every factual claim in it maps to a verified source.
  3. The owner approves publication in writing.
  4. A version and date are fixed so readers can cite it.

Evidence register

Each statement on this page is tracked against a source. A claim without a verified source is never presented as fact.

Claims on this page and the verification state of their sources
ClaimSource typeVerificationNote
Planned paper titles, purposes and scopesOwner-provided registerSource claimed, not yet verifiedReserved for the preview; no draft document has been supplied or inspected.
Any published, citable paper or downloadReleased documentNo source on fileNothing released; nothing linked.