Skip to content

Live technical information site. The planned DLT is not live; membership is on ByteShares.dk.

ByteShares.org

Operations

Source & Repository Readiness

Awaiting approval

A specification for how source will be taken in, classified, versioned and published — written before any candidate repository is accepted, so the process can be audited rather than reconstructed afterwards. GitHub is Awaiting approval / Not connected for this project; no official ByteShares repository was verified through the connected account, and no repository has been created or imported, and no repository name here is final.

Not live

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

Awaiting GitHub connection. No repository URL, name or link is published. Anything elsewhere presenting itself as an official ByteShares repository is unverified as far as this platform is concerned.

Source / verification
Owner instruction plus supplied inventory, integrity and ownership-schedule evidence; repository acceptance pending
Document version
0.9 RC1
Last reviewed
7 October 2026

Documentation release candidate — October 2026

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.

Documented provenance and concept lineage

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.

Evidence currently available

Safe metadata only. These records support readiness work; they do not establish complete legal title, repository acceptance or production readiness.

Inventory report
VPLedger_E_Drive_Recovery_Report_2026-09-17.xlsx — historical evidence dated 17 September 2026
Integrity coverage
52,014 files / 54.27 GiB SHA-256 hashed without missing entries; USB OpenLedger manifest contains 10,024 file records
Ownership declaration
Boesing_Corporation_IP_Ownership_Schedule_2026.docx records the owner's VPLedger ownership declaration and sole complete-code custody statement
Historical support
Historical documents and the four October archive records support founder/originator chronology and conceptual lineage; OpenLedger project-rights and contractor records remain subject to title review
Legal-title limitation
Historical title documentation is incomplete; possession alone does not establish ownership of every component, and contractor-assignment and bankruptcy-transfer evidence is incomplete
Sensitive-material status
Restricted wallet, key and credential-related categories are indexed for safe handling; quarantine and repository-level scanning remain pending

Inventory, integrity and acceptance boundaries

The five root names and file counts below are bounded to the historical recovery report dated 17 September 2026. The estate-level 52,014-file / 54.27 GiB hash record and 10,024-record USB manifest are recorded integrity evidence, not a current repository scan or a claim that those records are the same accepted baseline. No new archive inspection occurred in this documentation pass.

  • Inventory shows recorded roots; proposed targets do not establish canonical scope or import acceptance.
  • Hashes support content identity within their recorded scope; they do not prove authorship, legal title, licensing, safety or runnability.
  • Class C remains the disposition for candidates. Moving to A/B needs repository-level history, source identity, title/licence and reviewer evidence; the legend is not acceptance.
  • Class X and metadata-only handling define exclusion rules, not evidence that quarantine or scans have run. Per-root exclusion/scan records and reviewer sign-off are still required.

The four October archive records support founder/originator chronology and concept lineage. Component-linked assignments, collaboration agreements and applicable transfer records are still needed for title review; no historical software ownership or licence is inferred.

What readiness does and does not mean

Readiness is not connection

Awaiting approval

GitHub readiness means the process is defined. It does not mean GitHub is connected.

Connection is not acceptance

Awaiting approval

A connected account does not mean any repository or its source has been accepted.

Acceptance is not operation

Awaiting approval

Accepted repositories do not mean infrastructure exists or runs.

Public documentation is separate

Documented architecture

ByteShares.org is already publicly available at https://byteshares.org. Source acceptance and future operational releases remain gated; they do not disable the existing documentation domain or indexing.

GitHub readiness gate

