XDC’s EVM-compatible blockchain has the speed, security and the trustless composition to support a series of DeFi applications and enable a future where financial markets can run decentrally, globally, 24/7 with no single central party having any more control or access in this economy than any other.
1,250x faster than Ethereum
Ethereum currently averages just 7-12 TPS.
Costs less compared to BTC ($15) and ETH ($10)
Source of funding.
10M x more efficient than BTC
This power output is comparable to the yearly average output of a handful of single family homes.
How is the XDC Network Secured?
XDC Network relies on a delegated proof-of-stake mechanism, titled XinFin Delegated Proof of Stake (XDPoS) to reach consensus. This unique consensus mechanism ensures the XDC Network uses virtually zero energy and is highly resistant to spamming.
A proposed forensics-enabled consensus mechanism (termed XDC 2.0) is built upon an advanced BFT consensus protocol and will guarantee absolute zero forking in the finalized blockchain as long as the ratio of adversarial masternodes in each epoch does not exceed one-third. The block time will remain at two seconds with the adoption of XDC 2.0, but, most importantly, after the adoption of XDC 2.0 confirmation is finalization, meaning transactions will be finalized six seconds after their inclusion in a block.
XDC 2.0 builds off of the original XDPoS consensus mechanism by introducing a BFT committee, which is a set of masternodes selected using a deterministic and verifiable algorithm at the beginning of each epoch. The nodes aim to reach consensus using the advanced BFT protocol (Chained Hotstuff) and have the ability to identify malicious actors with cryptographically provable forensic evidence.
In the unlikely event the ratio of adversarial masternodes exceeds one-third during an epoch, those adversarial masternodes will have to sign and certify certain messages that will be embedded into the blockchain in order to violate the safety of the network. These embedded messages can be accessed through on-chain forensics monitoring and used as irrefutable evidence of misbehavior.
The holistic integration of accountability and forensics within the blockchain positions XDC Network as a uniquely secure and well-monitored blockchain protocol.
WATCH: Dr. Fisher Yu provides a status update on XDC 2.0
The XDC community has adopted numerous token standards to ensure the composability of smart contracts and dApps and that the tokens are interoperable across projects built on the XDC Network. The XDC Tokens work with the following standards:
XRC20 Is the technical standard for fungible tokens and is used for token implementation in the majority of smart contracts on the XDC Network. XRC20 tokens can digitally represent virtually anything and are widely accepted by wallets and exchanges.
Non-fungible Tokens (NFTs) have gained popularity in the collectables, art, gaming, and music industry to show ownership of unique items. XRC721 is the standard used to build NFTs on the XDC Network and it defines the minimum requirements a smart contract must meet for NFTs to be owned, managed, and traded.
XRC1155 is a multi-standard token combining XRC20 and XRC721 standards that allow for multiple tokens to be generated within a single contract. The XRC1155 is a single smart contract that can represent and govern an infinite number of tokens.
Learn more about the XIP Process
XDC Network Improvement Proposal (XIP)
XIPs are used by the XDC Community to propose new features on the network, collect technical input on an issue, and document design decisions that have gone into the network. They are derived from Ethereum Improvement Proposals (EIPs), which are in turn derived heavily from Bitcoin Improvement Proposals (BIPs), which were derived from Python Enhancement Proposals (PEPs). These proposals contribute to the open source economy facilitated on the network and enables developers and builders to contribute to network and broader industry standardization.
XDC Network Improvement Proposals (XIPs) describe standards for the XDC platform, including core protocol specifications, client APIs, and contract standards. Network upgrades are discussed separately.
Anyone can submit an XIP, but the technical bar is high. XIP editors ensure proper formatting and style guidelines are followed. Before writing a formal XIP, an idea should be proposed on the developer forum and vetted by the community. Once it is vetted, an XIP can be written in GitHub for review by all interested parties, editors, developers and the XDC community.
Standards Track XIP