sarveshsharma101 / open-hackathon

Welcome to XinFin Open Hackathon Powered By XinFin

Open Hackathon

VISION

To innovate and replace existing non-efficient closed systems with more transparent, efficient system using blockchain.

NOTES

1. Participants are given complete freedom for choosing technology, programming languages etc. in the development of the application.
2. Problem statements are meant to be generic in order to give participants flexibility to work around.

Submission Guidelines

Submission Guidelines.

Open Problem Statements

Below we have listed the problem statements which are open to all. In order to participate, create a proposal in the format specified & make a pull request.

Prizes upto $10000 USD worth of XDC will be given if your solution is expected.

Task 1 : Change Proof of Work (PoW) Consensus in blockchain

Too much energy consumption makes PoW consensus non practical and not suitable for real world system. We need to find out other innovative consensus where transaction and network remains de-centralised but without much energy consumption. Restriction numbers of node make its more centralized while large number of nodes makes the system very slow. Many industry experts are trying out different consensus like DPoS. We need to find out innovative solution to replace PoW Consensus with other Consensus which gives more efficiency, speed and less energy consumption.

Consensus Related References

a. DPOS

• XDPOS.
• EOS.
• TRON.

b. Ethereum's Proof of Work ( ethash ).

c. Ethereum's Proof of Authority ( clique ).

d. Ethereum's Proof of Stake ( casper ).

e. Proof of Stake-Velocity ( POSV ).

f. Comparision ( POSV vs Clique ).

g. Smart contracts for PoS .

Blockchain Related References

a. XDC Nodes.

b. Ethereum.

c. Bitcoin.

Task 2 : Cross Blockchain Interoperability.

Various blockchain need to connect to each other to create more efficiency in system. Like Bitcoin, Ripple and IOTA. We need to Create Bridge between various blockchain.

Blockchain Interoperability References

a. Parity-Bridge.

b. BTCRelay.

Task 3 : XDCE Token Staking Function.

A staking mechanism requires users who offer compute power or other resources to the service takers in the ecosystem to put up a portion of their tokens in order to do so. If a user has no tokens to stake, but wants to support the network by providing resources they must purchase them. In exchange for staking their tokens and providing the service a financial reward is received. By forcing providers to take a financial risk you are weeding out bad actors.

Read more detailed requirement here

DAPPS Related References

1. Boilerplate DAPP.

2. Dapp tutorial.

Solidity Related References

1. Solidity docs.

For Hackathons

Below are the links to the specific problem statements for ongoing hackathons :

• SPIT Hackathon.
• Hackference.

Contacting Us

Join our Telegram Developer Group and put up your queries. We would love to answer your questions.

You can also join our Public Slack Group. Enter your E-mail ID and you will get an invite to our slack.