Rupam Gumber
Back to home

Letting banks bring their own vault

Xalts was holding the keys to its clients' digital assets, and banks didn't love that. I designed how an institution connects its own Fireblocks custody instead, and how it sees every wallet once it does.

RoleProduct Design Intern
Team1 PM, 2 designers, 1 researcher, developers
Timeline3 weeks, May–Jul '24
PlatformWeb

A 30-second primer

Xalts, backed by Accel and Citi Ventures, helps banks tokenise real assets like bonds, bank guarantees and treasury bills. Those assets live on blockchains like Polygon and Avalanche, inside wallets.

Whoever holds the keys to those wallets is the custodian. That one word is what this project is about.

What

Tokenising financial assets: bonds, bank guarantees, treasury bills, currencies.

How

Automated workflows that move assets through each step.

Why

Many parties can collaborate, move faster, own and transfer assets digitally, and keep data where it must live.

The problem

Without an outside custodian, Xalts held every key. Banks weren't comfortable with that, and Xalts didn't want the risk either.

Being a custodian comes with heavy security and compliance duties. Institutions wanted a provider they already trusted, like Fireblocks, to carry them.

What we heard

Most institutions wanted to bring their own custody provider.
Many already had a Fireblocks workspace, or would happily pay for one.
Some used other providers, like Blockdaemon and Taurus.
Whatever the setup, every wallet had to be visible inside Xalts.

Who I designed for

Each organisation has one root user, its admin, and in practice that's someone from IT. I gathered user stories from our founders and PMs, who talked to these clients directly.

Rajesh, 30IT team, financial institution · root user

Eight years setting up and maintaining systems at financial institutions, where everything must pass security and compliance reviews. Technical and careful, but not necessarily fluent in crypto terms.

Story 1 · Root user Mine

Give the platform a Fireblocks workspace, so it can create wallets and sign on my behalf.

Story 2 · Root user Mine

See every wallet set up at organisation and user level, and the wallets behind each network.

Story 3 · Root user Ashmita

For each on-chain transaction, see which wallets signed it and what kind of transaction it was.

Story 4 · Normal user Ashmita

See only the details of my own wallets.

Getting the requirements right

Custody is unforgiving, so I worked through the technical requirements with the Fireblocks team directly, and checked feasibility with our developers as I went.

A working session with the Fireblocks team

Where it fits

New users meet it inside onboarding, which was already long, so custody became its own small step, broken into four parts. Existing users get a nudge on the home screen that opens the same flow.

Mapping the wallets

Before designing any screen, I mapped every wallet type and who controls it. It's the part that confuses everyone, including us at first.

Fireblocks

  • Vault · Root walletCreated by the bank, connected during onboarding, signed manually
  • Vault · Org walletCreated by Xalts, signed through raw signing
  • API keyRevoked by deleting the API user

Org smart contract wallet

  • AdminRoot wallet
  • OwnerOrg wallet on Fireblocks

User EOA

  • Created by XaltsOne per user, private keys kept in a secrets manager

User smart contract wallet

  • AdminRoot wallet, which can change the owner and co-signer; Xalts has no access
  • OwnerThe user's EOA
  • Co-signerOrg wallet on Fireblocks, new in this project

Organising the console

Then the information architecture: where networks, wallets and users live, so an admin can start from whatever they already know.

Sketches first

Rough sketches and low-fidelity wireframes went to the team early, so feedback landed before any pixels were polished.

Paper first, feedback early

Part 1: connecting Fireblocks

It had to feel like the rest of onboarding, so it reused the same patterns and a step tracker on the right. The first screen explains what bringing your own custodian means, then lets you pick one.

Choosing Fireblocks as the custodian

Iterations

Two decisions that took a second try

A video walkthrough

  • The clearest experience
  • Fireblocks changes its UI often, and we had nobody to re-record the video

Written steps Shipped

  • Clear, actionable steps
  • We can update the copy in minutes, whenever Fireblocks changes

Confirm it worked

When you've just handed over your keys, "did that work?" shouldn't be a guess. A clear success screen closes the loop and makes the whole system feel more reliable.

The success state

Part 2: seeing every wallet

The organisation console already existed. My job was to make custody and wallet ownership obvious: who is admin, who is owner, who co-signs.

The console, with key numbers up front
Key numbers up front

Admins see what matters the moment they land, instead of digging.

Three wallet tabs

Primary, organisation and user wallets, each one click away.

Jargon, explained in place

Info icons next to terms like smart contract wallet.

Addresses you can scan

First and last 10 characters, full address on hover, the way Etherscan does it.

Pagination for slow data

User wallets are slow to fetch, so paging keeps the table responsive.

Nothing hidden

The API key shows as masked, with docs on policies and how to revoke access.

Primary wallets: root and org wallets, and who manages them
User smart contract wallets, paged

Wallets everywhere

People don't all start from the same place, so wallets appear wherever you'd look for them: on each network, and on each user.

Networks, with chain ID and environment
A new Wallets tab on each network
Users, with their teams and status
Each user’s EOA and smart contract wallets in one place

What changed

+20%Growth in institutional clients
3 weeksFrom user stories to handoff

Institutions could keep custody with a provider they trusted, which made them far more comfortable putting real assets on the platform, and Xalts stopped carrying a risk it never wanted.

Security and compliance

Keys held by a custodian banks already trust.

Better adoption

More institutions willing to bring real assets on-chain.

Less risk for Xalts

No more acting as everyone's custodian.

What I'd do next

Teach inside the console. Tooltips, a short guided tour and a little education for first-time admins, beyond the info icons.

Test with real bank admins. We designed from stories told by founders and PMs. Watching a few Rajeshes do this live would have caught edge cases we guessed at.

Design for the next custodian now. Blockdaemon and Taurus were already in the research. A flow built for any provider would save a redesign.

What I took away

A project this technical looked daunting at first. Breaking it into small, clear steps made it manageable, and so did asking for help early and giving it back.

Thanks to

Sunil Nakka (Product Manager), Ashmita Roy (Product Designer) and Jeet Parekh (Tech Lead), who made a very technical three weeks feel manageable.

Get to know me.

The story behind the work, or my résumé on one page.

Resume

Rupam Gumber's resume, Oct 2026: Founding Designer at Atlabs AI; earlier at Xalts and ClearFeed; IIT Roorkee; Adobe Designathon 2024 first runner-up and Best CSS Site of the Day.

Rupam Gumber Founding designer at Atlabs · replies within a day