Web3Auth

Concept With the advent of AI, deep-fakes and the rise of social media regimes content ownership and appropriaion has become a hurdle for every creator. There is no verifiable and concrete way to prove content ownership in the web2 ecosystem. This has led to most of the current solutions being claim-based without any actual way to verify one's ownership of the underlying or to verify his claim. This has led to misappropriation of content and missing value accrual for the creator due to a flawed system. We propose a social verification protocol built to be trustless and achieve true value accrual for creators. A social platform where creators are judged by their peers who can attest to the verification/authenticity of content. With built-in dispute creation and resolution mechanisms to combat fraudulent content verification and keep validators in line. Platform Mechanism: Creators: Any user can put up content of any kind up for verification this process takes a small fee and a minimum timelock of 24 hours for any disputes to emerge without the need to put up collateral to challenge the authenticity of the content. Creators pay a small fee for every content verified this is used as incentive for Validators. Challenger: A Challenger is any user who disputes the authenticity of any verified or unverified content by either claiming it as his own or a misappropriation of another content. To create a dispute a challenger needs to put up a collateral equal to the verification fee. Challengers are granted ownership over the content or a form of economic incentive on a dispute ruled in their favour Validators: Validators are users who are economically incentivized with a portion of the fees collected from challengers and creators. A validator would need to put up a bond of 100 ETH which is slashed when a dispute is ruled in favour of the challenger where the validator was in support of verifying a piece of content.

Links

• https://github.com/hridyansh-khatri/eth-india

Because of the scope of the project and the various systems which needed to be implemented to bring it into fruition. This was an ambitious project for a small team of 2 developers. Yet we tried our best to implement complete working modules into the system. We built and tested Contracts to handle verification using on-chain signatures as attestation to any content. The deployment to Scroll and verification were big step due to the contracts only being able to be compiled using --via-ir pipeline they required a secondary implementation in Hardhat to get verified. Safe SDK integration for social login and AA was left midway because they are not available on Scroll Testnet which led to a lot of lost developer hours. Subgraph Integration and development with IPFS has always been clunky with custom/nested structures using too much boilerplate code. Frontend development took a lot of time and hours on bugs that were to be abandoned this could have been avoided with better planning. Yet this was a learning experience and we hope that you see the project for the vision that we had.