ixo Keysafe • Shipped 2020

Blockchain Case Study: ixo Keysafe browser extension

Role

Product Design Lead

Year

2020

Methods

Stakeholder, 3rd party supplier and developer collaboration
User interviews
Persona creation
User journey mapping
Wireframe and interactive prototype
Style guide and design system
User interface design
Quality assurance testing

Overview

The ixo Keysafe browser extension is your connection to the ixo blockchain. It allows you to manage your profile and sign transactions on ixo projects. View my case study, Blockchain case study: ixo — the new world of impact for context.

Objective: create a secure identity vault

How do we keep your identity secure and prevent fraud on the ixo.world platform?

It is a secure identity vault that stores your identity with public and private keys.

ixo does not store any personal data (not even email addresses) and will never share personal information with any other party without the member’s consent.

The flow of public data on the ixo.world network.

The flow of public data on the ixo.world network.

My role

As Product Design Lead, I partnered closely with technical lead and developer to design the experience of the ixo Keysafe. I also assisted the Quality Assurance team with testing and logging errors.


Research

Step 1: Research

Being new to Web3 standards I familiarized myself with the new and unique UX design patterns around self-sovereign identify verification.

Decentralized identifiers represent an exciting new breakthrough in the field of identity management. They can be thought of as a vital component in a new layer of decentralized identity, which employs cryptography and public key infrastructure to provide a more secure way of using the internet.

An example of what a DID Document could look like.

An example of what a DID Document could look like.

Step 2: Dissection

In order to make it easy for people to register with ixo’s network, we forked the crypto wallet, MetaMask, and built the ixo Keysafe.

Keeping the existing MetaMask Web3 register and login patterns, I customized the flows to now cryptographically sign ixo project documents instead of transactions.

Understanding users

The Keysafe Persona

The ixo customer is required to create their own DID via the ixo Keysafe to interact with the ixo.world platform.

  • Lara requires Keysafe to successfully create a project on ixo.world.
  • To invest and generate funds on a project Mike requires Keysafe.
  • Lauren uses Keysafe to cryptographically sign her proof of impact.
  • Graham uses Keysafe to approve Lauren’s proof of impact thereby successfully completing a claim on Lara’s project.
The ixo persona types.

The ixo persona types.


Final designs

Your key to the world of ixo

Once installed, a user must set up Keysafe for the first time. This setup process will generate a DID for the customer.

Registration process — Web3 replaces email recovery with the secret backup phrase verification.

Registration process — Web3 replaces email recovery with the secret backup phrase verification.

Create verified impact projects

Verifiably prove that your social impact initiative contributions are being utilised correctly.

Securely sign your impact project to the ixo blockchain as a Project Owner. This means that no information or claims can be tampered with and skew final impact data.

Project details being cryptographically signed onto the ixo blockchain.

Project details being cryptographically signed onto the ixo blockchain.

Cryptographically sign all documents

As a Service Provider and an Evaluator, you cryptographically sign all transactions with the ixo Keysafe. These transactions include actions such as submitting and evaluating claims. These claim actions are then immutable proof of an impact on a project.

An example of a Service Provider submitting a claim on the ixo Keysafe.

An example of a Service Provider submitting a claim on the ixo Keysafe.

Reflection

What made the project challenging

  • The Web3 backup phrase: these words help you recover your account instead of email. This was a behaviour Web2 users are not accustomed to.
  • I had to work closely with the marketing team to communicate and educate users on new and unusual UX patterns and practices.
  • The last iteration included payment methods using crypto and fiat, prompting various different user flows depending on your payment choice.

What made the project cool

  • ❤️ Designing for Web3.
  • 🦊 Collaborating with Consensys on the MetaMask forking.
  • 🦸 Targeted user testing: A Telegram channel was created for interested customers that are willing to assist with testing. This provided us with valuable feedback to iterate rapidly on bugs and UX improvements.
  • 👍 Designing and testing for a new medium.

Available for download on the Chrome web store.


Next

Real-time reporting from conflict areas

BRAC • Shipped 2015