This post calls for proposals to audit the forthcoming XDC2.0 consensus upgrade. Deadline: 31/Sep/2023, anywhere in the earth.
XDC2.0 is a significant backward-incompatible upgrade of the XDC network. It will create a hard fork that requires all the network participants to comply. This upgrade will change the consensus engine of the XDC network from XDPoS1.0, a delegated proof-stake (DPoS) plus longest-chain mechanism, to XDPoS2.0, a DPoS mechanism with the optimal Byzantine-fault-tolerance (BFT) based on the chained-Hotstuff algorithm.
The upgrade is led by Professor Pramod Viswanath from Princeton University and his protocol engineering team. This upgrade will enhance the security level of XDC network against malicious master nodes without compromising the network’s high performance (e.g., high transaction throughput) and applications (e.g., all the EVM-compatible smart contract-based applications). It will also broaden the adoption of the XDC network due to the new features it brings in, such as forensics and enterprise private subnet.
The upgrade has been deployed on the XDC devnet since June 2023 and has worked properly without any issues for 2 months – until the protocol team shut it down and redeployed it to incorporate recent upgrades from the community.
Before applying XDC2.0 to the XDC mainnet, at least two requirements should be met:
- The upgrade is deployed to the XDC Apothem testnet and works without issues for at least three months.
- The upgrade passes the audit from at least one highly professional and reputable audit team.
The results of the deployment and audit will be published for the community to make the final decision.
- Object: all the code developed between V1.1.0 and V1.4.8 under the XDPoSChain repo
Goal: to provide, after neccesary iterations of code modifications, an assessment on whether XDC2.0 is suitable to be deployed to the XDC mainnet or not. Here, by “suitable”, we mean:
- The implementation of the algorithm meets the desired BFT security (including safety and liveness) properties.
- The code is high-quality and robust, with all edge cases covered, so it will not cause network failures or enable security-threatening attacks.
Supports from the protocol team:
- Provide all the related codes and documentation
- Guide deployment and testing
- Answer technical questions and participate in technical discussions
- Evaluate code revision suggestions and implement the changes
The successful audit team should:
- be highly reputable in the industry
- have deep expertise in auditing consensus protocols with a provable track record
- submit a comprehensive proposal with:
- clearly defined scope of work
- clearly explained methodology
- a good estimate of the workforce the team will bring in
- a good estimate of the timeline, or a convincing justification if an estimate cannot be given
- a comprehensive fee scheme
Please submit your proposal by either replying to this post with your proposal in text, or, if your proposal is a file, replying to this post with a link to your file.
Deadline: 31/Sep/2023, anywhere in the earth.