Twelve gates, each stated with the evidence its current state rests on. States are deliberately conservative: anything unproven is not started or blocked.

  • G1

    Inventory complete

    In progress

    Every candidate source set is mapped and named.

    Basis: The five core VPLedger roots and broader OpenLedger roots are inventoried; full canonical intake scope is not approved.

  • G2

    Integrity captured

    In progress

    Manifests and hashes recorded where practical.

    Basis: Estate-level evidence records 52,014 SHA-256 hashes without missing entries and a 10,024-record USB OpenLedger manifest; accepted repository baselines are not yet linked.

  • G3

    Provenance classified

    In progress

    Class A/B/C/D/X assigned with evidence.

    Basis: Core candidate roots remain class C while commit history, legal title, licensing and canonical intake are reviewed; nothing is class A or B.

  • G4

    Sensitive material separated

    In progress

    No secrets, private keys or wallet dumps destined for Git.

    Basis: Restricted wallet, key and credential-related categories are identified for index-only handling; quarantine and repository-level secrets scans remain pending.

  • G5

    IP and licensing reviewed

    Blocked

    Ownership and licence gaps explicitly recorded.

    Basis: The IP Provenance Dossier, IP Concept Evolution Register, Chain-of-Title Matrix and 2026 IP Foundation Clean Title Record support founder/originator chronology and concept lineage. Historical contractor/collaboration assignments, transfers, complete legal title and licensing remain incomplete.

  • G6

    Canonical repo mapping approved

    Not started

    Each accepted source set has an approved target.

    Basis: Mapping is proposed only; no approval recorded.

  • G7

    Build baseline documented

    Not started

    Build, dependency and test state recorded per source set.

    Basis: No candidate DLT source build baseline has been verified; this does not refer to the documentation site build.

  • G8

    Version baseline assigned

    Blocked

    Versions assigned after source verification.

    Basis: Blocked by G3; no version may be assigned before provenance.

  • G9

    Documentation baseline present

    Ready for review

    Readme, security, contribution and provenance expectations defined.

    Basis: Documentation RC1 expectations are specified and await owner review.

  • G10

    GitHub connection approved

    Not started

    Explicit owner approval to connect GitHub.

    Basis: Awaiting approval / Not connected. No official ByteShares repository verified through the connected account.

  • G11

    Repository import verified

    Not started

    Imported contents match the accepted source sets.

    Basis: Nothing connected, so nothing imported.

  • G12

    Future source and operational release acceptance

    Blocked

    Accepted source or operational claims require evidence and explicit approval; this does not gate the already-public documentation site.

    Basis: Future source/operational scope depends on G1 through G11, independent operational evidence and owner approval. Existing public domain and indexing are already recorded.

Proposed repository architecture

Proposed repository architecture — awaiting source and provenance acceptance.

Separation follows responsibility and provenance rather than a monorepo assumption, so a source set with unclear origin cannot contaminate verified material. Names are working labels, not final, and no URL is implied by any of them.

protocol-core

Canonical DLT and protocol implementation; where verified protocol source ultimately belongs.

Proposed; no source accepted

vpledger-core

VPLedger core and ledger implementation.

Proposed; candidate source pending classification

vpledger-client

Client and frontend application.

Proposed; candidate source pending classification

vpledger-backend

Backend and supporting services.

Proposed; candidate source pending classification

vpledger-tests

Regression, smoke and integration test assets.

Proposed; candidate source pending classification

network-testnets

Testnet and node configuration and infrastructure assets.

Proposed; candidate source pending classification

specifications

Protocol architecture, invariants, Sig-56, F.I.P., Web4 and governance technical specifications.

Proposed; documents not supplied

developer-docs

API, SDK and developer documentation and examples.

Proposed; content drafted only on this platform

sdk

Client libraries, if a distinct codebase exists.

Proposed; awaiting source verification

explorer

Explorer application, if a distinct codebase exists.

Proposed; awaiting source verification

security

Threat model, security policy and responsible disclosure. Never secrets.

Proposed; threat model incomplete

archive / legacy mapping

Index mapping legacy OpenLedger and VPLedger assets to eventual canonical destinations. Documentation, not necessarily a repository.

Proposed; index not compiled

Provenance classes

Provenance classification legend
ClassMeaningConsequence
A — Verified canonicalBytes, history and provenance verified sufficiently for canonical intake.Eligible for a canonical repository.
B — Verified with gapsSource appears authentic and usable, but legal or history gaps remain.Intake only with gaps recorded and owner acceptance.
C — CandidateTechnically relevant; identity, version or provenance not established.Hold. No publication.
D — Archive / referenceHistorical or supporting material, not suitable as active source.Index only; never a build input.
X — Excluded sensitiveSecrets, private keys, credentials, wallet dumps, personal or confidential material.Quarantined. Never enters Git; represented only by safe metadata.

