go-ethereum/README.md
Daniel Liu 1472f3b1eb
docs: add document for JSONRPC API (#1027)
* docs: add document for module XDPoS

* docs: add document for module admin

* docs: add document for module debug

* docs: add document for module eth

* docs: add document for module miner

* docs: add document for module net

* docs: add document for module personal

* docs: add document for module rpc

* docs: remove module shh

* docs: add document for module txpool
2025-05-19 15:30:52 +08:00

69 lines
2.7 KiB
Markdown

# XDPoSChain
<p align="center">
<img src="./assets/images/xinfin-logo.png" />
</p>
<p align="center">
XinFin XDPoSchain<br/>
Enterprise ready hybrid blockchain for global trade and finance
</p>
<br/>
## XinFin Hybrid Blockchain
XinFin Hybrid Blockchain is an Enterprise ready Blockchain for global trade and finance
Visit: [XinFin.org](https://xinfin.org)
Contribute: [Developer Docs](https://docs.xinfin.org)
## XinFin Network XDPoS is community driven project to achieve the following
- XinFin DPOS (XDPoS) consensus that selects 108 set of Masternodes to achieve a high throughput Energy efficient consensus with instant block finality
- KYC Enforcement on Masternodes for Enterprise Adoption and compliance
- Ability to port/relay limited set of data and transactions from privacy channels to public channel
- Interoperability between applications hosted on Private Blockchains like Corda, Hyperledger, Quorum(JP Morgan) using relayers to XinFin Network
- Customer Centric and consortium driven Governance to equally benefit the validators as well as providing comfort for large scale enterprise applications to be hosted on the Network. This achieves
- Rapid Upgradability
- DApps Standardisation for rapid commercialisation
- Compliance with major global jurisdictions.
### KYC for masternodes
#### OVERVIEW
To add a layer of KYC for masternodes in the current system and a sense of ownership amongst the masternodes hence tying such a cluster of masternodes to physical entity which can held accountable for its actions.
#### Design
We established a bidirectional connection between a candidate and its owner inorder to retrieve a candidate belonging to a specific owner & vice versa.
All the masternodes are recognized by the KYC of their owners and hence are considered as a single verified entity ( for eg. while voting for invalid KYC, only one vote is considered per such cluster )
The contract is very strict in handing out penalty for invalid KYC, it results loss of all funds invested in all of its candidates.
For eg. say A proposes condidates B,C,D by paying for its proposal cost.
If at a later stage if some predecided amount of owners ( investors ) vote that a KYC for a A is invalid then A & all of its candidates (B,C,D) will lose their position & all their funds will be lost ( will remain with contract wallet ).
### Documents
[Document](./docs/README.md)
### For developers
#### Continues integration & delivery
See <https://github.com/XinFinOrg/XDPoSChain/tree/dev-upgrade/cicd>
### To contribute
Simple create a pull request along with proper reasoning, we'll get back to you.
Our Channels : [Telegram Developer Group](https://t.me/XinFinDevelopers) or [XDC.Dev](https://xdc.dev)