Summary: ADI Chain's modularity allows it to be transformed into its own ecosystem of multiple sublayers and chains. For example, Layer 3 (L3) blockchains can be built on top of it and function as customized chains to host a specific application. This flexibility enables ADI to cater to a wide variety of businesses, industries, and compliance standards, ultimately paving the way to bring many businesses and individuals around the world on-chain.
Overview
ADI Network is designed with a modular and extensible architecture, which means it’s not just a single monolithic blockchain, but part of a broader framework that can be composed into multiple layers and chains. The concept of Layer-3s (L3s) refers to additional blockchain networks that run on top of the ADI L2, inheriting security from L2 (and transitively from L1) but offering even more specialization. This modular approach allows ADI to cater to diverse applications, jurisdictions, or workloads on separate chains that are all interconnected.
In practical terms, an L3 is like a “rollup on a rollup.” It could be an application-specific chain or a privacy-focused network that posts its proofs to ADI L2 (instead of directly to L1). ADI’s architecture permits multiple L3s to settle on the ADI L2, each potentially using its execution environment or rules, but relying on ADI L2.
Key Features
Modularity: ADI Network’s modular design means components can be swapped or layered. For example, the choice of data availability (on-chain vs off-chain) is a module. The choice of execution environment (EVM vs something else) could be a module in the future. By having clear interfaces (like the proving layer, the messaging layer, etc.), ADI can integrate new technology as it emerges.
Integrated L3s: A likely scenario is that ADI Network (the main L2) will host specialized L3s for things like privacy-sensitive operations, compliance-isolated environments, or partner-specific chains. For instance, a healthcare records system might run on a private L3 that anchors to ADI L2, ensuring patient data is only on that L3 yet still benefiting from Ethereum security via ADI L2. Another L3 might be for high-frequency trading that needs even lower latency and can operate with a specific VM optimized for that purpose, settling to L2 periodically.
Compliance and Segmentation: A major advantage of L3s in ADI’s context is segmentation for compliance or jurisdiction. Different countries or organizations might require certain data to remain siloed, or certain transactions to follow specific rules. By giving them their own L3, ADI can meet these requirements without cluttering or risking the main L2. L3s can implement custom economic rules or module configurations – for example, an L3 might choose to use a different gas token or a different data availability mode (maybe the country wants to host its own DAC). ADI L2 is flexible enough to accommodate that, since from L2’s perspective, the L3 is just another client submitting proofs (perhaps akin to how L1 sees an L2).
Interoperability of L3s: All L3s connected to ADI share the same proving and messaging backbone, meaning they can interoperate relatively easily.