No material is currently classified A or B. Assigning a class requires evidence, not familiarity.

Repository intake and provenance checklist

Every candidate source set is recorded against the same fields before any disposition is reached. Secret contents are never recorded — a sensitive file is represented by safe metadata only, and its contents are quarantined.

Intake fields21 fields
  1. Source origin — physical or logical location
  2. Original relative path
  3. Repository history present (.git) — yes or no
  4. Commit history available and readable
  5. Remote or origin evidence, where present
  6. Author and committer history
  7. Earliest and latest verifiable commit
  8. Licence file and licensing basis
  9. Copyright notices
  10. Contributor and developer identity evidence
  11. Corporate or project ownership evidence
  12. Contractor or IP-assignment evidence, where applicable
  13. Submodules and external dependencies
  14. Build and package manifests
  15. Secrets and credentials scan status
  16. Generated, vendor or binary classification
  17. SHA-256 or source snapshot reference, where available
  18. Comparison status against duplicate or archive copies
  19. Chain-of-title status
  20. Reviewer, date and evidence reference
  21. Acceptance disposition — Accepted / Accepted with gaps / Hold / Rejected / Archive only
Current field state for the five candidate rootsSafe metadata only
Intake fields and what is currently established for the candidate source sets
Intake fieldCurrent state for vpledger, vpledger_client_app, vpledger-backend, vpledger-tests and testnets
Source originRecorded in the recovery inventory as preserved estate roots
Original relative pathRecorded in the recovery inventory; not restated here
.git present and commit historyNot established — requires repository-level intake
Remote or origin evidenceNot established
Authors and committersNot established
Earliest and latest verifiable commitNot established
Licence file and copyright noticesNot established; no licence decided
Contributor and IP evidenceOwner declaration, four archive IP records and historical support; founder/chronology and concept lineage supported, contractor/collaboration assignments incomplete
Submodules and dependenciesNot established
Build and package manifestsNot established
Secrets scan statusRestricted categories identified; repository-level scan not performed
Binary, vendor and generated classificationNot established
SHA-256 referenceEstate-level hash evidence exists; per-root baseline linkage not established
Duplicate and archive comparisonNot established
Chain of titleIncomplete — historical title documentation missing in part
Reviewer and evidence referenceNot recorded
Acceptance dispositionHold pending intake — no set has reached a disposition

"Not established" means no evidence has been produced, not that evidence is absent from the estate. Nothing has been accessed, scanned or built for this platform.

Source inventory
Core roots inventoried and preserved; canonical scope and repository intake pending
Integrity evidence
Preserved estate hashes and manifests exist; canonical per-repository baseline linkage pending
Sensitive handling
Restricted categories identified; publication quarantine and repository-level secrets scans pending
Dispositions reached
None

Legacy candidate source mapping

Candidate source sets inventoried and preserved in the recovery report, presented pending canonical repository intake and provenance acceptance — not as imported repositories.

Candidate source sets mapped to proposed targets with class, gaps and disposition
Candidate source setInventory evidenceProposed targetClassVerification gapsDisposition
vpledger499 filesvpledger-coreC — CandidateCommit history, licence and legal title intake pendingHold pending intake
vpledger_client_app164 filesvpledger-clientC — CandidateCommit history, dependencies and repository-level secrets scan pendingHold pending intake
vpledger-backend60 filesvpledger-backendC — CandidateCommit history, sensitive-content quarantine and build state pendingHold pending intake
vpledger-tests112 filesvpledger-testsC — CandidateCommit history, test runnability and coverage pendingHold pending intake
testnets125 filesnetwork-testnetsC — CandidateCommit history, configuration quarantine and repository-level secrets scan pendingHold pending intake
Other legacy OpenLedger roots, including libevm and ol4Inventoried; count not stated herearchive / legacy mappingC — Pending classificationCanonical scope, relevance, licensing and legal title pendingArchive-only unless accepted by evidence

