The TSS Node callback mechanism is a critical component in the server co-signer solution that enables custom risk control implementation. When enabled, it reviews and approves all task requests before the TSS Node executes them.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.
Sample callback server
Cobo provides example callback server implementations in multiple programming languages to help you quickly develop your callback server. You can find these examples in our GitHub repository.How it works
After startup, the TSS Node establishes a persistent connection with the Cobo WaaS service to receive task requests. These tasks fall into three categories:- Key generation (KeyGen): Creating new key shares for your MPC Wallets.
- Key signing (KeySign): Signing transactions or messages.
- Key resharing (KeyReshare): Redistributing key shares among participants.
Communication security
The TSS Node and callback server communicate via HTTP, using JSON Web Token (JWT) with RS256 signing algorithm to ensure secure data transmission. This involves:- Key generation: Both the TSS Node and callback server generate their own RSA key pairs.
- Key exchange: Each component configures the otherโs RSA public key in their system.
- Request signing: All requests are signed using the senderโs private key.
- Signature verification: Recipients verify signatures using the senderโs public key.
Implementation steps
To implement the callback mechanism:- Deploy your TSS Node callback server.
- Configure callback keys.
- Start both the TSS Node and callback server.
