ProtoLedger Standard 3.0

The Two-Axis Framework for Distributed Ledger Assessment

June 2026 · Apache-2.0 · Open Standard · Authored by Oleh Bezuhlyi

UNCALIBRATED — all v1 scores are expert-judgment estimates, not statistically validated. They can be challenged at /protoledger/challenges/.

Abstract

The ProtoLedger Standard defines what a distributed ledger must achieve to function as money. It organises assessment criteria into two independently scored axes — Monetary Fitness (Layer A) and System Soundness (Layer B) — and one non-scored disclosure axis (Layer C).

Each axis is composed of named, measurable properties. Every property is scored 0–10 against defined criteria. M is the mean of the seven Layer A scores; S is the mean of the nine Layer B scores. M and S are never combined into a single total — a ledger can be monetarily fit but technically unsound, or vice versa, and collapsing the two axes would hide that distinction.

The Standard exists because the blockchain industry lacks a shared, rigorous definition of what a distributed ledger is supposed to do. In its absence, projects define their own success metrics, optimise for those metrics, and claim success. This document is an attempt to fix that.

Section I — Why This Exists

Every blockchain project that has achieved significant market capitalisation has compromised at least one founding principle in exchange for adoption speed, regulatory compliance, or investor appeal. This is not speculation — it is documented in the scoring table at /index/ and in the chain profile pages.

Bitcoin compromised on privacy, post-quantum security, and on-chain governance. Ethereum compromised on decentralisation, MEV resistance, and finality guarantees. Every subsequent chain repeated the same trade-offs while claiming to have solved them.

The result is an industry that measures itself against its own marketing rather than against principled engineering criteria. The ProtoLedger Standard is an attempt to provide those criteria — not to shame any particular project, but to give builders, investors, and users a basis for honest evaluation.

The Standard is intentionally demanding. No existing production blockchain achieves M ≥ 7 and S ≥ 7 simultaneously. This is the point.

Section II — Layer A: Monetary Fitness

Seven properties that determine whether a ledger can function as money. M is the mean of all non-null Layer A scores. A gate fires at A1 < 7: the ledger is not money-in-use regardless of other scores.

Code	Property	Score 7–10	Score 0–3
A1	Acceptability & Liquidity	Widely accepted as payment; deep liquidity; used in commerce beyond speculation.	No significant payment use; primarily speculative asset.
A2	Value Stability	Stable over 12-month horizon; empirically hedges against baseline inflation.	Highly volatile; provides no hedge against fiat inflation.
A3	Usability & Safety	Divisible to at least 6 decimal places; fungible across all network participants.	Coarse denomination; known fungibility breaks (e.g. UTXO taint).
A4	Portability & Divisibility	Fully non-custodial self-custody available; no central counterparty required.	Requires centralised custody or permission for standard transfers.
A5	Fungibility	Hard supply cap or proven disinflationary emission with no governance override.	Supply governed by discretionary inflation or uncapped issuance.
A6	Recognizability	Transparent transaction finality; provably irreversible after settlement.	Probabilistic or reversible finality; reorg risk documented.
A7	Cost Efficiency	Accepted by significant regulated merchant base or institutional custody providers.	No regulated institution accepts or custodies the asset.

Section III — Layer B: System Soundness

Nine properties that determine whether the ledger infrastructure is trustworthy and censorship-resistant. S is the mean of all non-null Layer B scores. A gate fires when B1 < 7 or B2 < 7.

Code	Property	Score 7–10	Score 0–3
B1	Supply Integrity	Nakamoto Coefficient ≥ 100; no entity controls >5% of consensus.	<10 entities can halt or reverse the chain; single-party dominance documented.
B2	Settlement Assurance	Deterministic BFT finality; no reorgs possible above Byzantine threshold.	Longest-chain rule; reorgs above 6 blocks documented in production.
B3	Resilience & Liveness	No transaction censorship documented; mempool is open and permissionless.	Documented censorship events or permissioned mempool access.
B4	No Single Point of Control	All transaction signing uses NIST PQC (ML-DSA, SLH-DSA) or equivalent.	ECDSA-only; no PQC migration path published.
B5	Rule Auditability	Default shielded transactions; identity unlinkable without explicit disclosure.	Transparent-only ledger; all addresses and amounts permanently public.
B6	Forward Security Margin	Total energy per transaction proportional to useful computational work.	Proof-of-Work with no useful computation component; energy waste by design.
B7	No Invisible Rent	All protocol upgrades require on-chain governance; no foundation veto path.	Upgrades controlled by core team, multisig, or foundation without on-chain vote.
B8	Capture-Resistant Rule-Change	Fully open-source; formal spec published; reproducible builds verified.	Closed-source components; no reproducible build; specification absent.
B9	Resource Proportionality	No extractable MEV above base fee; structural prevention at L1.	MEV structurally embedded in block proposer incentives; no mitigation.