Source intake sequence

The order in which the five evidenced candidate roots will be worked, once repository-level intake is authorised. Nothing in this sequence has been started: no source has been accessed, scanned, built or classified beyond the existing inventory evidence.

Evidenced candidate roots entering the sequence
Candidate rootInventory evidenceProposed target
vpledger499 filesvpledger-core
vpledger_client_app164 filesvpledger-client
vpledger-backend60 filesvpledger-backend
vpledger-tests112 filesvpledger-tests
testnets125 filesnetwork-testnets
  1. 01

    Quarantine sensitive material

    Restricted wallet, key, credential and personal categories are separated as class X before anything else is touched. Contents are never transcribed; only safe metadata is recorded.

  2. 02

    Repository-local secrets scan

    Each candidate root is scanned in place for credentials and key material. Findings are quarantined, not fixed in passing.

  3. 03

    History capture

    Presence of .git, readable commit history, remote or origin evidence, author and committer records, and earliest and latest verifiable commit.

  4. 04

    Dependency and licence inventory

    Package manifests, lockfiles, submodules, vendored and generated material, third-party licences and copyright notices.

  5. 05

    Build and test baseline

    Whether the set builds, what it needs, and whether tests pass, fail, are not runnable or were not verified. Failures are recorded, not hidden.

  6. 06

    SHA-256 baseline linkage

    The candidate root is linked to the preserved estate hash evidence so the accepted bytes are identifiable later.

  7. 07

    Provenance classification

    A, B, C, D or X assigned against recorded evidence. Candidates stay class C until evidence justifies otherwise.

  8. 08

    Proposed canonical target

    The classified set is mapped to a proposed repository, with the mapping itself still requiring owner approval.

  9. 09

    Acceptance review

    A repository acceptance record is completed and reviewed. Acceptance means honestly described and safe to publish — never production-ready.

Sensitive material is handled first and never leaves quarantine. A step is only recorded as done when its evidence exists.

Reusable source-intake record

One record per source set, completed during authorised intake. Sensitive content is recorded as metadata only or excluded as class X — never credentials, keys, wallet dumps or secrets. No record has been completed.

Source-intake record fields19 fields · template
Source-intake record fields and completion guidance
FieldGuidanceValue
Source setRoot name as inventoried, e.g. vpledger.Not yet recorded
OriginWhere the preserved copy came from; no personal data.Not yet recorded
Relative pathPath within the preserved estate.Not yet recorded
.git / history statePresent, partial or absent.Not yet recorded
Commit evidenceEarliest and latest verifiable commit reference.Not yet recorded
Remote / origin evidenceRecorded remote, stated as metadata; never published as a link.Not yet recorded
ContributorsCount and role categories; names only if already on the legal record.Not yet recorded
Licence / copyrightAs found in the source. Never fabricated.Not yet recorded
IP / assignment evidenceReference to assignment documents, or stated as missing.Not yet recorded
Dependencies / submodulesManifest reference and third-party licence summary.Not yet recorded
Build manifestsLockfiles and build files present.Not yet recorded
Secrets-scan stateNot run / run with findings / clean. Findings as category only.Not yet recorded
Binary / vendor classificationOwn code, vendored, generated or binary.Not yet recorded
SHA-256 evidenceReference to estate hash record; per-repository linkage.Not yet recorded
Duplicate / archive comparisonRelationship to other copies; candidate for class D.Not yet recorded
Chain-of-title stateComplete, gaps documented, or unresolved.Not yet recorded
Reviewer / evidence dateReviewer role and date of review.Not yet recorded
Target repositoryProposed canonical target; never an existing URL.Not yet recorded
DispositionA / B / C / D / X class and acceptance disposition.Not yet recorded

Repository acceptance record template

The record feeds the gates: intake fields close G1–G5, target and version baseline close G6–G8, and a completed, owner-approved record is the evidence for G11. Acceptance is not production readiness — operation still needs implementation and operational verification.

One record per candidate source set, held in this preview only. Values shown are the current honest state — the template is not pre-filled with assumptions, and no set has reached a disposition.

