TrustPOAP
Anonymous Verified Reviews with Sybil and Spam protection for POAP events
Created on 18th September 2022
•
TrustPOAP
Anonymous Verified Reviews with Sybil and Spam protection for POAP events
The problem TrustPOAP solves
Currently reviews are vulnerable to sybil attacks and untrustworthiness, they can be abused to aritificially manipulate ratings and make brands/products/events more attractive. People are more interested in reviews of users who actually watched/purchased/went to an event.
We all know how POAPs are loved within the ethereum community, and obvisously, we are not an exception. They are a great use case of NFTs for non-financial applications.
With that in mind, we believe they are the perfect primitive to benefit from Anonymous Verified Reviews. Why:
- POAPs ensures proof of attendance, therefore -> reviewer = attendee => actual valuable review
To mitigate Sybil Attacks, we chose to use humanbound.xyz, which provides a unique proof of humanhood, enabling TrustPOAP to:
- Ensure a review is made by an actual human
Therefore, with POAPs + humanbound.xyz, trustPOAP can make sure a reviewer:
- ✅ Is an actual attendee
- ✅ Is a unique human
- ✅ Can write only one review
- ✅ Preserves user anonymity
- ✅ Is censorship resistent
Review content is saved on IPFS 🌐
Review Hashes are immutable and submitted on the Blockchain 🔒
To create a review a user needs to:
1 - Participate at an event 💃
2 - Receive a POAP from it
3 - Be a Human ❌👽 (have a humanbound token from humanbound.xyz)
4 - Cannot have previously submitted a review for this event (the transaction will fail 😉)
5 - That's it 🎉
Challenges we ran into
We ran into time issues, mainly because we got inspired and got this idea on the hackathon itself, starting everything from scratch.
We also had difficulties finding plugs and extensions cables 😭
Unfortunately due to the time constraint we took some workarounds on the contract side; the humanbound token is verified both onchain and on the frontend, while POAP ownership verification is done solely on the frontend -> We would have to deploy the contracts on GNOSIS chain to verify the aforementioned ownership, but started with Polygon 🤦
Next Steps would include:
- Adding cross-chain oracles to verify any POAP issued anywhere
- Creating a more user-friendly way to search for events
- Adding decentralized review curation + voting
- IPFS caching and quality of life improvements (speed mostly)
- CryptoEconomics / Token Engineering
Technologies used
