would

XDC Network

<a href="https://x.com/XDCNetwork" rel="noopener noreferrer nofollow">@XDCNetwork</a> has built its subnet architecture around a core tension in enterprise blockchain: institutions need private ledgers, but they also want the security guarantees of a public chain. The subnet model is its answer.
<h2 id="a-private-chain-wholly-owned-by-the-customer">A Private Chain, Wholly Owned by the Customer</h2>
An XDC subnet is, in the words of the network's own documentation, <cite>"a sovereign, permissioned, and high-performing blockchain wholly owned by the customer."</cite><cite>It runs on XDC2.0, the consensus engine built in-house for XDC and deployed to the mainnet as well,</cite> meaning the enterprise environment and the public network share the same underlying protocol.
<cite>XDC Network is an enterprise-focused, EVM-compatible Layer 1 blockchain designed to digitize global trade finance and tokenize real-world assets.</cite><cite>Enterprise customers demand privacy, meaning their transactions and ledger should not be disclosed to the public, which prohibits them from directly submitting transactions to XDC mainnet.</cite> The subnet design addresses that constraint directly.
<h2 id="how-the-checkpointing-mechanism-works">How the Checkpointing Mechanism Works</h2>
The architecture relies on three interlocking components. <cite>These are: a subnet driven by the XDC2.0 consensus engine with configurations tailored for the customer; a relayer program that checkpoints critical consensus data of the subnet to the XDC mainnet; and a smart contract on the XDC mainnet that verifies and records those checkpoints.</cite>
<cite>The relayer periodically calls the Checkpoint Smart Contract to update the subnet status, by default every two minutes.</cite> Critically, what crosses over is minimal. <cite>Only block header information is checkpointed to the XDC mainnet, enhancing data protection,</cite> while the underlying transaction data never appears on the public chain.
<cite>The Checkpoint Smart Contract deployed to the parent chain provides enhanced security by recording block hashes from the subnet, ensuring that subnet blocks cannot be tampered with while protecting and concealing the underlying subnet data.</cite> That tamper-evidence is the crux of the model: any attempt to quietly rewrite subnet history would produce a mismatch against the snapshots already recorded on mainnet.
<cite>XDC's subnet-mainnet checkpointing is light-client based, meaning the relayer cannot deceive the system. This is considered more secure than a common bridge, which relies on a trusted third party.</cite>
For regulated industries, <cite>the hybrid architecture enables selective data disclosure: enterprises can keep customer information on private subnets while anchoring transaction proofs to the public mainnet, a design that satisfies both privacy regulations like GDPR and transparency requirements like audit trails.</cite>
Sources: <a href="https://docs.xdc.network/subnet/overview/" rel="noopener noreferrer nofollow">XDC Network Official Subnet Documentation</a> <a href="https://xdc.org/solutions/xdc-subnets" rel="noopener noreferrer nofollow">XDC Subnets Overview, XDC.org</a> <a href="https://xinfin.org/xdc-subnet" rel="noopener noreferrer nofollow">XDC Subnet Architecture, XinFin.org</a>

XDC subnets keep enterprise transactions private while anchoring to the public chain

Table of Contents

BSCN

Other articles published on Aug 27, 2026

Join our free newsletter for daily crypto updates!