Signing Schemes
Signing
To transact virtual assets, a signature with the private key must be completed. Octet supports three signing methods: multisig (SSS), multisig (MPC), and singlesig.
Multisig
Multisig is a method that distributes control over assets across multiple key shares. A transaction is approved only with the participation of multiple verifiers under the configured condition (M-of-N), so asset theft through a single leaked key can be prevented.
1. Multisig (SSS)
Octet supports the SSS (Shamir's Secret Sharing) 2-of-3 method and uses a multisig key that splits the private key into three parts for signing. The multisig key is divided into the Octet key, user key, and backup key, which are managed separately by Octet and the client.
Multisig key types
| Type | Description |
|---|---|
Octet key |
A key stored by Octet. |
User key |
A key stored by the client. |
Backup key |
A key stored by the client. |
Creating a multisig (SSS) key
The client creates the multisig key directly with the key generator. The program does not collect any information, and the information generated by the program is stored only in the environment where the program was run. Octet stores only the encrypted Octet key data that the client delivers directly, and cannot know the client's private key.
2. Multisig (MPC)
MPC (Multi-Party Computation) is a threshold signing method in which m of n key shares cooperate (M-of-N) to produce one valid signature. Because the parties each take part in the computation with their distributed shares without ever creating or reconstructing a complete private key, it offers very strong security.
Octet supports the MPC 2-of-3 method, distributing signing authority across three independent shares. The shares consist of Octet Share 1, Octet Share 2, and the user share, which are managed separately by Octet and the end user, completely eliminating any single point of failure.
A multisig (SSS) key splits one generated private key into three parts.
In contrast, the MPC key used in multisig (MPC) never generates a single private key; instead, three shares take part in the signing computation and act together as the private key.
MPC key types
| Type | Description |
|---|---|
Octet Share 1 |
Share 1, stored by Octet. |
Octet Share 2 (backup key) |
Share 2, stored by Octet. |
User Share |
The share stored by the end user. |
Creating a multisig (MPC) key
The client creates the MPC key directly with the MPC agent. The information generated by the program is stored only in the environment where the program was run. Octet stores only the encrypted server shares and cannot know the end user's User Share. For detailed key creation steps, see the MPC key creation guide.
3. Singlesig
Octet manages the private key entirely. When the client requests a withdrawal, Octet signs using the private key it stores. If you choose the singlesig method, Octet automatically generates the private key when the wallet is created.
Key management methods
The keys needed for signing can be managed in three ways. The key management method is chosen when creating a wallet, and it determines the signing method and the withdrawal method.
1. Co-managed - SSS
Three multisig keys are divided between the Octet team and the client, each managing their own. This strongly blocks external security threats. However, the multisig keys must be managed safely so that they are not leaked externally.
2. Co-managed - MPC
Three shares are divided between the Octet team and the end user, each managing their own. This strongly blocks external security threats.
3. Octet-managed
One private key is managed by the Octet team. Since there is no need to manage keys yourself, we recommend choosing the Octet-managed method if it is difficult to build a high-level security system.
| Co-managed - SSS | Co-managed - MPC | Octet-managed | |
|---|---|---|---|
| Key manager | Octet, client | Octet, end user | Octet |
| Key type | 3 multisig keys | 3 MPC keys | 1 private key |
| Signing method | Multisig (SSS) | Multisig (MPC) | Singlesig |