Skip to content

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

ByteShares.org

Layers

VPLedger

Documented architecture

VPLedger is the working name for the proof, evidence and audit ledger described in the architecture. This page records the model as written. There is no ledger instance, no genesis state, no balances and no transactions.

Not live

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

Source / verification
Owner canon; archive founder/chronology and concept lineage recorded, historical title and repository review incomplete
Document version
Ledger specification: not yet assigned
Last reviewed
7 October 2026

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.

Model as documented

The ledger is described as an append-only record of entries. An entry references the participant it concerns, the kind of contribution or transfer it represents, and the moment it was accepted. Entries are described as never edited: a correction is itself a new entry that refers back to the one it corrects.

Two kinds of record are distinguished in the drafts: value entries, which track transferable amounts, and participation entries, which track contribution that is recognised but not transferable. The separation is deliberate, so that recognition of work cannot be traded as if it were value.

Proof + Execution Layer

Deterministic rule execution

Documented architecture

The same declared inputs, authorized rule version and prior state are intended to produce the same outcome. Hidden application logic is outside the canonical model.

Verifiable histories

Documented architecture

Each accepted transition should retain its inputs, authority, rule reference, timestamp and link to prior state so the result can be reconstructed.

Controlled participation

Documented architecture

Eligibility and authority proofs gate who may submit, approve or receive a particular state transition.

High-integrity accounting

Documented architecture

Accounting state is append-only, reconciliable and attributable; correction occurs through a linked compensating entry rather than silent mutation.

These are documented invariants. No execution engine, proof verifier or production accounting system is running.

Proof objects

Contract lifecycle

Documented architecture

Creation → escrow → settlement. Each stage records the governing terms, authority, state change and evidence reference.

Governance decision

Documented architecture

Proposal → vote → authorization. The proof binds eligibility, threshold evaluation and authorized outcome.

Compliance & eligibility

Documented architecture

A scoped proof states that a condition was satisfied under a named rule without requiring unrelated source data to be exposed.

Institutional audit extract

Documented architecture

A bounded, reproducible extract links selected entries, rule versions and evidence references to an anchored snapshot for independent review.

Merkle snapshots

Documented architecture

A Merkle snapshot is the documented proof primitive for committing a defined record set at an epoch boundary. Its root can be anchored with the timestamp and rule context; an inclusion path then verifies a selected record without disclosing the full set.

Snapshot format, hashing profile, epoch policy and verifier are not yet implemented or fixed.

Anchors and durable evidence

Separation between on-chain anchors and off-chain durable evidence
Kept on-chainKept off-chainReason
Rule references and versionsFull rule text and rationaleThe commitment must be small; the material must stay readable.
Hashes and timestampsThe documents and records they commit toA commitment can support content matching without disclosing the artefact; it does not establish its truth or legal title.
Accounting state transitionsSupporting commercial and identity evidenceAccounting must be reconstructable without exposing source data.
Evidence referencesThe evidence itself, under custodyCustody and retention stay explicit and revocable.

Content-addressed storage is the documented direction for durable evidence, with a Filecoin rail recorded only as planned positioning. No storage rail is contracted or in use, and hash construction, reference format and retention obligations are to be specified.

Data sovereignty and commitment limits

Proposed / Non-operational — custody and disclosure responsibilities, not a storage contract.

Compact anchors and retained evidence have different responsibilities. A custodian retains the underlying material; a permitted disclosure or audit extract refers to that material without turning an anchor into permission to access it. Identity and commercial source evidence must not be published merely because a proof references it.

Matching a commitment or checking inclusion does not prove evidence truth, legal ownership, current authority or continued retrievability. Revoking access cannot erase a historical anchor. Data classification, retention obligations, reference construction and retrieval policy remain TBD / Requires source; no Filecoin or other storage rail is in use.

Lifecycle examples

Each example shows where a proof object would be produced. None can be executed today.

  1. A

    Contract: creation → escrow → settlement

    Terms and authority are bound at creation, the escrow condition is recorded, and settlement produces a proof referencing both earlier stages.

  2. B

    Governance authorization

    Proposal, eligibility and threshold evaluation resolve into an authority record that execution can reference.

  3. C

    Compliance or eligibility proof

    A scoped proof states that a named condition held, without disclosing the underlying documents.

  4. D

    Institutional audit extract

    A bounded set of entries, rule versions and evidence references is tied to an anchored snapshot for independent review.

Unresolved

Consensus mechanism
Not decided
Entry schema
Draft, not fixed
Finality rules
Not specified
Instance
None exists

Open questions / evidence required

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

What exactly does a snapshot commit to?
TBD / Requires source: Record selection/ordering, canonicalisation, hashing, inclusion format, epoch closure and trusted-root specification, with verifier vectors.
Who retains evidence and for how long?
TBD / Requires source: Data classification, custodian/retention and retrieval policy; no availability guarantee follows from a content commitment.
Which historical components can be accepted?
TBD / Requires source: Component-linked title/licence and source-intake dispositions; the four archive records support chronology and lineage, not complete software ownership.
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
Append-only entry model with value/participation splitMaster Business Plan v2.1 / aligned canonSource claimed, not yet verifiedOwner-provided masterplan extracts and recorded historical lineage support the documented concept; full-source fidelity, source acceptance, legal title and implementation remain unverified.
Proof objects and deterministic execution modelOwner-provided aligned technical canonSource claimed, not yet verifiedDocumented model only; schemas, hashing and snapshot formats are to be specified, not invented.
Any balance, supply or transaction figureLedger stateNo source on fileNo ledger exists; no figures are shown anywhere on this platform.