Getting Started with ABC WaaS
With ABC WaaS, you can integrate blockchain wallet functionality into your service quickly. This page introduces the two core pieces you need for integration: authentication and MPC integration methods. Once you choose an MPC integration method, you can move directly into setup and implementation.
Step 1 - Authentication Overview
All WaaS features operate based on an Access Token.
When your backend calls the ABC WaaS Auth API with a username, a token is issued, and that token becomes the starting point for MPC signing and wallet access.
The authentication flow is always the same regardless of which MPC method you choose. The only difference is whether the issued token is passed to the Client Node or to the client SDK.
Your Backend -> Auth API Request -> Access Token Issued
|
v
Delivered to MPC Client Node or Client SDK
You need an API Key before calling the Auth API. Request a console account through Contact Us, then check your API Key in the console.
Step 2 - Choose an MPC Integration Method
MPC can be integrated in two different ways depending on your service architecture. Choose based on whether keys should be managed on the server or on the user device.
Option A - Server-side (Client Node)
Your backend handles key generation and signing directly. ABC provides a Docker image that you deploy into your server environment and call through REST APIs.
Your Backend -> Client Node (Docker) -> MPC Node
Best suited for
- Server-centric services that do not install an SDK on user devices
- Cases where key shares should be stored and managed directly by the service backend
- Exchanges, custody platforms, and enterprise backends
Start here -> Server-side Guide
Option B - Client-side (Mobile SDK / WASM)
The user device (app or web browser) communicates directly with the MPC Node and performs signing. Your backend only needs to issue the Access Token and deliver it to the client.
User Device (SDK/WASM) -> MPC Node
Your Backend -> Issues Access Token only
Best suited for
- Wallet apps where users review and sign transactions directly
- Web DApps and browser-based services
- Security-sensitive environments where key shares must not pass through the server
| SDK | Environment | Start here |
|---|---|---|
| Mobile SDK | Native Android / iOS apps | Mobile SDK Guide |
| WASM | Web browser | Contact us separately |
Comparison
| Option A (Server-side) | Option B (Client-side) | |
|---|---|---|
| Key share location | Service backend | User device |
| Installation target | Docker (server) | SDK or WASM (client) |
| Backend role | Full key generation, signing, and management | Access Token issuance only |
| Key exposure risk if server is compromised | Requires separate encryption and operational controls | None (key shares are not on the server) |
| Best suited for | Exchanges, custody, enterprise | Wallet apps, DApps, web services |
Both options use an MPC 2-of-3 architecture, so compromising a single node does not expose the private key. For more details about the security model, see the MPC Service Guide.
Next Steps
Once you choose a method, proceed in this order:
- Get a console account - Request one through Contact Us
- Issue an API Key - Check your API Key in the console
- Architecture - Understand the full Auth -> MPC -> Core flow
- Install MPC
- Server-side -> Client Node Guide
- Mobile -> Mobile SDK Guide