From Concept to Measurement: A Survey of How the Blockchain Trilemma Can Be Analyzed

summary

The gist

The blockchain trilemma highlights the difficulty of simultaneously achieving a high degree of decentralization (DoD), scalability, and security in blockchain systems.

In short

This work creates a unified framework for analyzing the blockchain trilemma by defining 12 constructs across decentralization, scalability, and security and operationalizing them with 15 specific metrics. It synthesizes literature to provide a common vocabulary and map of analysis approaches, enabling reproducible quantitative evaluations.

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 used across episodes

This episode discusses

The paper

From Concept to Measurement: A Survey of How the Blockchain Trilemma Can Be Analyzed · Read on arXiv

Mansur Masama Aliyu, Niclas Kannengießer, Ali Sunyaev

Karlsruhe Institute of Technology · Technical University of Munich

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.

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>.

More episodes

← Home