The embedded risk control mechanism is a basic risk control mechanism built into the TSS Node. It evaluates task requests based on predefined rules that cannot be customized. A task request must be approved by both the embedded risk control module (if enabled) and all configured callback servers before it can proceed.Documentation Index
Fetch the complete documentation index at: https://cobo.com/developers/llms.txt
Use this file to discover all available pages before exploring further.
Configurations
The embedded risk control module can be configured through theconfigs/cobo-tss-node-config.yaml file. The configuration defines rules for the following task requests:
- Key generation (KeyGen): Creating new key shares for MPC Wallets
- Key signing (KeySign): Signing transactions or messages
- Key resharing (KeyReshare): Redistributing key shares among participants
enable: Enable or disable the embedded risk control mechanismkey_gen.reject_all: If true, reject all key generation requestskey_sign.reject_all: If true, reject all key signing requestskey_share_sign.reject_all: If true, reject all requests to sign messages for key share verificationkey_reshare.reject_all: If true, reject all key resharing requests<key_gen>.allow_listor<key_reshare>.allow_list: List of allowed key generation or resharing configurationsxpubkey: Root extended public key for key resharingnew_threshold: The new signature thresholdnew_node_ids: Node IDs of the parties allowed in key resharing
<EXTENDED_ROOT_PUBKEY>: The MPC Walletโs root extended public key<Cobo TSS Node ID>: Coboโs TSS Node ID<Customer TSS Node ID>: Your TSS Node ID<ThirdParty TSS Node ID>: A third-party TSS Node ID
Security recommendations
- While the embedded risk control mechanism provides basic security, itโs strongly recommended to also implement the callback mechanism for additional custom risk controls. This combination offers a more comprehensive and flexible risk management strategy.
- Regularly review and update your risk control configurations
- Test your configurations in a development environment before deploying to production
