A crypto wallet that unlocks like a normal sign-in

Five years, senior to principal: I led the frontend architecture for Ultra’s browser-extension wallet and NFT marketplace, used by thousands of players.

Role
Senior to principal engineer
Team
Led 2 frontend engineers
When
Mar 2020 – Sep 2025
Core stack
Angular, Chrome extension, Electron, NestJS
Users
Thousands of active players
Ultra wallet screens: a balance view and a collectible transfer

The story

  1. Problem

    Seed phrases lose buyers

    Players came to buy game items, not to learn crypto. Seed phrases, extension pop-ups, and unclear signing prompts lost them at checkout.

  2. Approach

    Make the wallet feel like an account

    Sign in once and the wallet unlocks. Keys never live in the frontend, and the marketplace can only ask the wallet for a few safe things.

  3. Result

    A wallet thousands of players used

    A wallet built as a self-contained module: it shipped as a Chrome extension, then moved into Ultra’s desktop game launcher with little rework. I led two frontend engineers.

One purchase, end to end

Marketplace and wallet only talk across the dashed line, and every message is encrypted. The solid block is where the player decides.

PlayerdecidesMarketplaceweb appWalletextensionUltra APIbackendSign inone accountSessionverifiedUnlockedno key keptBuy itemProxy callConfirmpopupApprovein popupSignthe orderSettleon-chainencrypted messages onlyPlayerdecidesMarketweb appWalletextensionUltra APIbackendSign inone accountSessionverifiedUnlockedno key keptBuy itemProxy callConfirmpopupApprovein popupSignthe orderSettleon-chainencrypted messages only

Calls I made

  • Sign-in is the unlock

    People already trust their account. Decryption keys are never stored in the frontend, so there is no key at rest in the browser to steal.

  • A Proxy, not an open API

    A JavaScript Proxy exposes only the commands the marketplace needs. Everything else doesn’t exist from the page’s side.

  • One wallet module, two hosts

    The wallet kept no ties to the browser it first shipped in, so the same module dropped into the Electron game launcher instead of being rebuilt for desktop.

  • Encrypt even our own messages

    The marketplace and the wallet talk only through Chrome extension message events, and every one is encrypted, because the page is untrusted ground.

Beyond the wallet

Wallet
  • Angular
  • Self-contained module
  • Chrome extension
  • Proxy command API
  • Encrypted messaging
Marketplace
  • Angular architecture
  • API contracts with backend
Services
  • NestJS
  • GraphQL
  • Apache Kafka
Desktop
  • Electron game launcher
  • Same wallet module
  • Works offline
  • Updates itself
Delivery
  • CI/CD pipelines

“An exceptional teammate. Excelled in front-end architecture with a strong UX and security focus. His expertise and collaborative spirit made a real difference.”

Paulo Ferreira
Lead Backend @ Ultra
Next case · ACTThe AI drafts the exam question. A specialist decides.