From Concept to Measurement: A Survey of How the Blockchain Trilemma Can Be Analyzed
Listen
Radio episode about this paper
Transcript
Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.
Nadia: We're looking at the paper: "From Concept to Measurement".
Elias: Here's the gist of the paper. The blockchain trilemma highlights the difficulty of simultaneously achieving a high degree of decentralization (DoD), scalability, and security in blockchain systems.
Nadia: This work contributes a harmonized foundation for quantitative analyses of the blockchain trilemma, guiding both researchers in developing analysis approaches and practitioners in evaluating real-world systems.
Elias: Defining the Core Concepts The paper systematically reviews literature to synthesize constructs and their operationalizations through metrics to analyze the trilemma’s subconcepts.
Nadia: The authors identified 12 constructs, operationalized through 15 metrics, that capture DoD, scalability, and security.
Title and authors: Nadia: So we're looking at this paper titled "From Concept to Measurement: A Survey of How the Blockchain Trilemma Can Be Analyzed." It’s a survey that basically tries to organize all the messy ways people have been trying to measure the three big problems of blockchain systems.
Elias: Yeah, it seems like they're not just listing things; they’re trying to build a common vocabulary so researchers can actually compare their results. The authors are Masama Aliyu, Niclas Kannengießer, and Ali Sunyaev from Karlsruhe Institute of Technology and Technical University of Munich.
Priya: I'm interested in how they define these terms because right now, the definitions seem really scattered across different studies. It sounds like their main goal is to harmonize those concepts so we can actually talk about them consistently.
Nadia: Exactly. They point out that the existing guidance is fragmented and inconsistent, which makes it hard for anyone to know what they are even measuring when they compare different research projects on this topic <ref:2505.03768#pg1>.
Elias: That lack of clarity is a real hurdle because without a common language, you can't really say if one system is better than another in terms of decentralization or security, right?
Priya: Right. If the definitions are different, then the numbers you get from different benchmarks might not even be comparable <ref:2505.03768#pg1>.
The paper's summary: Nadia: So what they actually did in this survey is systematically reviewing a lot of literature on the blockchain trilemma and existing benchmarks. They synthesized all those different constructs and operationalizations into a set of twelve constructs and fifteen metrics.
Elias: That’s the core contribution, right? They aren't just summarizing; they are building a framework where you know exactly what to look for when measuring decentralization, scalability, or security in any given system.
Priya: I want to know if this framework is actually useful for real-world data. They're trying to show how these constructs and metrics apply in practice so we can trust the claims made by other studies <ref:2505.03768#pg2>.
Nadia: Right. They explain the applicability, interpretability, and limitations of these things for analyzing those three core areas: degree of decentralization, scalability, and security <ref:2505.03768#pg2>.
Elias: And they also developed an overview of analysis approaches that apply these constructs to investigate the trilemma <ref:2505.03768#pg2>. They are mapping out how different methods connect to these concepts.
Priya: It sounds like they are showing us a map, not just a list of definitions. That helps a lot because it shows how one analysis method might be better suited for understanding certain trade-offs than another <ref:2505.03768#pg2>.
The paper's improvements: Nadia: One of the main things they propose is how to actually use this framework to find good designs. They suggest a way to perform Pareto-optimal design selection by identifying specific combinations of constructs that show meaningful trade-offs across decentralization, scalability, and security <ref:2505.03768#pg1>.
Elias: That means practitioners could look at a set of systems and figure out which ones actually meet their requirements by seeing where the tensions between the subconcepts are most important <ref:2505.03768#pg1>.
Priya: I like that idea of surfacing "meaningful tensions across subconcepts." It moves beyond just saying something is good or bad, and shows you exactly where the compromises have to happen <ref:2505.03768#pg1>.
Nadia: And they also help with data collection by clarifying the input variables for these metrics. They explain what system characteristics you need to monitor, like how many validating nodes or how big a block size is, to get the right measurements <ref:2505.03768#pg2>.
Elias: That makes sense for benchmarking because it gives experimental designers a clear target: they know exactly what system features they should be manipulating to see the effect on things like maximum possible throughput <ref:2505.03768#pg2>.
Priya: So this is about making the evaluation process more systematic, giving researchers a clearer path for setting up experiments and interpreting the results <ref:2505.03768#pg2>.
Conclusion: Nadia: So to wrap up, this paper provides a common vocabulary, explicit metric formulations with their input variables, and a map of analysis approaches that should enable more reproducible evaluations and better system design under the blockchain trilemma.
Elias: It moves us toward being able to compare results across different studies in a way that’s much more consistent than what we have now <ref:2505.03768#pg1>.
Priya: I think the main thing is gaining this shared conceptual space so we can stop arguing about what decentralization actually means in different contexts <ref:2505.03768#pg1>.
Nadia: And for us, it means we have a better map to guide future research into where the real bottlenecks are occurring in these systems <ref:2505.03768#pg2>.
Elias: We’ve got a clear idea of what the tensions are, even if they aren't unique just to blockchains; they show up in consensus-based replicated databases generally <ref:2505.03768#pg1>.
Priya: I think it’s a solid foundation for actually building systems that are more robust by understanding these trade-offs better <ref:2505.03768#pg1>.
Mansur Masama Aliyu, Niclas Kannengießer, Ali Sunyaev
Karlsruhe Institute of Technology · Technical University of Munich
cs.CR
Submitted: 2025-04-26
Updated: 2026-10-30
Comments: 23 pages, 2 figures, 8 tables. v5: substantially revised. Retitled; trilemma reframed as an analytical lens; literature search extended (165 studies); applicability conditions and metric caveats added; constructs refined with feedback from the author teams of the reviewed studies; appendix on input parameters and analysis approaches added
Code: https://github.com/bitshares/whitepaper
License: http://creativecommons.org/licenses/by/4.0/
Importance score: 83/100
The gist: The blockchain trilemma highlights the difficulty of simultaneously achieving a high degree of decentralization (DoD), scalability, and security in blockchain systems.
Key concepts
- Degree of Decentralization
- This measures how equitably and autonomously validating nodes participate in consensus. It is assessed using metrics like block-proposal randomness, geographical diversity, hashing power distribution, token concentration, and wealth distribution.
- Scalability
- Scalability refers to a blockchain's ability to handle increasing workloads. It is quantified by metrics such as confirmation latency and maximum possible throughput (transactions per second), indicating how well the system manages transaction volume.
- Security
- Security is defined as the system's resilience against faults, partitions, and malicious attacks. This construct is measured using metrics like cost of attack, fault tolerance, reliability, and stale block rate to assess robustness under adverse conditions.
Terminology
Summary
The blockchain trilemma highlights the difficulty of simultaneously achieving a high degree of decentralization (DoD), scalability, and security in blockchain systems. p. 0 sunyaev}@tum. de
Abstract—The blockchain trilemma highlights the difficulty of
simultaneously achieving a high degree of decentralization (DoD),
scalability, and security in blockchain systems. Beyond blockchain, the findings offer
insights for distributed database systems that rely on consensus
and state machine replication. This work contributes a harmonized
foundation for quantitative analyses of the blockchain trilemma,
guiding both researchers in developing analysis approaches and
practitioners in evaluating real-world systems.Where the paper says it
Where the paper says it
Defining the Core Concepts
The paper systematically reviews literature to synthesize constructs and their operationalizations through metrics to analyze the trilemma’s subconcepts. The authors identified 12 constructs, operationalized through 15 metrics, that capture DoD, scalability, and security. p. 0 We
systematically reviewed literature on the blockchain trilemma
and blockchain benchmarks to synthesize constructs and their
operationalizations through metrics to analyze the trilemma’s
subconcepts. We identified 12 constructs, operationalized through
15 metrics, that capture DoD, scalability, and security. We define DoD as
the extent to which validating nodes participate equitably and
(quasi-)autonomously in consensus. Geographic distribution
and economic concentration are incorporated as influencing
factors, rather than core definitional elements, to provide a
clear operational boundary while recognizing their impact on
consensus participation. It also depends on how system performance scales with
the number of consensus-critical participants [41], [64]. We
therefore define scalability as the ability of a blockchain
system to handle changing workloads, including the number of
validating nodes per decision and the number of transactions
per second [1], [4], [65]. Some works emphasize availability and fault tolerance [6], [7], others highlight partition tolerance [16], [17],
while others stress adversarial resistance [3]. We harmonize
these by defining security as the degree to which a blockchain
system remains operational and resilient against faults, partitions, and malicious attacks [3], [6], [41].Where the paper says it
Where the paper says it
Where the paper says it
Where the paper says it
Operationalizing Constructs with Metrics
The study details 12 constructs associated with the trilemma subconcepts (5 for DoD, 3 for scalability, and 4 for security) operationalized through 15 metrics. For Degree of Decentralization, five metrics are used: block-proposal randomness, geographical diversity, hashing power distribution, token concentration, and wealth distribution. p. 6 Table IV offers an overview of the input variables used in
the metrics. 1) Degree of Decentralization: To estimate the DoD of
blockchain systems, we identified five metrics that operationalize the constructs: block-proposal randomness, geographical
diversity, hashing power distribution, token concentration, and
wealth distribution. For accurate
application, Gini-based estimates should be contextualized with
knowledge of system design and governance. 2) Scalability: We identified six metrics to operationalize
the constructs: availability, confirmation latency, and maximum
possible throughput of scalability. Benchmarks such as
BLOCKBENCH [7], BBSF [6], and Diablo [8] provide
experimental setups to evaluate blockchain systems, but employ
different constructs. To measure security, for example, stale
block rate has been used [80], [81], while other works have
used fault tolerance approximated by changes in throughput
and confirmation latency under faulty validating nodes [6], [7].Where the paper says it
Where the paper says it
Where the paper says it
Analysis Approaches and Findings
The paper compares various analysis approaches that implement these constructs to investigate the trilemma's subconcepts. Analysis approaches that addresses multiple subconcepts most commonly use maximum possible throughput (eq. p. 0 A variety of analysis approaches, such
as BBSF [6], BLOCKBENCH [7], Diablo [8], and the simulator
SimBlock [2], [9], operationalize these subconcepts using
different constructs and metrics. 1 For DoD, examples include
the construct of block-proposal randomness [10]–[12] and
the construct of wealth distribution [2], [13]–[15], each with
multiple candidate metrics. Substituting into equation 9 yields Gini ≈ 0. 244,
suggesting relatively equal wealth distribution and therefore
high DoD. Some works emphasize availability and fault tolerance [6], [7], others highlight partition tolerance [16], [17],
while others stress adversarial resistance [3]. We harmonize
these by defining security as the degree to which a blockchain
system remains operational and resilient against faults, partitions, and malicious attacks [3], [6], [41]. 4
clear conceptual foundation of DoD, scalability, and security, as well as an understanding of how these subconcepts
interact in real-world blockchain systems. Existing literature
presents multiple and sometimes conflicting definitions of these
subconcepts, which dilutes the conceptual foundation of the
blockchain trilemma and complicates empirical analyses aimed
at identifying Pareto-optimal designs.Where the paper says it
Where the paper says it
Where the paper says it
Where the paper says it
Contributions to Research
The study makes three main contributions to research and practice. First, it synthesizes the literature on constructs and their operationalization, explaining their applicability, interpretability, and limitations for evaluating the blockchain trilemma. p. 1 This work contributes to purposeful evaluation of blockchain
systems under the trilemma in three ways. First, we synthesize
common constructs and their operationalization through metrics,
explaining their applicability, interpretability, and limitations for
analyzing DoD, scalability, and security. First, we synthesize
common constructs and their operationalization through metrics,
explaining their applicability, interpretability, and limitations for
analyzing DoD, scalability, and security. Second, by clarifying
the input variables of these metrics, we support data collection
in benchmarks (e. , which system characteristics must be
monitored to feed relevant metrics). Third, by comparing
analysis approaches based on their choice of constructs and
metrics, we guide the selection of suitable approaches for future
investigations.Where the paper says it
Where the paper says it
Where the paper says it
Limitations and Future Directions
The scope of this study is bounded by conceptual harmonization rather than empirical validation. The metric catalog presents operationalizations developed under heterogeneous assumptions, workloads, and system models. p. 4 They operationalize consistency
via fork probability, availability via throughput, and DoD via the
probability that a partitioned network ceases to function. While
these constructs are conceptually appealing, their applicability
to heterogeneous permissioned systems is limited by the
restrictive assumptions of the system model, such as eventual
consistency, equal computational power, and at least two-thirds
honest validating nodes, which constrain generalizability. We identified 12 constructs, operationalized through
15 metrics, that capture DoD, scalability, and security. We explain
how these constructs apply across different blockchain systems and
provide a structured overview that supports benchmarking and
blockchain system design. Benchmarks such as
BLOCKBENCH [7], BBSF [6], and Diablo [8] provide
experimental setups to evaluate blockchain systems, but employ
different constructs. To measure security, for example, stale
block rate has been used [80], [81], while other works have
used fault tolerance approximated by changes in throughput
and confirmation latency under faulty validating nodes [6], [7]. In contrast, protocols with probabilistic finality, such
as Nakamoto consensus in Bitcoin [23], are less sensitive to
network size, but relax consistency assumptions and provide
only eventual consistency [41]. Although the blockchain trilemma originated in blockchain
discourse, similar tensions occur in consensus-based replicated
databases (e.Where the paper says it
Where the paper says it
Where the paper says it
Where the paper says it
Conclusion
This work provides a common vocabulary, explicit metric formulations with inputs, and a map of analysis approaches that together enable more reproducible, comparable evaluations and more purposeful system design under the blockchain trilemma. p. 1 Based on this analysis, we
developed an overview of analysis approaches that apply these
constructs and metrics to investigate the blockchain trilemma. This work contributes to purposeful evaluation of blockchain
systems under the trilemma in three ways. In contrast, protocols with probabilistic finality, such
as Nakamoto consensus in Bitcoin [23], are less sensitive to
network size, but relax consistency assumptions and provide
only eventual consistency [41]. Although the blockchain trilemma originated in blockchain
discourse, similar tensions occur in consensus-based replicated
databases (e. In contrast, protocols with probabilistic finality, such
as Nakamoto consensus in Bitcoin [23], are less sensitive to
network size, but relax consistency assumptions and provide
only eventual consistency [41]. Although the blockchain trilemma originated in blockchain
discourse, similar tensions occur in consensus-based replicated
databases (e. In contrast, protocols with probabilistic finality, such
as Nakamoto consensus in Bitcoin [23], are less sensitive to
network size, but relax consistency assumptions and provide
only eventual consistency [41]. Although the blockchain trilemma originated in blockchain
discourse, similar tensions occur in consensus-based replicated
databases (e. In contrast, protocols with probabilistic finality, such
as Nakamoto consensus in Bitcoin [23], are less sensitive to
network size, but relax consistency assumptions and provide
only eventual consistency [41]. Although the blockchain trilemma originated in blockchain
discourse, similar tensions occur in consensus-based replicated
databases (e.Where the paper says it
Where the paper says it
Where the paper says it
Where the paper says it
Where the paper says it
Green — the paper says it, and the page is printed. Red — no passage carries it, so treat that sentence as unverified. The same check runs on your own text: check a summary against its source, $5.
Improvements for AI systems
-
Improved system can perform Pareto-optimal design selection by identifying construct tuples that reveal meaningful trade-offs across degree of decentralization, scalability, and security. This allows practitioners to select designs that meet common non-functional requirements by surfacing
meaningful tensions across subconcepts.
-
The AI system can support systematic benchmarking by providing explicit input variables for metrics, such as the number of validating nodes or the maximum block size. This directly supports experimental design by clarifying
what blockchain system characteristics (e.g., maximum block size) could be manipulated to investigate system behaviors in focus (e.g., maximum possible throughput).
-
The system can generate a coherent theoretical framework for measuring the trilemma by synthesizing literature on constructs and their operationalization through metrics. This provides a
common vocabulary, explicit metric formulations with inputs, and a map of analysis approaches that together enable more reproducible, comparable evaluations.
-
The AI system can guide research by comparing different analysis approaches based on their choice of constructs and metrics. This helps researchers position empirical results within a
shared conceptual space
and suggests opportunities for developingmore advanced analysis approaches that cover subconcepts and their interrelationships in more detail.
-
The system can refine security assessments by combining multiple indicators, such as fault tolerance, stale block rate, and reliability. This addresses the finding that
No single measure captures all aspects of security,
leading to a more comprehensive view of system robustness under adversarial or fault conditions.
Abstract
The blockchain trilemma provides an analytical lens for examining trade-offs among degree of decentralization (DoD), scalability, and security in blockchain systems. However, different aspects of these dimensions are measured in different ways, making it difficult to justify metric selection, compare results across studies, and interpret what a metric value means for a trilemma dimension. Through a review of blockchain-trilemma related literature, we synthesize 12 measurable aspects and 15 metrics for analyzing DoD, scalability, and system-level security in core blockchain systems. We clarify which aspects of the blockchain trilemma dimensions these metrics quantify, when they are applicable, and how their interpretation depends on blockchain system designs and analysis approaches. These results help researchers and practitioners select suitable metrics, interpret metric values, and compare blockchain systems with respect to trade-offs among DoD, scalability, and security.
Sources
- A Fast Confirmation Rule for the Ethereum Consensus Protocol
- SoK: Blockchain Decentralization
- Automated Market Makers in Cryptoeconomic Systems: A Taxonomy and Archetypes
Related papers
- From Strategy Search to Policy Learning: MCTS-Guided Adversarial Co-Evolution for LLM Safety Alignment
- Privacy Leakage from Recurrent State in LLM Inference
- Incrementally Verifiable Oracle Aided Computation
- Privilege and confidentiality in generative AI workflows
- BadMoE: Backdooring Mixture-of-Experts LLMs via Routing-Aware Triggers and Task-Underutilized Experts
- CoVault: Secure, Scalable Analytics of Personal Data