Skip to main content

Embedded Wallet

1. Embedded Wallet (MPC) overview​

Embedded Wallet is a next-generation virtual asset wallet model designed so that end users have direct control over their own asset addresses. By using MPC (Multi-Party Computation) technology to store key shares in a distributed way, it dramatically raises security and gives end users real control over their assets.


Key features​

Figure 1: 2-of-3 MPC model
  • 2-of-3 MPC model: Two of the three key shares are required to complete a signature.
    • 1 (User Share): Stored and controlled on the end user's side.
    • 2 (Octet Shares): Stored securely by Octet.
  • End user control: Moving assets always requires the end user's signature; neither the client nor Octet alone can withdraw assets.


2. Choosing an integration method: agent vs SDK​

Octet provides two integration methods to suit the client's infrastructure and service type. You can choose the appropriate method for your business requirements.

  • Agent method: The MPC agent program provided by Octet is installed and operated on the client server. MPC key creation and signing computations are performed by the agent inside the client server.
  • SDK method: The MPC SDK provided by Octet is integrated into the end user's app (iOS/Android) or web. MPC key creation and signing computations are performed directly on the end user's device.

Comparison by method​

ItemAgentSDK
MPC computation locationMPC agent installed on the client serverEnd user device (iOS/Android/Web)
Final storage of the User ShareThe User Share created by the agent is delivered to the end user and then stored on the end user's device according to the client's implementation (device-local secure area such as Secure Enclave recommended)Device-local secure area (Secure Enclave, etc.)
User Share delivery flowRetrieved from the agent → delivered to the end user → deleted from the agentThe SDK stores it directly in the device's secure storage
Installation targetClient infrastructure (server)End user app/web
Reissue (Refresh) on User Share lossSupported — the agent performs the reissue computation and delivers the new User Share to the end user againNot supported


3. Contact​

For the agent program or SDK, and any other guidance needed for integration, contact us below.