Layers

Protocol Architecture

Documented architecture

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.

Source / verification: Owner interim-platform canon; protocol implementation unverified
Document version: Not yet assigned
Last reviewed: 26 September 2026

Design principles as written

Documented architecture

Stateless, protocol-enforced logic — rules should execute from explicit inputs and recorded state rather than hidden application state.
Wallet as account — authority and participation attach to verifiable wallet-held proofs, not a mandatory platform account.
Minimal frontend and cloud dependency — interfaces are replaceable access surfaces, not the source of protocol truth.
Resilience and auditability — append-only history, portable evidence and explicit state transitions support reconstruction and review.

These are stated design intentions taken from internal drafts. They describe how the system is meant to be built, not how anything behaves today.

Protocol system flow

Documented architecture

Identity

Establish the subject, credentials and eligible authority.

Governance

Determine the applicable mandate, proposal and authorization.

Proof

Produce verifiable objects for rules, events and outcomes.

Auditability

Preserve a reviewable history and evidence references.

Services

Expose authorized protocol functions without becoming the source of truth.

Markets

Coordinate eligible exchange and allocation under explicit rules.

Applications

Provide replaceable interfaces for people and institutions.

The sequence is a documented responsibility flow, not a deployed processing pipeline.

Layer register

Identity layer (eIDspot)Documented architecture
Subject identifiers, credentials and proof presentation.
Ledger layer (VPLedger)Documented architecture
Recording value and participation entries as an append-only history.
Governance layerDocumented architecture
Proposal, role and threshold objects expressed as protocol data.
Node layerDocumented architecture
Roles, responsibilities and message flow between participating nodes.
Interface layerPlanned
Read and write surfaces intended for applications and explorers.

Storage & Data Sovereignty

On-chain anchors

Documented architecture

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.

Off-chain durable evidence

Documented architecture

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 positioning

Planned

Filecoin is a planned durable-storage option in the architecture. No storage agreement, integration, retrieval path or operational data is claimed.

Merkle snapshots

Documented architecture

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.

Asset & value architecture

The canonical model describes functions, not investment products, prices, yields, markets or live assets.

VPL / Vimple

Documented architecture

Participation and value-accounting function within the VPLedger model.

TIB / Terabyte

Documented architecture

Unit function for accounting for a defined quantity of digital storage capacity.

PIB / Petabyte

Documented architecture

Higher-order storage-capacity accounting function related to the TIB unit.

JOYY

Documented architecture

Recognition and participation function within the canonical value model.

CTZ

Documented architecture

Citizenship or community-eligibility function used to express scoped participation.

GROW

Documented architecture

Growth and contribution-allocation function in the documented model.

FIL / ETH / BTC / RWA SmartCoin bridges

Planned

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.

Infrastructure modules

eIDspot

Documented architecture

Identity, credential and eligibility-proof function for subjects and authorized agents.

eDEV

Planned

Proposed development and delivery function for governed digital services and institutional workflows; no operational service is claimed.

UCityX

Planned

Productized operational implementation concept of the broader eDEV function; not a deployed city platform or service.

FILDEX

Planned

Proposed discovery and exchange interface for eligible storage-related records and services; no market or exchange is operating.

AI City

Planned

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.

Current state

Implementation: None claimed
Reference client: Not available
Wire format: Draft description only
Conformance tests: Not written

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
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; the cited source document 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.