Safeheron

• Name: Safeheron
• URL: https://safeheron.com/
• Category: institutional MPC custody / white-label wallet infrastructure / key-management company
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: Safeheron belongs as an entity note, not a protocol note. The useful question is who sells and shapes the institutional signer workflow across MPC self-custody, white-label wallet infrastructure, approval policy, offline authorization, and recovery procedure. The practical leverage is not a new account model; it is the Safeheron-controlled operating shell that decides deployment shape, policy features, wallet separation, and which Safeheron-managed components remain in the path.
• What it does:
  • Provides an institutional MPC self-custody platform for holding and moving digital assets across mobile, web-console, browser-extension, API, and Web3-facing wallet surfaces
  • Offers a white-label MPC Node Suite with server-side services plus browser, Android, and iOS SDKs so teams can build branded wallets and embedded wallet products on top of Safeheron’s signer stack
  • Distinguishes between Asset Wallets for transfers and operational automation, and Web3 Wallets for DApp interaction, NFT handling, contract deployment, and typed-data or transaction signing
  • Packages policy-engine controls, multi-factor and offline authorization, off-chain multisignature approvals, and recovery mechanisms so institutions can harden signing ceremony and fallback paths without building the whole control plane themselves
  • Publishes developer documentation and open-source cryptographic repositories covering MPC-TSS, TEE / SGX concepts, SDKs, wallet models, and related integration patterns
• Key claims:
  • Safeheron describes itself in the developer docs as an open and transparent digital asset self-custody platform for institutions built with MPC and TEE technologies
  • The official site markets battle-tested security solutions for 170+ institutions since 2021, $1.5B+peakassetsundercustody,and$150B+ securely transferred; these should still be read as vendor claims unless independently verified
  • Product materials say the MPC Node Suite supports on-prem or privatized deployment, multiple threshold configurations, and a broad signature and chain matrix spanning ECDSA, EdDSA, and Schnorr use cases
  • Security pages emphasize zero-trust architecture, WYSIWYS-style approval integrity, AML screening, disaster recovery, and user-controlled key recovery as core differentiators
  • The public GitHub organization and docs reinforce Safeheron’s pitch that open-source cryptographic components and transparent engineering are part of the trust model, not just marketing language
• Whitepaper: No classic company whitepaper is the point here. The strongest primary materials remain Safeheron’s official site, product and security pages, developer documentation, and GitHub organization, alongside the existing source capture in ../whitepapers/safeheron-primary-sources-2026-04-23.md.
• Sources:
  • https://safeheron.com/
  • https://safeheron.com/products/mpc-self-custody/
  • https://safeheron.com/products/mpc-node-suite/
  • https://safeheron.com/features/security/
  • https://developer.safeheron.com/
  • https://developer.safeheron.com/concepts/wallet
  • https://developer.safeheron.com/smn/technology_overview/mpc-tss-overview
  • https://developer.safeheron.com/smn/technology_overview/tee-overview
  • https://github.com/Safeheron

Internal linkages

• Project-layer alias: safeheron.
• Keep the comparison set on the clearest adjacent custody-and-policy operators: bitgo, fireblocks, and zodia-custody.
• Cleaner contrast where more of the signer stack stays application-side: dfns.

Control surface

• Authority sits in node placement, approval policy, signing ceremony design, wallet-type separation, recovery paths, and which Safeheron-managed services remain in the path.

• Self-custody MPC does not erase the operator boundary if Safeheron still defines the product shell, recovery logic, policy affordances, and white-label stack customers standardize around.

• Treat Safeheron as institutional signer-workflow infrastructure first. Wallet and self-custody are just the front labels.

• Last reviewed: 2026-08-07 UTC