Fireblocks custody

Fireblocks builds custody on multi-party computation, specifically its own MPC-CMP protocol. A private key is never assembled in one place. Instead it is split into several key shares held by different parties, so no single device, employee or breach can produce a valid signature on its own. Signing a transaction requires the relevant shares to compute a joint signature, and a policy engine sits in front of that process to enforce who can initiate a transfer, to which addresses and above what size, before any signature happens. That combination, key-share splitting plus policy enforcement, is what "custody layer" means in practice.

This is different from a hot wallet controlled by one private key, where compromising that single key is enough to move funds. It is also different from a cold wallet that is safe from remote attack but slow and manual to operate. MPC-CMP is built to give both properties at once, no single point of compromise and transaction throughput fast enough for an active platform.

The Fireblocks relationship is stated on EarnPark's own Proof of Reserves page, alongside the custody wallets covered in the monthly report. Fireblocks does not publish a public customer registry, so there is no independent third-party page that names EarnPark as a client the way a stock exchange listing or a government register would. That is a real limit of this signal and worth saying plainly rather than glossing over. What can be checked independently is narrower but concrete, namely the on-chain wallet addresses named on the Proof of Reserves page, which anyone can look up in a public block explorer regardless of what EarnPark says about them.