Overview

At the heart of Fireblocks' security lies the MPC protocol, providing robust security while heavily relying on the network due to multiple rounds between your end-user client and Fireblocks. This implies that every enhancement between the end-user and Fireblocks is then multiplied by the number of rounds (when optimizing steps that are called during the MPC process). You can find more information about the MPC protocol here:

Boosting Backend Performance

Here are a few tips on implementing your backend for optimal performance:

Initialize Fireblocks JS SDK: Use HTTP Keep-Alive parameter as demonstrated in the backend demo.
Utilize WebSockets: When listening to RPC endpoints, use WebSockets to save time on opening a new connection for each call. See the example in the web demo here.
Optimize walletId Retrieval: Ensure the walletId is fetched promptly before attaching it to every RPC call delegated to Fireblocks.

Boosting Client Performance

During SDK initialization, the client will fetch a few certificates required to make calls to Fireblocks endpoints if it was not previously called. This process may take a few moments; therefore, it is highly suggested to initialize the SDK as early as possible. The initializations don't have to be adjacent to the call to generateMPCKeys.

On mobile, it is recommended to use a connection pool and maintain some connections. You can view an example of a connection pool in our Android demo.