No critique of blockchain for institutional finance has been more persistent — or more persistently referenced after it ceased to be accurate — than scalability. ‘Blockchain can’t handle the transaction volumes of global capital markets’ was true of first-generation infrastructure and is now, in most relevant respects, an outdated frame. Understanding precisely how the scalability picture has changed, and what the remaining challenges look like, is essential for technology leaders evaluating blockchain infrastructure rather than blockchain promises.
The Blockchain Trilemma: What It Actually Means
The blockchain scalability trilemma, articulated early in blockchain’s development, holds that a blockchain network can optimize for only two of three properties simultaneously: decentralization (no single party controls the network), security (the network resists attack and manipulation), and scalability (the network can process a high volume of transactions quickly). A network maximizing decentralization and security — Bitcoin and Ethereum’s base layer — achieves this at the cost of throughput. A network maximizing throughput and security may do so by centralizing validation to fewer parties. This trade-off structured a decade of blockchain architecture debate.
The solution that has emerged — and is now deployed at scale — is not to optimize a single chain across all three dimensions, but to separate the three functions across layers, allowing each layer to be optimized independently.
The Layered Architecture Solution
Layer 1: Security and Finality
The base layer (Ethereum, for example) is optimized for security and decentralization. It processes relatively few transactions directly — Ethereum’s base layer handles 15–30 TPS — but provides the cryptographic finality that all upper layers inherit. Every transaction processed on Layer 2 solutions is ultimately settled and secured on the Layer 1 base layer, meaning the base layer’s security guarantees apply to the entire transaction volume of the upper layers.
Layer 2: Throughput
Layer 2 solutions process transactions in batches off-chain, periodically submitting compressed proofs or transaction data to the Layer 1 chain. Ethereum-based Layer 2 rollups now process over 40,000 TPS following the Dencun upgrade (EIP-4844), which introduced blob space — a dedicated, low-cost data lane for rollup data. ZK rollups, which use zero-knowledge proofs to compress and verify large transaction batches cryptographically, are projected to reach 15,000+ TPS at approximately $0.0001 per transfer — making them viable for institutional-scale transaction volumes at a cost structure far below traditional market infrastructure.
Modular Architecture: Separating Execution, Settlement, and Data
Beyond the Layer 1/Layer 2 model, modular blockchain architectures decouple the execution layer (where transactions are processed), the settlement layer (where finality is established), and the data availability layer (where transaction data is stored and accessible) into separate, independently optimizable components. Polygon’s AggLayer, Ethereum’s Danksharding roadmap, and Celestia’s dedicated data availability layer all follow this modular paradigm, allowing each component to be scaled independently rather than requiring a single monolithic chain to handle all three functions simultaneously.
Current Throughput Benchmarks for Institutional Applications
| Infrastructure | Throughput | Finality | Transaction Cost |
|---|---|---|---|
| Ethereum base layer | 15–30 TPS | ~12 seconds | $0.25–$0.50 (can spike significantly) |
| Ethereum L2 rollups (post-Dencun) | 40,000+ TPS | Minutes to L1 finality | Under $0.05 |
| ZK rollups (projected mid-2026) | 15,000+ TPS | Under 1 second | ~$0.0001 |
| Hyperledger Fabric / Quorum | 10,000+ TPS in production | Configurable, near-instant | Minimal — no gas token |
| Solana (base layer) | 65,000 TPS actual; 710,000 theoretical | 21–46 seconds | Sub-cent |
| Polygon PoS (2026 roadmap) | Toward 100,000 TPS (AggLayer) | Variable | Sub-cent |
What Scalability Means Differently for Institutional Finance
Raw TPS is not the right scalability metric for most institutional tokenization use cases. Most regulated asset tokenization platforms are not competing with Visa’s transaction volumes — they are serving institutional issuers who may have dozens to thousands of investors, not hundreds of millions. The relevant scalability questions for institutional finance are different:
- Finality consistency: For settlement and compliance purposes, what matters is not just throughput but the consistency of finality — is every transaction finalized with the same latency, or does congestion create variable and unpredictable finality times?
- Gas price stability: On public networks, transaction costs can spike dramatically during network congestion, making budget planning difficult. Layer 2 solutions with dedicated block space (blobs) address this, as do permissioned networks with no gas token economics.
- Compliance logic overhead: Smart contracts with sophisticated whitelisting, compliance checking, and governance logic have higher computational requirements than simple token transfers. The throughput available for compliance-heavy tokenized securities transactions is lower than raw TPS numbers for simple transfers.
- Data availability at scale: As the number of tokenized assets grows, the requirement to store and access historical transaction data for audit, reporting, and regulatory purposes creates data infrastructure requirements that are distinct from transaction throughput.
Permissioned Networks and Institutional-Grade Throughput
For institutional deployments on permissioned or enterprise blockchain environments — JPMorgan Kinexys, R3 Corda, Hyperledger Fabric, Canton Network — the scalability picture is already at production-grade. Hyperledger Fabric and Quorum-based environments achieve 10,000+ TPS in production environments, processing interbank transfers and securities settlement at volumes relevant to wholesale financial markets. The throughput constraint in these environments is typically network bandwidth and storage, not consensus mechanism — and both scale with hardware investment in ways that public blockchain TPS does not.
The more relevant scalability consideration for permissioned institutional networks is interoperability with public chain liquidity and DeFi infrastructure — the challenge covered in detail in the previous article in this series. A permissioned blockchain can scale to institutional transaction volumes within its own network; connecting those volumes to the broader tokenized asset ecosystem requires the cross-chain infrastructure that interoperability protocols provide.
The Remaining Scalability Challenges
Honest assessment of where scalability challenges remain for institutional blockchain infrastructure in 2026 points to three specific areas rather than raw throughput: data availability under sustained high load (ensuring that rollup data remains accessible and verifiable during peak congestion periods), latency consistency across geographically distributed validator nodes (critical for real-time settlement applications), and regulatory data storage requirements (the need to maintain verifiable, queryable records of compliance events for multi-year audit windows, which creates storage demands that grow linearly with adoption). These are solvable engineering problems — several teams are actively solving them — but they are more accurate descriptions of the frontier than ‘blockchain can’t scale.’
Scalability and Compliance Logic: The Overhead Most Benchmarks Ignore
Most blockchain scalability benchmarks measure simple token transfers: the maximum number of times an ERC-20 contract can move tokens between two addresses per second. Institutional tokenized securities contracts are materially more complex than this. A single transfer on a compliance-enforcing platform involves checking the sender’s balance, validating the recipient’s whitelist status against an identity registry, evaluating jurisdiction-specific transfer conditions, and potentially logging the compliance event for audit purposes — all within the same transaction block. The computational overhead of this compliance logic reduces effective throughput below the raw TPS benchmark for simple transfers.
This distinction matters for institutions evaluating blockchain infrastructure based on published throughput numbers. A platform quoting 10,000 TPS for simple token transfers may achieve a fraction of that for compliance-heavy security token transfers with full eligibility checking. Evaluating infrastructure on its actual throughput for the intended use case — compliance-enforced tokenized security transfers with full onchain audit trail — rather than on its theoretical maximum for unrestricted token movement is the relevant metric for institutional procurement decisions.
What the Scalability Roadmap Means for Institutional Planning
For institutions planning blockchain infrastructure investment today, the relevant scalability trajectory suggests two practical considerations. First, throughput limitations are unlikely to be the binding constraint for institutional tokenization deployments within the next five years — the gap between current Layer 2 throughput (40,000+ TPS) and what institutional asset servicing actually requires (thousands to low hundreds of thousands of transactions per day for most issuances) is wide enough that TPS will not drive architecture decisions for most institutional use cases in the near term. Second, the modular architecture trend — separating execution, settlement, and data availability — means that the scalability infrastructure is likely to continue improving faster than institutional demand grows, making today’s scalability investments forward-compatible rather than requiring replacement as the infrastructure matures.
How Blockmaze Structures Settlement for Scale
Blockmaze provides T+0 atomic settlement on every transaction — meaning the compliance check, transfer, and register update are a single block event with immediate finality, not a multi-step process with a settlement lag. The governance and compliance logic, including KYB/KYC verification and DAO-governed issuance approval, is designed to scale with the number of issuances on the platform rather than creating per-transaction bottlenecks. Proof of Reserve attestations on a 15-day cycle are structured as off-chain oracle inputs to the onchain record, meaning they do not add transaction volume pressure during the attestation cycle but produce verifiable, queryable state changes that are available for real-time audit.
Frequently Asked Questions
1. Is blockchain scalable enough for capital markets transaction volumes?
For most institutional tokenization use cases — serving thousands to hundreds of thousands of investors rather than retail transaction volumes — yes. Layer 2 solutions processing 40,000+ TPS, permissioned enterprise networks at 10,000+ TPS, and ZK rollups projected toward 15,000+ TPS at minimal cost are all comfortably above the transaction volume requirements of institutional asset servicing.
2. What is the blockchain trilemma?
The trilemma is the observation that blockchain networks face trade-offs between decentralization, security, and scalability — optimizing fully for all three simultaneously is structurally difficult. Layered and modular architectures address this by separating the three properties across different layers of the stack.
3. What is the Ethereum Dencun upgrade’s impact on institutional scalability?
The Dencun upgrade (EIP-4844, March 2024) introduced ‘blob space’ — a dedicated, low-cost data lane for Layer 2 rollup data. This reduced average L2 transaction fees by approximately 90% and removed the primary economic barrier to Layer 2 adoption for cost-sensitive institutional applications.
4. Does TPS (transactions per second) matter for institutional tokenized assets?
TPS is a necessary but insufficient metric for institutional applications. Finality consistency, gas price stability, compliance logic overhead, and data availability under sustained load are equally or more important metrics for regulated tokenized asset infrastructure.
5. How does Blockmaze handle settlement at scale?
Blockmaze provides T+0 atomic settlement on all transactions — compliance check, transfer, and register update as a single block event. Governance and compliance logic is designed to scale with issuance volume, not per-transaction complexity.