Acceptance record fields14 fields
Repository acceptance record fields and their current state
FieldCurrent state
Candidate source setNot yet recorded — one record per accepted set
Accepted scopeNot yet recorded
Provenance classC — Candidate (no set has been reclassified)
Source and hash referencesPreserved estate hash evidence exists; per-repository linkage not yet recorded
Commit baselineNot yet recorded
Build and test stateNot yet recorded
Licence and IP statusLicence undecided; chain of title incomplete
Excluded sensitive pathsSafe metadata only — category and handling decision, never contents or locations that reveal secrets
Target repositoryProposed only; mapping not approved
Version baselineNot yet assigned
ReviewerNot yet recorded
Owner approvalNot recorded
Acceptance dispositionAccepted / Accepted with gaps / Hold / Rejected / Archive only — none reached
DateNot yet recorded

Excluded sensitive paths are represented by safe metadata only — category and handling decision. Contents, credentials, keys and wallet data are never recorded here.

Versioning policy

Software componentsProposed
  • Semantic versioning — MAJOR.MINOR.PATCH — for releasable software components.
  • Pre-production components stay on 0.x until acceptance criteria justify 1.0.
  • Git tags annotated, and signed where operationally feasible.
  • No historical release number is invented. No accepted DLT software version is assigned; 0.9 RC1 is the documentation candidate version only.
Specifications and documentsProposed

Specifications carry an explicit specification version and a status of Draft, Review or Approved. They never borrow software release numbers to look more finished than they are.

What a release bindsProposed
  • Commit and tag
  • Changelog entry
  • Maturity status
  • Source and provenance state
  • Compatibility notes
  • Relevant specification version
Compatibility matrixValues unassigned
Compatibility matrix structure with unassigned values
ComponentVersioning basisVersionStatusCompatible spec version
protocol-coreSemVer, prospective onlyNot yet assignedNot yet assignedNot yet assigned
VPLedgerSemVer, prospective onlyNot yet assignedNot yet assignedNot yet assigned
API / SDKSemVer, prospective onlyNot yet assignedNot yet assignedNot yet assigned
ExplorerSemVer, prospective onlyNot yet assignedNot yet assignedNot yet assigned
SpecificationsSpecification version plus Draft / Review / Approved statusNot yet assignedNot yet assignedNot applicable

Architecture pages on this platform expose version, maturity, source and verification, and last reviewed, using "not yet assigned" wherever a value is unknown.

Branch and change control readiness

Proposed governance. These are not currently active GitHub settings, because there is no GitHub connection to configure.

  • Protected main branch.
  • Feature and fix branches with a pull-request workflow.
  • Review required before merge.
  • Required build and test checks once continuous integration exists.
  • No secret is ever committed; scanning precedes merge.
  • CODEOWNERS or equivalent ownership review where appropriate.
  • Release tags cut only from an accepted main state.
  • Changelog and release notes for every release.
  • Security-sensitive changes require explicit named review.

Repository minimum files

Expected minimum files per future repository
File or artefactExpectation
README.mdWhat the repository is, what it is not, and its maturity — matching the labels used here.
LICENSEA licence, or an explicit "Awaiting approval / verification" status. No placeholder licence is ever added.
SECURITY.mdResponsible disclosure route and response expectation.
CONTRIBUTING.mdContribution terms, review expectations and attribution.
CHANGELOG.mdRequired for releasable components.
CODEOWNERSWhere ownership review applies.
Architecture and docs linkPointer to the corresponding ByteShares.org documentation.
Build and test instructionsHow to build and test, including known failures.
Dependency manifest and lockfileReproducible dependency state.
.gitignoreExcludes build output and anything sensitive.
Environment exampleVariable names only. No secret values, ever.
Provenance noteSource set, class and evidence reference.
Maturity noteCurrent maturity, consistent with this platform.

Proposed repository-to-documentation link review

Proposed / Non-operational — review record structure only; no repository URL is assigned or activated.

