Narrative Goldmine

Blockchain Scalability

3 min read

Properties

Type
  • Class
Resource
  • urn:ngm:class:blockchain-scalability
Domain
  • blockchain
Status
  • stable
Maturity
  • draft
Quality
  • 0.72
Is a
Part of
Has part
Requires
Enables
Generated
  • by: process:vault-migrate/1.0 · at: 2026-09-22T12:41:39.024503178Z
Bridges to
Contrasts with
Depends on
Implements
Legacy term id
  • BC-0602
Links
Page resource
  • urn:visionflow:page:b93bdabea566799526167e092d49b7a1d884dda164ad584ff460e4880de2b336
Related to
Uses

Blockchain Scalability encompasses the technical solutions and architectural approaches designed to increase the transaction throughput, reduce latency, and improve the efficiency of blockchain networks while maintaining security and decentralisation.

Semantic Classification

Content

Blockchain Scalability addresses the fundamental tension between decentralisation, security, and transaction throughput. Bitcoin processes approximately 7 transactions per second whilst Ethereum historically handled around 15, far below Visa’s 65,000 transactions per second capacity. Layer 2 solutions operate above the base blockchain, bundling transactions and settling them periodically on-chain. Lightning Network enables near-instantaneous Bitcoin payments with microsecond finality for micropayments, whilst Rollups on Ethereum compress hundreds of transactions into single on-chain proofs.

Sharding partitions blockchain state across parallel chains, enabling simultaneous transaction processing on different chain shards. Danksharding advances this through data availability sampling, reducing validator hardware requirements. State channels enable counterparties to execute transactions off-chain, updating shared state only when disagreements occur or channels close.

Scalability solutions introduce trade-offs: Layer 2 solutions may reduce decentralisation if few operators exist, whilst sharding increases protocol complexity. The optimal scalability architecture depends on application requirements—instant micropayments prioritise latency, financial settlements prioritise final security, and data availability systems prioritise throughput.

Current Landscape (2026)

  • Ethereum’s rollup-centric roadmap has become the dominant scaling paradigm: the Dencun upgrade (March 2024, EIP-4844 proto-danksharding) introduced “blob” data and cut Layer 2 fees by roughly 90%, and by mid-2026 the network settles over 100 million transactions daily across its L2 ecosystem while mainnet gas often sits below 0.5 gwei.
  • The Pectra upgrade activated on 7 May 2025, doubling blob throughput (EIP-7691, from 3/6 to 6/9 blobs per block), adding EOA-to-smart-contract execution for account abstraction (EIP-7702) and raising the maximum effective validator balance to 2,048 ETH (EIP-7251).
  • Fusaka went live on 3 December 2025, shipping PeerDAS (EIP-7594) so validators sample blob data via erasure coding instead of downloading it in full — enabling roughly an 8x theoretical increase in blob capacity without raising node hardware requirements — and standardising the L1 gas limit at 60M (up from 30M through 2025).
  • Fusaka also introduced lightweight “Blob Parameter Only” (BPO) forks to raise capacity without full hard forks: BPO1 (9 December 2025) lifted the blob target/max from 6/9 to 10/15, and BPO2 (7 January 2026) pushed it to 14/21.
  • The L2 market has consolidated sharply: L2Beat lists roughly 73-80 active rollups holding around $45-48bn TVL by mid-2026, with Arbitrum One and Base together commanding about 77% of L2 DeFi liquidity as many smaller general-purpose rollups shut down in 2025-2026.
  • Modular data-availability layers now compete on raw bandwidth: Celestia holds around 50% of the external DA market and its Matcha (v6) upgrade lifted maximum block size from 8MB to 128MB, while EigenDA V2 advertises around 100 MB/s and Celestia’s experimental Fibre protocol targets terabit-per-second throughput.
  • Open challenges as of 2026 remain sequencer centralisation (most rollups still use a single sequencer), cross-chain bridge security, state growth, and cross-rollup interoperability; the next named upgrade, Glamsterdam (expected mid-2026), targets enshrined proposer-builder separation (EIP-7732) and Block-level Access Lists (EIP-7928), with full danksharding still years away.

References

Provenance

Graph View

Backlinks