Privacy
Limit access to authorized participants and keep application transactions within a permissioned environment.
Powered by XDC Subnet
Privacy-focused enterprise networks
Keep application transactions inside a network you control, with public checkpoints for integrity verification.
On this page
A permissioned network built around your requirements
XDC Subnet enables a customer-owned network with configurable validators, governance and access controls. Organizations can run private applications while retaining the ability to anchor consensus data to XDC Mainnet.
The application’s private transaction records remain within its permissioned environment. The deployment determines who can participate, access data and operate infrastructure.
Privacy, control, security & scale
Sovereignty
Control the network configuration, participating validators, access rules and data governance.
Security
Use the XDC 2.0 consensus design, monitoring and checkpoint verification within the deployment’s operating assumptions.
Scalability
Create infrastructure for an application’s workload and adjust capacity as requirements evolve.
Owned by you, anchored to mainnet
Customer subnet
An XDC 2.0 consensus engine runs with system settings, validators, governance and access rules chosen for the deployment.
Relayer
A relayer periodically submits critical consensus data from the subnet to XDC Mainnet.
Mainnet checkpoint contract
A smart contract verifies and records the submitted checkpoints, creating a public integrity reference.
Wallet APIs
Wallet interfaces connect users and applications to the subnet’s transaction workflows.
Explorer and forensic monitoring
Network tools provide transaction visibility and consensus monitoring within the deployment’s access policy.
Private transactions, public integrity
A subnet can maintain its own validators and permissioned application state. A relayer sends consensus checkpoints to a smart contract on XDC Mainnet, producing a public record for integrity checks without publishing the underlying private transactions.
XDC Zero handles communication between a subnet and XDC Mainnet. Endpoint contracts send and receive messages, a relayer transports the payload, and an oracle provides block-header data for validation. Applications can build data exchange and asset-transfer workflows on these components.
Checkpointing and cross-chain execution solve different problems. Each deployment must define its verification rules, operator responsibilities and failure handling. Proposed XIM research extends this model toward heterogeneous ledgers and authenticated financial gateways; it is not a production service.
For data-sensitive organizations
Private blockchain networks
Create an application network with confidential records, defined membership and organization-specific rules.
Cross-chain transactions
Coordinate messages and asset-transfer workflows between networks using an explicitly chosen verification policy.
Supply-chain security
Track the movement and provenance of goods and materials with a shared transaction record.
Decentralized applications
Deploy smart-contract applications on infrastructure configured for their security, access and scaling requirements.
Operational flexibility
A dedicated subnet can support application-specific capacity, access policies and cost models. Privacy and security depend on configuration, authorized participants and operational controls.
Guides & documentation
Subnet setup guides
Docker setup and introductory videos.
Gasless subnet whitepaper
September 2024 technical proposal by Mohuya Chakraborty and Atul Khekade.
Subnet architecture
Components and design in the official network documentation.
XDC Zero
Endpoint, relayer and oracle messaging components.
XDC developer forum
Ask technical questions and share implementation experience.
Questions about privacy networks
Are subnet transactions private?
Subnets can restrict access to authorized users. Application transactions remain in the permissioned environment according to the deployment’s access rules.
What is published to XDC Mainnet?
The relayer submits consensus checkpoint data to a mainnet contract. This creates an integrity reference without publishing the underlying private transactions.
Who owns and operates the network?
The customer controls the subnet, relayer, checkpoint contract and wallet APIs, and defines validators, governance and access rules.
How is the network secured?
The subnet uses the XDC 2.0 consensus engine, while a mainnet smart contract verifies and records checkpoints. Operational security remains a deployment responsibility.
Can it connect to other networks?
XDC Zero supports communication between a subnet and XDC Mainnet. XIM research proposes connections to additional blockchains, institutional ledgers and financial gateways.
How do I get started?
Follow the Docker setup guide and video tutorials, or contact the team to discuss a subnet deployment.
Read moreCreate your privacy network
Discuss your requirements
Get assistance with an XDC Subnet deployment.
Developer Telegram
Join the XDC developer community.
SOURCE & CONTEXT
Content carried forward from XinFin’s public website and linked primary sources. Historical material is identified where applicable.
Source record Editorial methodology