Process / HoneyPot.Money
Gitcoin's founder, Kevin Owocki, partnered with me to create HoneyPot.Money — a platform that incentivizes the creation of digital identities to counter sybil attacks that harm the blockchain.
Product Design, Visual Design, Prototyping (HTML, CSS, JS)
It might sound complex but you're probably aware of events similar to a sybil attack: rigged giveaways where users submit multiple entries by using multiple emails, online voting systems with questionable voter identities, and even questionable social media engagement from users that don't seem to be operated by real people.
We designed HoneyPot.Money to integrate with BrightID which is a privacy-first social identity network allowing users to be able to authenticate proof of identity without having to share their personal information.
The claim flow is designed to be pretty straightforward since the identity authentication process happens off-platform via the BrightID integration.
When working on open-source + public goods projects at Gitcoin, there are times where there's no Developer readily available to collaborate with.
I prepared a Github repository as the design documentation for developer hand-off since design and development might have a significant gap in timeline.
As the sole Designer for the project, I also took on illustration and branding. After some quick rough drafts, I met with Kevin to walk him through my progress and assumptions and we ended up choosing a storybook-like approach to the Visual Design of the platform.
During the design phase, I proposed an idea where some of the elements in the UI will be randomly generated and only appear at certain local machine time to simulate day and night.
To push the design further, I also added animated svg elements that randomly spawn and add more depth to each composition.
“I proposed an idea where some of the elements in the UI will be randomly generated and only appear at certain times based on the user's local machine time to simulate day and night.”
As there was still no available developer to collaborate with after finishing the designs, I spent some time creating prototypes of the different claim scenarios.
I completed this Github repository so incoming developers can also easily fork the code and use it as a guide or even as a starting point for development even if I'm not available to walk them through my designs.
As a result, Developers were able to easily fork the repository and take a stab at the project. They were able to connect the backend with the designs I coded which shaved some time off front-end development.
Potential additional learning features about sybil attacks and sybil resistance can be introduced to the project, taking advantage of the storybook-like illustrations and fun approach which can be conducive to teaching complex concepts in a fun way.
I would love to get the chance to explore this idea further and make the experience more robust not just for users familiar with Web3 but also new users interested in taking control of their private information.
