01
Identity
Establish the subject, credentials and eligible authority.
Live technical information site. The planned DLT is not live; membership is on ByteShares.dk.
Layers
A written description of how the intended stack is layered and where responsibilities sit. No implementation is claimed by this page, and no layer below is running.
These are stated design intentions taken from internal drafts. They describe how the system is meant to be built, not how anything behaves today.
Proposed / Non-operational — design intent, not normative invariants or conformance results.
Identity establishes the subject, governance scopes the mandate and rule context, and VPLedger describes append-only outcomes and linked corrections. Nodes would execute authorized rules; replaceable interfaces must not grant authority or become protocol truth. A wallet-held proof does not make a bare address an entitlement.
Independent reconstruction depends on retained evidence, historical rule context and a trusted snapshot. A proposed normative invariant set and conformance minimum now exist as a draft awaiting owner acceptance; conformance tests and implementation evidence remain TBD / Requires source.
01
Establish the subject, credentials and eligible authority.
02
Determine the applicable mandate, proposal and authorization.
03
Produce verifiable objects for rules, events and outcomes.
04
Preserve a reviewable history and evidence references.
05
Expose authorized protocol functions without becoming the source of truth.
06
Coordinate eligible exchange and allocation under explicit rules.
07
Provide replaceable interfaces for people and institutions.
The sequence is a documented responsibility flow, not a deployed processing pipeline.
Proposed / Non-operational. The diagram separates legal or organisational authority from technical evidence and replaceable applications. Arrows show intended responsibility, not deployed integrations.
Cooperative authority
Member and constitutional decisions belong to ByteShares.dk.
Scoped mandate
Identity, eligibility, authority and applicable rule context.
Proposed protocol
Fail-closed evaluation, outcome and evidence relationship.
ProductCo operations
Commercial execution cannot change cooperative constitutional rights.
VPLedger evidence
Append-only proof, custody references and linked correction model.
AI City modular applications
Planned replaceable application family; interfaces do not create protocol truth or authority.
Subject identifiers, credentials and proof presentation.
Recording value and participation entries as an append-only history.
Proposal, role and threshold objects expressed as protocol data.
Roles, responsibilities and message flow between participating nodes.
Read and write surfaces intended for applications and explorers.
Rules, hashes, timestamps, accounting state and references form the compact verification surface. Anchors prove that referenced material and state existed in a particular form; they do not need to contain the durable evidence itself.
Documents, attestations and other evidentiary payloads remain under explicit custody and retention controls, linked by content proofs. This separates public verification from unnecessary disclosure.
Filecoin is a planned durable-storage option in the architecture. No storage agreement, integration, retrieval path or operational data is claimed.
A Merkle root can commit to a defined set of records at an epoch boundary. Inclusion proofs can then verify one record against the snapshot without exposing or replaying the full set.
This model describes proposed functions, not investment products, prices, yields, markets or live assets.
Participation and value-accounting function within the VPLedger model.
Unit function for accounting for a defined quantity of digital storage capacity.
Higher-order storage-capacity accounting function related to the TIB unit.
Recognition and participation function within the canonical value model.
Citizenship or community-eligibility function used to express scoped participation.
Growth and contribution-allocation function in the documented model.
Conditional bridge concepts for representing externally verifiable value or asset references under governed rules. Inclusion depends on technical, legal, custody and source verification; no bridge or wrapped asset exists here.
Identity, credential and eligibility-proof function for subjects and authorized agents.
Proposed development and delivery function for governed digital services and institutional workflows; no operational service is claimed.
Productized operational implementation concept of the broader eDEV function; not a deployed city platform or service.
Proposed discovery and exchange interface for eligible storage-related records and services; no market or exchange is operating.
ByteShares' intended long-term end-product family: an extensible modular environment with expandable white-label modules for different organisations, sectors and markets. Institutional access would be bounded by identity, authority and audit requirements. UCityX is a separate planned concept; neither is deployed.
Proposed / Non-operational — review questions, not decisions or implementation contracts.
Each statement on this page is tracked against a source. A claim without a verified source is never presented as fact.
| Claim | Source type | Verification | Note |
|---|---|---|---|
| Layer names and responsibilities | Owner-stated canon; Master Business Plan v2.1 not inspected | Source claimed, not yet verified | The owner describes the intended layers; private-source fidelity, authorized disclosure scope and implementation remain unverified. |
| Storage, asset functions and infrastructure module positioning | Owner-stated aligned technical canon | Source claimed, not yet verified | Descriptions follow owner direction; underlying specification documents have not been inspected and nothing is operating. |
| Any performance or throughput characteristic | Benchmark output | No source on file | No benchmarks exist; no figures shown. |