Security

Custody built on no single point of failure

CryptoMelon combines threshold multi-party computation, hardware-bound key shares, and policy-driven signing to protect institutional assets across Bitcoin, Ethereum, BNB Chain, Solana, and TRON.

MPC key shares distributed across independent hardware security modules

How CryptoMelon secures wallets

Every organization wallet is generated as a threshold key. Private key shares are distributed across operator devices and hardware security modules. A transaction can only be signed when a configured quorum approves, and the full private key is never assembled on any single device.

Threshold MPC

2-of-3 default, configurable up to 5-of-9.

Hardware-bound shares

TPM / Secure Enclave attestation per device.

Policy engine

Allowlists, limits, and per-address quorums.

SOC 2 Type II

Continuous controls and annual audit.

Operational protections

Encrypted infrastructure

All data is encrypted in transit and at rest. Wallet key shares are generated client-side or inside HSM-backed signing services CryptoMelon cannot decrypt.

Proactive resharing

Key shares are periodically refreshed so previously exposed or retired shares become unusable, without changing wallet addresses.

Audit trail

Every signing request, policy change, and operator action is logged immutably for compliance and incident review.

Run secure custody in production

Threshold signing, sub-address issuance, and automated sweeps across BTC, ETH, BNB, SOL, and TRX.

Create workspace Learn about MPC wallets