Context

The Challenge

In Web3, where privacy and anonymity are essential value propositions, how do we distinguish good users from bad users, without compromising the privacy of our users?

Coinlist is a $1B crypto platform that helps the world’s most promising token offerings (eg. Solana) get listed for the public to participate in, averaging massive returns on investment. It’s similar to enabling retail investors to buy pre-IPO shares of a company

My Responsibilities

I was given 3 months to build a zero-to-one feature, that allowed users to connect their non-custodial wallet to Coinlist.

Given the sensitivity and impact of this product, I lead design with a wide range of stakeholders, from our CEO, to Director of Engineering, Product, Data and legal and a team of 4 engineers.

Problem & Solution

Given the exceptional returns of investing in Coinlist’s vetted projects, more than 10 million users have flocked to Coinlist. However, getting chosen to participate in a token sale becomes highly competitive.

For example, 100,000 users may sign up for 20,000 spots.

A 3 Sided Problem

After internal and external research, we realized it came down to problems for our Users, Token Issuers, and Coinlist.

• High-quality users can’t get access to token sales: Crypto is filled with bad actors such as bots or short-term investors. They “steal” the slots of good users.
• Token Issuers complained about users quickly selling their tokens for a quick profit after their tokens were listed, negatively impacting the performance of their tokens.
• Coinlist’s business was threatened by not being able to provide high quality users to token issuers. If our users were not high quality, fewer token issuers would come to us, negatively impacting our revenue and brand in the long term.

Hypothesis & Solution

We believed we could help both users and token issuers, by offering users a way to share their on-chain activity, to verify positive behavior, in exchange for increasing their chances of participating in a token sale.

Design Process

Starting with Flows & Prototypes

I created a user flow that outlined the various entry points into this modal and covered the scope of the MVP. It was helpful it clarifying what we were NOT building too.