Builder Vault TSM Overview

1. What is Builder Vault TSM?

Builder Vault serves as a virtual threshold security module (TSM) designed for the secure generation, storage, and utilization of cryptographic keys. Our TSM is trusted by numerous institutions to enhance the security of wallets and enable multi-party approval mechanisms called Blockdaemon Advance MPC.

Builder Vault TSM is constituted by the following artifacts:

• MPC software that is uploaded to nodes under your control (containers, VMs, or mobile).
• An interconnected cluster of MPC nodes forms a TSM (Threshold Security Module), with each node responsible for generating and securely storing a portion of the private key.
• SDKs that deliver user-friendly interfaces for seamless integration, efficient administration, and enhanced control.
• A cluster of n MPC (Multi-Party Computation) nodes, wherein a transaction is collectively signed when approval is obtained from m out of the n participating parties using their respective key shares.

1.1 Why use the Blockdaemon Advance MPC?

• No Complete Key: Eliminates single point of failure vulnerabilities.
• Multi-party Approval: Cryptographically Enforced.
• One Key/Signature: Universal Multi-party Approval.
• Superior Efficiency: No smart contracts, gas fees and etc.

2. Builder Vault TSM Features

Builder Vault TSM presents five key features that make it well-suited for diverse industries, encompassing crypto-accepting payment companies, custodians, as well as Web3 and cryptocurrency foundations.

• Expertise: With over 15 years of MPC experience, we stand unrivaled in the industry, surpassing all vendors in terms of experience.
• Flexibility: When configuring our TSM, you encounter minimal limitations, making it the most flexible option available among vendors.
• Performance: Our TSM boasts an exceptional track record with millisecond-level latency, processing millions of keys in wallets, a feat no other vendor can match in terms of latency and scalability.
• Control: Achieve complete self-hosting capabilities with our TSM, eliminating any dependencies on vendors.
• Secure: Builder Vault places paramount importance on security, employing battle-tested MPC technology designed by leading cryptographers in the field.

These five features collectively solidify Builder Vault as the safest choice, as it harnesses the most established technology and provides unique functionalities unmatched by any other vendors. Additionally, it is developed by Blockdaemon, a prominent blockchain infrastructure provider, adding to its credibility and trustworthiness.

3. Builder Vault TSM Architecture

3.1 Application

The application that you are developing, such as a wallet, which interfaces with the TSM to have transactions signed, when approved.

3.2 SDK

The SDK has the capability to independently manage individual MPC nodes, while the User SDK can access and provide approvals. Additionally, the SDK is accessible through multiple programming languages, including JavaScript, Swift, and Golang, offering flexibility and ease of integration.

We provide the following SDKs:

3.3 ERS Application

An application to recover from a complete system loss or compromise.

3.4 MPC Nodes

MPC Nodes are highly versatile and compatible with a wide range of computing devices, including iOS, Java VM, Web Assembly, and Docker. You have the flexibility to self-host them in various environments, whether it's on-premises, in a public or private cloud, or on mobile platforms. MPC nodes serve various essential functions, including:

• Enabling MPC Quorum Approvals
• Managing Key Shares
• Performing Cryptographic Operations
• Supporting MPC Protocols

3.5 Message Broker

The message broker plays a pivotal role in establishing connections between nodes and offers the flexibility to be hosted independently, separate from the MPC Nodes themselves.

4. TSM Environment

Builder Vault TSM offers two different environments that can be used when setting up your TSM in a multi-party computation environment:

4.1 Static TSM Clusters

In a Static TSM Cluster, the number of participating nodes and their configuration remain fixed once the cluster is established. This means that the cluster has a predetermined number of nodes, and these nodes don't change in number or configuration without significant administrative intervention. This environment has the most alternative support with limited hosting options and a maximum of 1 mobile node per TSM.

4.2 Dynamic TSM Clusters

Dynamic TSM Clusters, on the other hand, are more flexible. They allow for nodes to be added or removed from the cluster, and the configuration can change dynamically without disrupting the overall operation of the TSM. Dynamic clusters are commonly used in the "Wallet as a Service" (WaaS) model, where the Service Provider (SP) hosts one or more nodes, while the client has the flexibility to host up to one node per TSM. This arrangement allows clients to easily adapt their cluster configuration based on their specific needs and requirements.

5. TSM WEB3 Wallet Use Case

In this example, we introduce a WEB3 wallet, designed as a self-custody multi-chain wallet. Below, we provide the architectural diagram used for this specific WEB3 wallet use case.

Utilizing the architecture described above, the WEB3 wallet offers the following advantages and functionalities:

5.1 Wallet Service

• No reliance on private keys or seed phrases.
• Noncustodial or self-custody model.
• Accommodates single or multiple mobile nodes or users, enabling:
  • Multi-party approval mechanisms.
  • Social Recovery options.

5.2 TSM-MPC-based Cryptographic Platform

• Proven Advanced MPC with utmost security.
• Scales to 100s millions of users/wallets.
• Blockchain Protocol agnostic (CeFi, DeFi, NFT).

5.3 SDK Libraries

• Separates wallets from applications.
• Abstraction of MPC and Cryptography.
• SDK libraries compatible across various platforms.