Menu
Theme

Years I contributed:2020–2025DeFi · Exchange application

Polkaswap

A decentralized exchange I helped build across its front end, wallet, and blockchain libraries, while hiring and leading the front-end team.

My role
Software engineering, architecture & front-end leadership
Context
Soramitsu · September 2020–May 2025
Explore the project

Polkaswap was my largest engineering commitment at Soramitsu. I started its front end in September 2020 and joined the hiring process the following week. I brought experienced front-end engineers onto the project and stayed involved in implementation as my responsibilities grew to architecture, code review, and team delivery.

The application brings trading, liquidity management, and cross-chain transfers into one interface. My work extended into the wallet and the TypeScript library connecting those features to the blockchain. We reached the public launch in April 2021 and continued developing the application through successive releases; my contributions ran through May 2025.

I am proud of the people I worked with here and how much we built together. Some of the technology choices, algorithms, and engineering approaches from this project are still among the decisions I value most.

Built with
VueTypeScriptVuexPolkadot.jsEthersRxJSTelegram Mini AppsIPFSSCSS

Inside the product

A reconstructed Polkaswap swap form with two asset amounts and transaction details.

From a quote to a transaction

A compact swap form brings together a live quote, available balance, network fees, and confirmation state. I worked on the calculations and transaction handling behind these controls, including guarding against repeated submissions.

A reconstructed trading view showing the XOR and ETH pair, price chart, and interval controls.

A workspace around the trade

Market information sits alongside the transaction controls. The team developed the trading workspace through successive releases, adding charts and widgets that users could rearrange, resize, and open in picture-in-picture.

  • Wallet and transaction infrastructure

    Started the wallet library and built core account and transaction flows, alongside the blockchain API. I introduced shared transaction tracking so submission, confirmation, and failure could be reported across the application. The application kept tracking a transaction after the user left the form that started it.

  • Complex financial interactions, built hands-on

    Built the collateral and borrowing interface with the team, including position management, repayment, and live price updates. My implementation connected multiple quote subscriptions and per-block collateral updates to the interface, letting users inspect how an action would change their position before confirming it.

  • Trading widgets outside the browser window

    Proposed picture-in-picture widgets, built the first prototype, and guided the architecture and team implementation. A user could keep a chart visible while playing a game or minimizing the browser, with swap controls and other interactive widgets available in the same always-on-top mode. We used the browser’s Document Picture-in-Picture API where supported.

  • Adapting the exchange to Telegram and mobile

    Designed Telegram Mini App support and native mobile interactions. I implemented the migration to Telegram’s native WebApp API, handling launch parameters, viewport behavior, gestures, and theme integration. The same application also had to keep working in an ordinary browser, so initialization and host-specific behavior needed clear boundaries.

  • Code review and releases across three repositories

    Led technical delivery across the exchange, wallet, and blockchain library. I reviewed teammates’ work, coordinated dependency updates and release branches, and remained hands-on with features and fixes. I contributed to every Polkaswap release during my time on the project.

An exchange that could run from static files

We distributed the application through IPFS (Interplanetary File System) as static files. Server-side rendering and an application-owned middleware service could not be prerequisites for using the exchange. Blockchain nodes and indexing services supplied data, while the browser managed the connected account, live updates, and the progress of transactions.

That made the boundaries between the exchange, wallet, and bridge important. Early in development, I moved connection management into a shared layer so their APIs could operate in parallel through the same blockchain connection. Opening, closing, and restarting that connection became a separate responsibility from performing a swap or reading a balance.

As the API grew, I reorganized it into modules for assets, swaps, liquidity, rewards, and referrals. Each module handled its own operations while reusing the same account, signing, fee estimation, and transaction submission logic. I also added runnable examples so developers could exercise those operations without going through the exchange interface.

The bridge showed why this structure was useful. A transfer could involve a transaction on one chain, approval signatures, and a contract call on another. I implemented the bridge API’s transfer operations, status handling, and asset conversions. The interface needed to explain which stage had completed and what still needed to happen, with shared account and transaction handling underneath.

My work at Soramitsu

At Soramitsu, I grew from Senior Front-end Developer to Front-end Team Leader, then Head of Front-end Development. That progression covered work across banking, wallets, exchanges, and shared front-end infrastructure.

Career timeline January 2020–2026

  1. Head of Front-end Development

    May 2024–2026

  2. Front-end Team Leader

    January 2021–May 2024

  3. Senior Front-end Developer

    January 2020–January 2021

Broader responsibilities

Progressed from senior engineering to leading the front-end department, while continuing implementation and code review.

  • Created the front-end department and established its structure, engineering workflows, and quality standards.
  • Built shared design-system foundations and helped migrate projects to a common front-end technology stack.
  • Hired and mentored developers, coordinated roadmaps and delivery, and supported collaboration across product, design, and engineering.
  • Organized internal meetups and knowledge-sharing sessions, and contributed to technical direction across company projects.
Full CV
Start a conversation

What are you
working on?

An engineering role, a product to build, or a technical problem to work through. I’d like to hear about it.