Wallet · MPC

Multi-chain MPC wallet

A private key custody architecture

PeriodAbout 1 month

Business LineC-end multi-chain wallet

Core StackMPC-TSS / EVM Multi-Chain / iOS· Android

RegionMiddle East

Project Background and Challenges

Clients need a multi-chain wallet aimed at the consumer end that guarantees asset self-custody without direct exposure to mnemonic phrases, and supports multiple EVM chains and mainstream assets.

The core challenge is the security model for key management and multi-chain compatibility—it must be both secure and reliable, while also making it accessible for ordinary users.

The scope we undertake

MPC key management architecture, multi-chain transaction signatures, asset and market aggregation, client (iOS / Android).

Scope 1

MPC key management architecture

Scope 2

Multi-chain transaction signatures

Scope 3

Assets and market aggregation

Scope 4

Client (iOS/Android)

Technology stack

Key

MPC-TSS (threshold signature, client-server sharding)

Chain

EVM multi-chain compatibility, unifying the transaction abstraction layer

Client

Native / Cross-platform iOS· Android

Backend

Node access + market data / asset aggregation services

Key technical decisions

Decision 01

Key Scheme: MPC vs Multi-Signature

Select MPC-TSS. Customers want a consumer-side experience—multi-signature requires multiple on-chain interactions and high gas costs, whereas MPC completes threshold signatures off-chain, saving gas and never exposing the complete private key.

Decision 02

Key sharded storage

Sharding is stored separately from the client and server sides; leakage on either side is insufficient to restore the private key, eliminating a single point of risk from an architectural perspective.

Decision 03

Multi-chain abstraction layer

By creating a unified transaction abstraction layer, new EVM chains only require configuration without changing the core signature logic, significantly shortening subsequent chain expansion cycles.

Delivery Success (Desensitization)

5+ entries

Supported EVM chains

100 +

Number of supported assets

<1 s

The signing process is end-to-end time-consuming

Teams and cycles

The total cycle is about 20 days, involving 5 people, progressing in four phases:

Safety model design

MPC key system

Multi-chain and client-side platforms

Audit and online service

Want to see the complete Figma file?

Schedule a 30-minute technical consultation where we walk you through the most relevant Figma / Lanhu files for your project via remote demo, including all pages, component libraries, and interactive prototypes.

Book Technical Consultation Telegram