Section IV — Layer C: Disclosures

Six design-choice axes that are disclosed but never scored. Each position is architecturally valid. Layer C values are rendered as badges on chain profiles and used as on/off filters in the Terminal. A ledger that discloses transparently scores better on B5 (privacy); disclosure itself is not scored.

privacy_posture Privacy Posture

identity_model Identity Model

issuance_ethic Issuance Ethic

consensus_cost Consensus Cost

governance_model Governance Model

autonomy_accountability Autonomy Accountability

Section V — Scoring Rules

M and S computation

M = mean of an asset's Layer A property scores.
S = mean of an asset's Layer B property scores.
M and S are never added or combined. The equal-weight default uses plain means. Archetype or slider ranking uses weighted means: M = Σ(score·w)/Σw.

N/A-by-design

A null score means the property is not applicable to this ledger's design, not that it scored zero. Null scores are excluded from the mean, not counted as 0. A ledger with 6 Layer A scores has M computed over those 6 values only.

Readiness tiers

Tier	Meaning
achieved	Property is implemented and live in production.
buildable	Technology exists; implementation not yet deployed at production scale.
speculative	Technology is an open research problem. Score represents a ceiling, not current reality.

A speculative score cannot contribute to a "ready today" verdict but is always displayed with its readiness label. The real number is never hidden.

Score Gates

Gates are warning badges. They never hide real scores. A gate fires when a critical threshold is not met:

A1 < 7 — Not money-in-use: acceptability below monetary threshold.
B1 < 7 or B2 < 7 — Not a sound system: critical infrastructure properties unmet.
B3 < 7 — Censorship-Resistant archetype only.

Section VI — Open Problems

Three properties in this Standard remain unsolved at production scale. They are included because their absence would make the Standard incomplete, not because any production system currently satisfies them.

B4 — Post-Quantum Security. Every major production blockchain has ECDSA keys in its current state. A live migration to NIST PQC primitives requires a hard fork with mandatory key rotation. No production chain has a credible, implemented migration path. The solutions exist; the political will to execute them does not.

B5 — Privacy by Default at scale. Zero-knowledge shielded pools exist (Zcash, Monero), but none combined with broad Layer A scores. Optional privacy (Ethereum's Tornado Cash attempt) provides near-zero anonymity — the opt-in population is trivially distinguishable.

B9 — Structural MEV elimination at L1. Proposer-Builder Separation and encrypted mempools mitigate but do not eliminate MEV. Content-metadata separation requires a new transaction gossip protocol. No production L1 has implemented this. FlashBots SUAVE is the most advanced research effort.

Section VII — Governance, Independence & License

Scores are never adjusted for commercial reasons. No chain can pay to improve its score. No advertiser relationship affects scoring. The methodology is public precisely so that anyone can verify this.

The Standard is authored by Oleh Bezuhlyi and published under the Apache-2.0 licence. Fork it. Implement it. Challenge it. The mechanism for formal challenges is at /protoledger/challenges/.

A valid challenge must include: the property code, the chain slug, the current score, the proposed score, and a specific verifiable source — block explorer link, published specification, or peer-reviewed audit. Claims without evidence are not challenges.

References

Nakamoto, S. (2008). Bitcoin: A Peer-to-Peer Electronic Cash System.
Castro, M., & Liskov, B. (1999). Practical Byzantine Fault Tolerance. OSDI.
NIST (2024). FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 206 (SLH-DSA). Post-Quantum Cryptography Standards.
Buterin, V. (2013). Ethereum White Paper.
Nakamoto Coefficient — Balaji Srinivasan (2017). Quantifying Decentralization.
Flashbots (2022). SUAVE: Single Unified Auction for Value Expression.
Ben-Sasson, E. et al. (2014). Zerocash: Decentralized Anonymous Payments from Bitcoin. IEEE S&P.
Lalley, S., & Weyl, G. (2018). Quadratic Voting. AEA Papers and Proceedings.
Cambridge Centre for Alternative Finance. Cambridge Bitcoin Electricity Consumption Index (CBECI).
Bezuhlyi, O. (2026). Bitcoin: A Revolution That Never Happened?

v1 archive: The original ten-principle framework (ProtoLedger v1) is preserved at protoledger/principles/. The current standard is this two-axis document.