The MPC nodes are all based on an implementation in Go. In some cases, this is cross-compiled to other platforms.
The default MPC node is based on our Go platform deployed as a Docker-based service. Such a node acts as a service, and operations can be initiated from a different machine using the TSM SDK.
Beyond this we support a number of other platforms with embedded nodes. An embedded node does not listen for incoming requests, and can thus only participate in protocol executions where the application embedding the node is the initiator.
- Web Assembly
We provide different tools for ensuring resilience including:
- node monitoring
- node back-up
- Emergency Recovery System (ERS) for cryptographic keys
Depending on the MPC protocol behind the cryptographic primitive in question, our solution delivers state-of-the-art performance.
As an example, when run in our load-balancing setup with seven TSM instances, our proprietary ECDSA-protocol allows for around 10,000 signatures per second.
Further numbers and details are available on request.
Updated 5 months ago