|
1 | 1 | # XDC Network Architecture |
2 | 2 |
|
3 | | -This document explains the technical architecture of XDC Network, including its hybrid design, consensus mechanism, and key components. |
| 3 | +The XDC Network is a **Layer-1**, **EVM-compatible hybrid blockchain** architecture designed to support both public decentralization and private enterprise requirements. |
| 4 | + |
| 5 | +**It combines:** |
| 6 | + |
| 7 | +- Public blockchain transparency |
| 8 | +- Private/permissioned network privacy |
| 9 | +- Enterprise-grade interoperability and compliance |
| 10 | + |
| 11 | +This hybrid design enables XDC to serve trade finance, tokenization, payments, and regulated financial infrastructure use cases. |
4 | 12 |
|
5 | 13 | ## Overview |
6 | 14 |
|
7 | | -XDC Network is an **enterprise-grade hybrid blockchain** that combines: |
8 | | - |
9 | | -- **Public Network**: Open, permissionless mainnet |
10 | | -- **Private Subnets**: Permissioned networks for enterprises |
11 | | -- **Interoperability**: Cross-chain communication between networks |
12 | | - |
13 | | -```mermaid |
14 | | -flowchart TB |
15 | | - subgraph "XDC Ecosystem" |
16 | | - subgraph "Public Layer" |
17 | | - A[XDC Mainnet] |
18 | | - B[108 Masternodes] |
19 | | - end |
20 | | - |
21 | | - subgraph "Private Layer" |
22 | | - C[Enterprise Subnet 1] |
23 | | - D[Enterprise Subnet 2] |
24 | | - end |
25 | | - |
26 | | - subgraph "Bridge Layer" |
27 | | - E[XDC Zero] |
28 | | - F[Checkpoint Contract] |
29 | | - end |
30 | | - end |
31 | | - |
32 | | - B --> A |
33 | | - C --> F |
34 | | - D --> F |
35 | | - F --> A |
36 | | - E --> A |
37 | | - E --> C |
38 | | - E --> D |
39 | | -``` |
| 15 | +The XDC architecture is built on four foundational principles: |
| 16 | + |
| 17 | +### 2.1 Hybrid (Public + Private) Architecture |
| 18 | + |
| 19 | +XDC enables coexistence of public and private states: |
| 20 | + |
| 21 | +- **Public Layer (Mainnet):** |
| 22 | + - Shared, immutable ledger |
| 23 | + - Global validator participation |
| 24 | + - Transparent transaction verification |
| 25 | +- **Private / Permissioned Layers (Subnets / Enterprise Networks):** |
| 26 | + - Restricted access networks for enterprises |
| 27 | + - Sensitive data remains private |
| 28 | + - Only hashed proofs or checkpoints are anchored to the public chain |
| 29 | + |
| 30 | +This ensures data privacy + auditability simultaneously, which is critical for regulated industries. |
| 31 | + |
| 32 | +### 2.2 EVM Compatibility Layer |
| 33 | + |
| 34 | +The XDC Network is a customized Ethereum-based protocol, enabling: |
| 35 | + |
| 36 | +- Smart contracts written in Solidity |
| 37 | +- Compatibility with: |
| 38 | + - Web3.js |
| 39 | + - Ethers.js |
| 40 | + - Existing Ethereum tooling |
| 41 | + |
| 42 | +This allows seamless migration of dApps and developer adoption. |
| 43 | + |
| 44 | +### 2.3 High-Performance Execution Layer |
| 45 | + |
| 46 | +The execution environment is optimized for: |
| 47 | + |
| 48 | +- ~2 second block time |
| 49 | +- Near-instant finality |
| 50 | +- 2000+ TPS throughput |
| 51 | +- Near-zero transaction fees (< $0.0001) |
| 52 | + |
| 53 | +This performance is achieved through: |
| 54 | + |
| 55 | +- Efficient validator coordination |
| 56 | +- Optimized block production |
| 57 | +- Lightweight infrastructure requirements |
| 58 | + |
| 59 | +### 2.4 Enterprise Interoperability Layer |
| 60 | + |
| 61 | +XDC is designed to integrate with: |
| 62 | + |
| 63 | +- ISO 20022 financial messaging systems |
| 64 | +- R3 Corda ecosystem |
| 65 | +- Traditional banking and trade systems |
| 66 | + |
| 67 | +This enables real-world financial system compatibility, not just isolated blockchain execution. |
| 68 | + |
| 69 | + |
40 | 70 |
|
41 | 71 | ## Network Layers |
42 | 72 |
|
@@ -80,16 +110,7 @@ XDC uses **XinFin Delegated Proof of Stake (XDPoS)** version 2.0: |
80 | 110 |
|
81 | 111 | ### Key Features |
82 | 112 |
|
83 | | -```mermaid |
84 | | -flowchart LR |
85 | | - A[XDPoS 2.0] --> B[BFT Finality] |
86 | | - A --> C[Forensic Monitoring] |
87 | | - A --> D[Penalty Mechanism] |
88 | | - |
89 | | - B --> E[Instant Finality] |
90 | | - C --> F[Detect Misbehavior] |
91 | | - D --> G[Slash Bad Actors] |
92 | | -``` |
| 113 | + |
93 | 114 |
|
94 | 115 | | Feature | Description | |
95 | 116 | |---------|-------------| |
@@ -161,23 +182,7 @@ const contract = new web3.eth.Contract(ABI, address); |
161 | 182 |
|
162 | 183 | ## Transaction Lifecycle |
163 | 184 |
|
164 | | -```mermaid |
165 | | -sequenceDiagram |
166 | | - participant User |
167 | | - participant Node |
168 | | - participant Mempool |
169 | | - participant Validator |
170 | | - participant Network |
171 | | - |
172 | | - User->>Node: Submit Transaction |
173 | | - Node->>Node: Validate Tx |
174 | | - Node->>Mempool: Add to Mempool |
175 | | - Validator->>Mempool: Select Transactions |
176 | | - Validator->>Validator: Create Block |
177 | | - Validator->>Network: Propose Block |
178 | | - Network->>Network: Validate & Sign |
179 | | - Network->>User: Transaction Confirmed (~2s) |
180 | | -``` |
| 185 | + |
181 | 186 |
|
182 | 187 | ### Transaction Finality |
183 | 188 |
|
|
0 commit comments