Hierarchical and Layered Blockchain Architectures

51 concepts49 papers1 proposal

Early blockchain networks operated on a flat topology: every node maintained the exact same global state, executed the same transactions, and participated in the same consensus rounds. While this design maximizes decentralization, it imposes a severe performance penalty. As demonstrated by Tien Tuan Anh Dinh et al. in Untangling Blockchain: A Data Processing View of Blockchain Systems and BLOCKBENCH: A Framework for Analyzing Private Blockchains, flat permissioned blockchains lag orders of magnitude behind traditional database systems due to architectural bottlenecks in execution and consensus.

To bridge this gap, a major research direction has emerged around hierarchical and layered blockchain architectures. Instead of forcing a monolithic network to handle all operations, these frameworks decompose the system along two primary dimensions: vertical functional layering (separating software responsibilities) and horizontal network tiering (separating local execution from global coordination).

Vertical Layering: Decomposing the Monolith

Why should a node's network routing logic be tightly coupled with its smart contract execution? In traditional database design, storage engines are strictly separated from query planners. Layered blockchain architectures apply this exact separation of concerns to distributed ledgers.

Tien Tuan Anh Dinh et al. formalized this via a modular four-layer software stack consisting of consensus, data model, execution, and application layers. By isolating these components, developers can independently optimize or swap out specific protocols without destabilizing the entire system.

This modular paradigm has been widely adapted across specialized domains to separate low-level cryptographic security from high-level business logic:

Furthermore, Rui Zhang et al. in Security and Privacy on Blockchain demonstrate that this modularity allows security auditors to isolate and mitigate vulnerabilities at specific stages of the transaction lifecycle rather than treating the ledger as an opaque, unmanageable whole.

Horizontal Tiering: Shielding the Edge via Gateways

While vertical layering organizes software, horizontal tiering reorganizes the physical network topology. This is crucial for the Internet of Things (IoT) and mobile networks, where edge devices lack the battery, bandwidth, and storage required to maintain a massive distributed ledger.

The core intuition behind horizontal tiering is to delegate the heavy cryptographic lifting. Instead of forcing every device to act as a full node, the network is split into high-resource and low-resource tiers.

+-------------------------------------------------------+
|             High-Resource Overlay Network             |
|   (Global Ledger, Heavy Consensus, Gateway Nodes)     |
+-------------------------------------------------------+
                           ^
                           | Gateway Mediation
                           v
+-------------------------------------------------------+
|             Low-Resource Edge Network                 |
|   (Local Transactions, Constrained IoT/D2D Nodes)     |
+-------------------------------------------------------+

Ali Dorri et al. introduced this concept in LSB: A Lightweight Scalable Blockchain for IoT security and anonymity by separating resource-constrained edge devices from a high-resource overlay network of cluster heads. The edge devices only interact with local managers, while the overlay handles the global public ledger.

Taking this further, Yehan Zhang demonstrates in Blockchain-based decentralized identity system: Design and security analysis and Blockchain-based Secure D2D localisation with adaptive precision how delegating consensus and ledger maintenance to a dedicated gateway layer allows low-power mobile devices to achieve secure data registration and device-to-device (D2D) localization without the energy costs of full network participation.

Performance Isolation via Main-Chain and Sub-Chain Topologies

In large-scale systems, a surge of transactions in one application can congest an entire flat network. Hierarchical architectures solve this by nesting independent sub-chains (or secondary chains) within a primary main-chain.

This design provides performance isolation. For example, in decentralized machine learning, Zehui Xiong et al. in Scalable and Communication-efficient Decentralized Federated Edge Learning with Multi-blockchain Framework and Dongdong Ye et al. in Blockchain-based Federated Learning for Industrial Metaverses: Incentive Scheme with Optimal AoI utilize a main chain for global model aggregation and multiple independent subchains for local gradient updates. If one learning task experiences a massive influx of updates, the congestion is confined to its specific subchain, leaving the rest of the network unaffected.

This multi-tier ledger architecture operates across several other domains:

Stratified and Meta-Consensus Frameworks

The final piece of the hierarchical puzzle is the consensus mechanism itself. In a flat network, broadcasting votes scales poorly ($O(N^2)$ communication overhead). Hierarchical consensus breaks the network into smaller, manageable groups or tiers.

As surveyed by Weili Wu 0001 in Recent Advances of Blockchain and its Applications, hierarchical committee-based structures balance the trade-off between scalability and security by utilizing smaller committees for primary validation while maintaining broad network oversight. To optimize this, Mengqian Zhang et al. in An Efficient and Robust Committee Structure for Sharding Blockchain propose a multi-tier monitoring architecture where a global referee committee oversees localized, randomly selected subsets within each shard.

Furthermore, consensus protocols can be entirely heterogeneous across layers. Wenlong Feng et al. in Grouped Multilayer Practical Byzantine Fault Tolerance Algorithm: A Practical Byzantine Fault Tolerance Consensus Algorithm Optimized for Digital Asset Trading Scenarios introduce a stratified approach where upper layers run a heavy Practical Byzantine Fault Tolerance (PBFT) protocol and recursively delegate requests to lower layers running a lightweight Raft protocol.

In a sharded setting, Sajjad Rahnama et al. in RingBFT: Resilient Consensus over Sharded Ring Topology propose a "meta-BFT" protocol that isolates intra-shard agreement from inter-shard coordination. By focusing purely on routing and verifying proofs between shards rather than managing their internal consensus logic, the system scales gracefully to hundreds of global nodes.

Key Foundational Work

Untangling Blockchain: A Data Processing View of Blockchain Systems (2017) — contributed 1 concept elements to this direction.
BLOCKBENCH: A Framework for Analyzing Private Blockchains (2017) — contributed 1 concept elements to this direction.
Digital trade coin: towards a more stable digital currency (2018) — contributed 1 concept elements to this direction.
History & citationVersion 1 · 2026-10-04

Current · Permanent link

View frozen version 1

Cite this direction

Latest version (a living page):

@misc{lacuna_layered_blockchain_architecture_e4c5f9ba,
  title = {layered blockchain architecture},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/layered-blockchain-architecture/rdr_e4c5f9bafdca4bef95cf8274507168bf},
  note = {Latest version of a living research direction; cite a version for a fixed text. Accessed 2026-11-20},
}

This exact version (version 1, frozen text):

@misc{lacuna_layered_blockchain_architecture_e4c5f9ba_v1,
  title = {layered blockchain architecture},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/layered-blockchain-architecture/rdr_e4c5f9bafdca4bef95cf8274507168bf/v/1},
  note = {Version 1, frozen 2026-10-04. Accessed 2026-11-20},
}
About

These directions overlap with this one through shared papers.

See something wrong? Report a mistake