Sadaiv C.I. (सदैव)

A continuous integration pipeline that backs up your GitHub contributions on the Decentralized Network without you worrying about it.

The problem Sadaiv C.I. (सदैव) solves


Today, most developer communities and organizations (including DAOs) use GitHub to host their projects. GitHub is a centralized organization providing limited support for web3 native values; hence, the data could be lost.

Here's an example of Tornado Cash:

Tornado Casȟ

To resolve, this issue there are tons of other projects built on the web3 stack that provides an alternative UI and architecture to host projects. But guess what people still don't use them. Even Tornado Cash continued to use Github after that happened.

The reason is that the features and comfort GitHub (or web2 solutions) provide is incomparable to the new immature emerging solutions.

Our Idea

Therefore, we thought to create a continuous integration to store the projects on GitHub to a decentralized network like Filecoin using Web3.Storage. This basically backs up the project onto the decentralized network every time a new commit is pushed to the branch. And the source of truth is moved from Github to spread across the network.

Additionally, we are indexing the CIDs with important metadata like contributor, commit message, etc. that will help in:

  • Having access to the full Github tree and contributions history
  • Providing on-chain identity to the developers contributing to the public repositories (Future Prospect)

Therefore, with Sadaiv CI developers can work with the comfort of web2 solutions like GitHub yet remain to ensure the ownership of their project and contributions is not in the wrong hands.

Challenges we ran into

We had to build 5 key components to achieve the desired user experience:

  • GitHub action that automatically runs to backup content on Filecoin using web3.storage
  • Writing a smart contract to keep track of code changes and maintain repository history
  • Creating a server that signs and sends the transactions to avoid user hassle and provide a smooth experience
  • Building a sub-graph so that it becomes seamless to run queries
  • Keeping the onboarding journey as easy as possible and less efforts required from developers

The toughest part was to build all this from scratch in just 36 hours, but we did it!!