Open-source development is often controlled by a small group of people in order to prevent that anyone can just perform malicious changes to the code. But these people tend to (often times unintentionally) guide the development into a certain direction which they think would be the best. In some instances this control has led other people who would otherwise have contributed to a project to not contributing for various reasons. There have also been cases where bugs have been overseen since the people who were in control of either the development or the review of these changes were not experienced enough to do so in a reliable way, like the bug that made it into the stable release of the Linux kernel 4.8 or the famous Heartbleed bug in OpenSSL.
No single entity controls the code development. All contributions are acknowledged by the community.
Community-acknowledged code contributions are rewarded with tokens, leveraging novel crypto-economic protocols.
All development processes are vetted by the community through the democratic nature of voting.
dit supports all public and private git repositories
(e.g. GitHub, Gitlab, Bitbucket).
Developers rank their code crafting skills through peer-reviewing.
Apart from standard open-source licensing models (e.g. GPL, MIT), dit supports novel models based on Harberger licensing.
dit is the decentralized version of git. It uses, thanks to the blockchain, crypto-economic mechanisms to vote on code contributions while rewarding code proposers and validators with tokens.
dit brings democracy into the world of open-source software development. Proposed changes to the code will lead to a voting, where validators democratically decide on accepting or rejecting the contribution. dit implements knowledge-extractable voting, a novel crypto-economic protocol centered around the idea of tokenized knowledge over wealth.
Knowledge-extractable voting is based on the concept of proof-of-stake voting. Proposers stake ETH, thus initiating a new vote, where the validators will vet the proposal through a counter-stake. In addition to the stake and slash mechanism, knowledge tokens (KNW) are minted for good contributions or respectively burned for bad contributions. In contrast to ETH or regular ERC20 tokens, KNW tokens are labeled and non-tradable. One can only gain KNW tokens for a particular label, if one continuously contributes to projects in that knowledge domain. With KNW tokens, coders implement a proof-of-contribution, validated by the community, and establish as experts in their field. Coders build up a reputation in the open-source community and through their proven expertise have higher weights in governing a project.
Classic voting schemes (like "one man, one vote") are unable to produce trustworthy results on the blockchain, since they are prone to sybil attacks. On a public blockchain it's easy to create multiple identities and distribute the stake, hence classic proof-of-stake voting is biased by the rich. Knowledge-extractable voting aims to limit the power of the rich by introducing the KNW token which is independent of wealth and can only be obtained through continuous good contributions to the open-source community.