Distributed Ledger Network
Describe one persistent distributed ledger network and its protocol, participation, governance and evidence context.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 10 questions
Network identity and protocol Which network and how it agrees on state.
Chain and protocol
Chain identifier, genesis, consensus and protocol version.
Network identity
The network is identified by its chain identifier and genesis, distinct from forks and test networks.
- Which chain identifier and genesis block identify the network?
- Is this the main network, a test network or a fork?
Consensus
The consensus mechanism and finality behaviour.
- Which consensus mechanism does the network use?
- When is a transaction considered final on this network?
Participation and governance Who runs it and who decides on changes.
Participants and governance
Node operators, validators and protocol change process.
Validator set
Who validates blocks and how they are admitted.
- Is participation permissionless or permissioned?
- Who are the validators, and how concentrated is control?
Protocol change
How upgrades are proposed, decided and activated.
- How are protocol upgrades proposed and decided?
- Which upgrades or forks happened, and when?
Compliance and risk Legal status and operational risk.
Regulatory context
Applicable regulation and known incidents.
Status and incidents
Regulatory status and recorded outages, attacks or reorganisations.
- Which regulatory regimes apply to services built on the network?
- Which outages, attacks or chain reorganisations have been recorded?
Classifiers Filled
- Family
- World Models
- Category
- Information and virtual systems
- Entry kind
- entity
- Navigation path
- NAV.INF.VRT.DLT
- Domain
- INF.VRT.DLT
- Industry
- Cross-industry
- Tags
- distributedledgernetworkinf.vrt.dlt
What it is Filled
A distributed ledger network is a network of nodes that maintains a shared, replicated ledger under a consensus protocol, such as a public blockchain or a permissioned ledger operated by a consortium. The subject is the network with its protocol, participants and governance, the context in which tokens and smart contracts live; the tokens, contracts and individual transactions are described in their own models.
In scope
- Network identity, ledger-domain references and protocol-version context
- Participation, governance, consensus assumptions, finality observations and lifecycle evidence
- Network-specific access, retention, interface and operational-observation context
Out of scope
- Token issuance, balances, custody, investment decisions and accounting ledgers
- Smart contract source, execution semantics, deployment, transaction submission and signing
- Node provisioning, key management execution, governance voting and incident response execution
- Legal classification of services or assets; bridge verification, settlement guarantees and universal non-blockchain consensus schemas
Why it exists Filled
Describe one persistent distributed ledger network and its protocol, participation, governance and evidence context.
Distinguishing features Filled
- It is the network and its governance, not a token, smart contract or transaction on it.
- Its identity rests on a chain identifier and genesis, so forks become separate networks.
- Governance spans on-chain rules and off-chain decisions by developers, validators and consortia.
- Distinct from a conventional ledger kept by one accountable party.
What robots and AI may and may not do Filled
Must not
- Sign or submit transactions without explicit human authorisation.
- Handle or expose private keys or seed phrases.
- Give personalised investment advice about network tokens.
- Treat a test network or fork as the main network.
- Help circumvent sanctions or anti-money-laundering controls.
Only with a human decision
- Any transaction that moves value.
- Operating or changing a validator or node.
- Voting on governance or protocol upgrade proposals.
May
- Read public ledger data and network parameters.
- Report the chain identifier, consensus and finality of a network.
- Monitor network health, upgrades and incidents.
Moral aspects Filled
- Immutability means errors and personal data written to the ledger may never be removed.
- Concentrated validator control can undermine the decentralisation users rely on.
- Energy use and financial risk vary widely between networks and affect society beyond users.
Who is affected
- Users holding assets on the network
- Node operators and validators
- Developers of applications on the network
- Regulators and the wider public
Owners Filled
Steward
The foundation, consortium or developer community that maintains the protocol, together with the validators who operate the network.
Roles
- Model steward
- Maintains boundary, identity resolution and versioned local records
- Network governance liaison
- Attributes proposals, mandates and adoption evidence without claiming sole ownership
- Evidence reviewer
- Checks profile scope, provenance and conflicting observations
- Access and records custodian
- Controls disclosure, preservation holds and authorized local disposition
- Operational observer
- Supplies scoped metrics and incident references without changing the network
Master systems
- Protocol specification repository
- Chain registry
- Block explorer
Links to other meta-models Filled
aligned
- WM-SFT-002 - Candidate registry parent alignment only; generic software-system ownership and lifecycle are not duplicated or imposed as network governance.
- CAIP-2 - Namespace-qualified chain identifier alignment where supported; namespace resolution and actual network binding require profile evidence.
- PROV-O - Conceptual mapping of record, observation activity and responsible role; no implemented RDF mapping or conformance claim.
references
- WM-VRT-011 - Optional contract identity bound to network and ledger domain; contract execution and lifecycle remain externally mastered.
- WM-ECO-013 - Optional native or hosted token reference; no required token, balance management or financial rights inferred.
- WM-XCT-014 - Optional accounting ledger or account integration; network domain and business ledger are distinct masters.
neighbor
- WM-SFT-002 Software System / Business Application - Registry parent is retained as a candidate alignment. Operator-governed software-system identity is distinct from a network whose governance may span independent participants. No unreviewed inheritance is asserted.
- WM-VRT-011 Smart Contract - Optional deployed-contract references carry network and domain context only; executable logic, deployment and contract lifecycle stay outside this root.
- WM-ECO-013 Crypto / Token and WM-XCT-014 Ledger / Account - Assets and account records retain their own identities. A network can operate without a native token; a replicated ledger domain is not automatically an accounting account.
- Nodes, organizations, channels and other networks - Node and participant master records remain external. A channel is a ledger domain, not automatically a separate network. A lasting split may merit a successor network; a temporary fork does not automatically do so.
parent
- WM-SFT-002
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A network is identified by its chain identifier, for example under CAIP-2, together with its genesis block hash.
- Nodes and validators are identified by their network keys or addresses.
Direct properties not applicable Not applicable
Not applicable
A distributed ledger network is a digital system; its parameters are recorded as protocol settings, not measured physical properties.
Recognition optional Filled
- A network is recognised by its chain identifier, genesis, client software and public endpoints.
- Often confused with its native token, with a test network or with a fork sharing the same name.
Capabilities and actions required Filled
- Transactions can be validated, ordered and finalised by consensus.
- The full history can be replayed and verified by any full node.
- The protocol can be upgraded through its governance process.
Hazards and failure modes required Filled
- Consensus attacks or chain reorganisations that reverse transactions.
- Loss of funds through key compromise.
- Permanent exposure of personal data written to the ledger.
Standards and interfaces required Filled
- CAIP chain identifiers for cross-network references.
- JSON-RPC node interfaces exposed by client software.
- ISO 22739 vocabulary for blockchain and distributed ledger technologies.
Context of use required Filled
- Used for crypto-assets, tokenised assets, supply chain tracing and shared registers.
- Services built on networks fall under crypto-asset and anti-money-laundering regulation such as MiCA.
Sources Filled
- Blockchain Technology Overview - National Institute of Standards and Technology
- CAIP-2: Blockchain ID Specification - Chain Agnostic Improvement Proposals community
- Ledger - Hyperledger Fabric project
- The Ordering Service - Hyperledger Fabric project
- Private data - Hyperledger Fabric project
- Proof-of-stake (PoS) - Ethereum documentation community
- PROV-O: The PROV Ontology - World Wide Web Consortium
- RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force
- ISO 22739 Blockchain and distributed ledger technologies - Vocabulary (ISO)
- Regulation (EU) 2023/1114 on markets in crypto-assets, MiCA (European Union)
- FATF Guidance for a Risk-Based Approach to Virtual Assets and Virtual Asset Service Providers (Financial Action Task Force)
Open questions
- Verify source responses and immutable revisions, reconcile documentation branch labels and pin each adopted protocol profile.
- Develop executable schemas and fixtures for identifier collision, invalid included transaction, stalled finality, divergent observers, lasting split, private-data purge and retirement.
- Research native non-blockchain ledgers and cross-network trust boundaries before widening implementation coverage.
- Restore independent external review and complete adopting-profile legal and operational review before canonical promotion.
- Independent external review absent; Claude and Grok skipped under owner override
- Direct HTTP checks not attempted because owner reports sandbox blocking; source status and body digests remain unmeasured
- Immutable revisions for living documentation and current profile applicability are unverified
- Nested instance schemas, profile-specific identifiers, interface adapters and conformance fixtures are not implemented
- Non-blockchain ledgers, bridge security, rollup settlement, economic analysis and jurisdiction-specific legal rules require separate research
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-vrt-010-distributed-ledger-network/spec.yaml, ver-cy/world-models/card-supplements/wm-vrt-010-distributed-ledger-network.json