ToteDAO
ZK-proofed products reviews. Get paid as a verified user. Powered by IOME.AI and Polygon.
Created on 28th August 2022
•
ToteDAO
ZK-proofed products reviews. Get paid as a verified user. Powered by IOME.AI and Polygon.
The problem ToteDAO solves
TL;DR: Verifiable good quality demography-specific reviews must be a basic access right to prospects, customers and product companies. This seems to be an open problem.
Problem:
-
e-Commerce has been one of the largest success stories on the internet for the past few decades
-
Today’s purchase experience lacks “touch-and-feel”. Users now rely more on customer reviews
-
Companies too rely on these reviews to improvise products in their future batches/cycles
-
We’re pestered by review farms and irrelevant feedback out of context
-
Gartner, G2 et. al. have tried to fix these issues, but lack decentralizaion in their ecosystem
Solution:
-
Build a DAO for genuine reviews by targeted demographic users verified by KYC-Ed ZK-proof wallet
-
PI is hidden away by the power of ZK proofs on the KYC data
-
Prospects and companies source honest reviews from specific demography they favour
-
DAO members identify themselves to a demography and provide genuine reviews for bounty/rewards
Employ AI to track common keywords and bucket them into weighted sentiments
Challenges we ran into
Originally, we planned to use the following tech stack:
Matic / Polygon: The easiest ledger of choice today
Alchemy: Easiest guided access to Polygon Smart Contract development
10M3: Zk-proofed KYC-ed private BIP44 wallet, powered by MOI
Web3.Storage: Storing review data and related datasets
Spheron Protocol: To access Polygon Network
Covalent API: To query Polygon Network and apply NLP on review datasets
EPNS: To alert users on status of actions
Arcana Network: To share product insights with companies in a permissible manner
Router Protocol: Cross-chain settlements of bounties
React.js: Front-end web app for DAO activities
Node.js: For some middleware activities
Solidity: Not-so-smart contracts, duh!
We ended up only using the following due to proper tooling and support:
- Polygon,
- Alchemy
- IOME on MOI,
- Web3.storage,
- Sentimental Analysis using NLP
We could not use the following:
- Covalent API (Our NLP model still hasn't progressed to a stage where we can use Blockchain state for sentinment analysis)
- EPNS (Did not get enough support to setup a channel on Polygon Mumbai and had to limit scope)