Skip to main content

Architecture


ABC WaaS Architecture

ABC WaaS is designed with three core layers so developers can integrate wallet functionality into their services immediately, even without deep blockchain expertise: Auth (Authentication) - MPC (Key Management) - Core (Execution).

This structure is responsible for the full flow from secure key handling and signing to final network broadcast.

1. Auth (Authentication): User Identification and Authorization

The process starts by identifying who the user is.

  • Role: Identifies users in the service app (DApp) and grants temporary access to wallet functions.
  • Flow: When the service backend completes a username-based login request, the WaaS server issues an authentication token (Access Token) that proves the session.
  • Usage: The issued token acts as the starting key to activate the MPC engine in the next step.

2. MPC (Key Management): Distributed and Secure Key Environment

This is the security layer that creates and manages blockchain keys based on authenticated tokens.

  • Role: Instead of storing a private key as a single complete secret, MPC generates and manages it as multiple distributed key shares (Key Share).
  • Flow: If the token from the Auth step is valid, the MPC engine prepares secure operations (generation/recovery/signing) using distributed key fragments.
  • Key Point: This structurally reduces key exposure risk and allows users to recover wallets safely through username authentication, even after device changes.

3. Core (Execution): Multi-Chain Transaction Delivery

This is the execution layer that communicates with actual blockchain networks using prepared keys.

  • Role: Builds transaction data and executes signing for multiple chains, including EVM (Ethereum, Polygon, etc.) and Solana.
  • Flow: When developers submit transfer data, the Core API requests signing from the MPC layer and then broadcasts the final signed transaction to the blockchain network.
  • Key Point: Developers can complete the transfer flow with API calls only, without implementing chain-specific RPC node management or complex signing logic.

Architecture Sequence

ABC WaaS Architecture Sequence