API Co-signer Management

In addition to manual transaction signing and Workspace configuration approvals using a mobile device, you can automate signing and approvals with an API Co-signer. This is ideal for workspaces that handle high transaction volumes or frequent activity.

A Co-signer is connected to a workspace by pairing it with an API user. Once connected, assuming the API user has a Signer or Admin role, you will be asked to approve MPC key shares for that API user.

To activate automatic signing through the Co-signer, configure the Policy to designate the API user paired with the Co-signer as the signer. When a transaction you initiate meets the criteria defined in the policy, it will be automatically signed by the Co-signer associated with the configured API user.

At that point, you can add multiple API users to the Co-signer and configure the Callback Handler for each API user paired with it.

Use the articles below for detailed guides and information.

---

CO-SIGNER INSTALLATION

Co-signer installation flow

Install AWS Nitro Install GCP Confidential Space Install SGX on Microsoft Azure Install SGX via Azure Marketplace Install SGX on IBM Cloud Install SGX on Alibaba Cloud

Install SGX On-Premise

SETUP AND TESTING

Using the Communal Test Co-signer

Establishing Secure Communication Between the Co-signer and the Callback Handler Callback Handler Response Object Approve Transactions Approve Configuration Changes

Callback Handler Code Example Use the Plugin-based Callback Handler Validate ETH Raw Transactions

MAINTENANCE

Overview SGX Co-signer Maintenance AWS Co-signer Maintenance GCP Co-signer Maintenance

CO-SIGNER OPERATION

Using APIs, Console and Command-Line Interface to Operate the Co-signer

VERSIONS

Overview SGX Co-signer Version History AWS Co-signer Version History GCP Co-signer Version History

SUPPORT

Troubleshooting