Status’s user profiles

User profiles derived from a user’s Ethereum wallet. This project is a work in progress. I’m about 30% of the way there.


User problem

Most users don’t actually own any of their data online. Once Instagram, Twitter or another of their favorite apps become unpopular (or crash, or ban them), they won’t be able to transfer their posts, friends, media or social capital from there anywhere else.

Business opportunity

Status is pivoting to become a community platform. Soon, users will be able to create Discord-like communities with native web3 functionality and permissions. Community owners will be able to create and airdrop ERC-20 tokens and NFT collections, and manage token gates across their community channels.

Because of the social nature of where the app is headed, overhauling the user profile is an important part of the new product focus.


  1. UI inspiration
  2. Competitor research — Traditionally, user profiles in chat clients are less detailed than they are in other social applications. If Slack is for work and Discord is for fun, why do both have essentially the same profile experience? A better Slack user profile would visualize your coworker’s place in your org chart, and Discord would benefit from allowing users to better customize their profiles. At Status, we want to be closer to Discord in functionality and flexibility. We also have something they don’t — wallet-derived profiles, which by nature contain data that users own. Showcasing their NFTs will be a point of pride for some users. We want to design a profile experience that accommodates that.
  3. Engineering requirements — What should we prioritize ahead of launch, given that there’s also significant work being done on Status’s wallet application itself. While we’d like to include liquidity pool positions, for example, we most likely won’t do so in the V1 because the wallet team is actively working on it.


Because Status is a social app, a user will want to see more than just another user’s wallet address — they will want to know something about their personality.

Because of this, we should allow users to showcase wallet assets and include a bio, social links, and so on.


  • DAOs looking for software to support their members.
  • Companies for whom operating a token or NFT collection is a necessity for their operations.
  • Groups of friends and other casual users.

Success metrics

Sustained use among Status users:

  • How many users customize their assets showcase? (Status collects zero user data. We can run surveys, however.)


I used Status’s design system for the majority of my work, which allows me to quickly try out ideas: should I use tabs to separate ERC-20 tokens from NFTs or just have a long list? Should I show assets using a card grid or a list?

Earliest designs


New components

For this project, I’ve created new components where needed, primarily: designs for social links (to Twitter, Github, YouTube, a personal site, etc.), and ERC-20 and NFT thumbnails.

I know that these will change while I’m working on the profile design, but making them early on saves a lot of time mid-project, when one small change to a card style needs to be reflected across many screens.


Next steps

  1. Stress test and define rules:
    • Set the user bio character limit
    • Decide what social links to support
    • See the corner cases — what happens when someone wants to showcase dozens of NFTs or tokens?
  2. Iron out privacy flows:
    • Status has worked hard to preserve user privacy — those in the chat app don’t automatically reveal their wallet address, and vice versa. How can we allow users to doxx their wallet under the right circumstances, and to the people they want?
    • Status’s HD wallet-as-a-profile also generates an array of public keys — a key for your first wallet, a key for your chat profile, and a new emojihash that helps identify you in a more legible way than long keys. How do we surface these to those who want them, and what circumstances do users want to see them?
    • How to give the user full control over what’s visible, to whom, and where.

Some of this work belongs to the realm of user settings, which I’ve also redesigned over the last few months, adding a live preview, a “View as” feature, and granular config on individual assets to allow users to only show assets to the people they want to share that information with.