Proposed documentation mapping and validation boundaries
Record elementReview requirementCurrent boundary
Source identityRecord source-set reference, accepted scope, class, branch/commit and reviewer evidence.The five roots remain class C and on hold; no accepted branch/commit exists here.
Documentation intentMap each accepted responsibility to its existing architecture/developer page and compare maturity labels.Candidate targets are listed above; a conceptual page must not imply the mapped implementation is live.
Link and reverse referenceOnce authorized source exists, check the repository pointer to the intended ByteShares.org page and any approved reverse link against the same source scope.No external repository URL, published link or validation result is invented.
Version and evidence boundaryKeep source/specification version, documentation review date, and implementation/operational evidence distinct.0.9 RC1 describes documentation only; owner approval and actual accepted-baseline checks remain pending.
Conceptual integration documentation

Repository acceptance criteria

A repository counts as accepted only when all of the following hold.

  1. Intended source scope is clear.
  2. Provenance classification is recorded.
  3. Sensitive content is excluded.
  4. Ownership and licensing status is explicit.
  5. Canonical branch and source baseline are identified.
  6. Build and dependency state is documented.
  7. Tests are classified as passing, failing, not runnable or not verified.
  8. The readme accurately describes current maturity.
  9. No production-readiness claim is made without evidence.
  10. Version and tag policy is applied prospectively.
  11. A mapping exists from the repository to its ByteShares.org documentation.
  12. Owner approval is recorded where required.

Acceptance does not mean production-ready. It means the repository is honestly described and safe to publish.

Sensitive material handling

Credentials, private keys, wallet dumps and personal or confidential material are class X: quarantined, excluded from anything destined for Git, and never reproduced in documentation. Where their existence must be recorded, only safe metadata is kept — location reference, type and handling decision, never contents.

Open questions / evidence required

Proposed / Non-operational — review questions, not decisions or implementation contracts.

What is the first evidence request for title review?
TBD / Requires source: Component-linked assignments/agreements and applicable transfers for unresolved historical contractor/collaboration elements, followed by reviewed licence/title disposition; provenance alone is insufficient.
What authorizes new source inspection?
TBD / Requires source: Ronny's explicit bounded approval for repository-level intake of the five recorded roots; no access, scans, builds, imports or GitHub connection are performed here.
Documentation-gap audit and evidence boundaries

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
Repository architecture, intake checklist, gates and policiesOwner instructionVerified source on fileSpecified directly by the project owner in this preview; names and policies remain proposals.
Core VPLedger candidate roots are inventoried and preservedVPLedger_E_Drive_Recovery_Report_2026-09-17.xlsxVerified source on fileThe report records the five named core roots and file counts. Canonical repository intake and acceptance remain pending.
Preserved source and archive estate has integrity evidenceProject portfolio hash and manifest recordsVerified source on file52,014 files / 54.27 GiB were SHA-256 hashed without missing entries; the USB OpenLedger manifest contains 10,024 records. Repository-level accepted-baseline linkage remains pending.
VPLedger ownership and sole complete-code custodyOwner declaration in Boesing_Corporation_IP_Ownership_Schedule_2026.docxSource claimed, not yet verifiedOwner-declared evidence for readiness review; it is not independent proof of complete legal title.
Founder/origin and OpenLedger project-rights historyHistorical documentary support summarized in the IP ownership scheduleVerified source on fileSupports originator status and records project ownership, contractual SaaS rights and an external contractor; scope and legal effect require title review.
Complete legal chain of title for every historical componentChain-of-Title Matrix and 2026 IP Foundation Clean Title Record; assignments and transfers still incompleteSource claimed, not yet verifiedArchive provenance and concept lineage are documented, but historical contractor/collaboration gaps remain. Neither possession nor the record titles establish exclusive ownership of every historical software component.
Restricted and sensitive categories identifiedRecovery inventory restricted-category indexVerified source on fileSafe category metadata exists. Secret contents are not shown; quarantine and repository-level secrets scans remain incomplete.
Repository names, URLs, imports or connectionsGitHubNo source on fileAwaiting approval / Not connected for this project. No official ByteShares repository verified through the connected account; no repository created, imported or linked.