Skip to main content
GET
/
wallets
/
mpc
/
cobo_key_share_holders
import cobo_waas2
from cobo_waas2.models.key_share_holder import KeyShareHolder
from cobo_waas2.rest import ApiException
from pprint import pprint

# See configuration.py for a list of all supported configurations.
configuration = cobo_waas2.Configuration(
    # Replace `<YOUR_PRIVATE_KEY>` with your private key
    api_private_key="<YOUR_PRIVATE_KEY>",
    # Select the development environment. To use the production environment, change the URL to https://api.cobo.com/v2.
    host="https://api.dev.cobo.com/v2",
)
# Enter a context with an instance of the API client
with cobo_waas2.ApiClient(configuration) as api_client:
    # Create an instance of the API class
    api_instance = cobo_waas2.WalletsMPCWalletsApi(api_client)

    try:
        # List all Cobo key share holders
        api_response = api_instance.list_cobo_key_holders()
        print("The response of WalletsMPCWalletsApi->list_cobo_key_holders:\n")
        pprint(api_response)
    except Exception as e:
        print(
            "Exception when calling WalletsMPCWalletsApi->list_cobo_key_holders: %s\n"
            % e
        )


[
  {
    "name": "Key share holder name",
    "type": "API",
    "tss_node_id": "coboAbCdEfGhIjKlMnOpQrStUvWxYz1234567890abcdefghi",
    "online": true,
    "signer": true,
    "status": "Valid",
    "account_id": "auth0|cobo|839305394802991371"
  }
]
import cobo_waas2
from cobo_waas2.models.key_share_holder import KeyShareHolder
from cobo_waas2.rest import ApiException
from pprint import pprint

# See configuration.py for a list of all supported configurations.
configuration = cobo_waas2.Configuration(
    # Replace `<YOUR_PRIVATE_KEY>` with your private key
    api_private_key="<YOUR_PRIVATE_KEY>",
    # Select the development environment. To use the production environment, change the URL to https://api.cobo.com/v2.
    host="https://api.dev.cobo.com/v2",
)
# Enter a context with an instance of the API client
with cobo_waas2.ApiClient(configuration) as api_client:
    # Create an instance of the API class
    api_instance = cobo_waas2.WalletsMPCWalletsApi(api_client)

    try:
        # List all Cobo key share holders
        api_response = api_instance.list_cobo_key_holders()
        print("The response of WalletsMPCWalletsApi->list_cobo_key_holders:\n")
        pprint(api_response)
    except Exception as e:
        print(
            "Exception when calling WalletsMPCWalletsApi->list_cobo_key_holders: %s\n"
            % e
        )

Authorizations

​
BIZ-API-KEY
string
header
required

The API key. For more details, refer to API key.

In the API playground, enter your API secret, and your API key will be accordingly calculated.

Response

Successfully listed MPC Wallets' key share holder information.

​
name
string

The key share holder name.

Example:

"Key share holder name"

​
type
enum<string>

The key share holder's TSS Node type. Possible values include:

Available options:
Cobo,
Mobile,
API
Example:

"API"

​
tss_node_id
string

The key share holder's TSS Node ID.

Example:

"coboAbCdEfGhIjKlMnOpQrStUvWxYz1234567890abcdefghi"

​
online
boolean

Whether the key share holder's TSS Node is online.

  • true: The TSS Node is online.

  • false: The TSS Node is offline.

​
signer
boolean

Whether the key share holder has been selected as the designated transaction signer. For example, in a 2-3 Threshold Signature Scheme (TSS), Cobo will serve as one signer, and you can choose one of the other two key share holders to act as the second transaction signer.

  • true: The key share holder is a designated transaction signer.

  • false: The key share holder is not a designated transaction signer.

Example:

true

​
status
enum<string>

The status of key share holder's TSS Node. Possible values include:

  • Valid: The TSS Node is configured and activated.

  • NotConfigured: The TSS Node has not been configured. This status is only applicable to mobile co-signer using the Cobo Guard.

  • NotActivated: The TSS Node has not been activated. This status is only applicable to mobile co-signer using the Cobo Guard.

  • Changed: The TSS Node has been changed. This happens when the key share holder sets up their Cobo Guard on a new phone. This Changed status serves as a reminder for you to call Create TSS request with the KeyGenFromKeyGroup and Recovery action type to finalize the setup of the key share holder's new phone. Once all set, the old TSS Node with the Changed status will be deleted.

Available options:
Valid,
NotConfigured,
NotActivated,
Changed
Example:

"Valid"

​
account_id
string

The key share holder's Cobo Portal account ID.

Example:

"auth0|cobo|839305394802991371"