Cubist

• Name: Cubist
• URL: https://cubist.dev/
• Category: key-management infrastructure / signing security / embedded-wallet and digital-asset operations tooling
• Tags: ethereum-ecosystem solana-ecosystem bitcoin-ecosystem
• Summary: Cubist is signer-and-policy infrastructure, not a wallet rail. The thing that matters is CubeSigner: hardware-backed key control with scoped sessions, org roles, receiver policy, and automation hooks for teams that want hot-wallet speed without handing raw key material to app servers.
• What it does:
  • Provides CubeSigner for hardware-backed key generation and signing, with API and SDK access for operational and application workflows
  • Exposes scoped sessions, role-based access, and programmable security policies for controlling which requests may be signed
  • Supports multiple blockchain environments in public SDK materials, including EVM chains plus Bitcoin and Solana
  • Markets architecture built around authentication, a policy engine, and a virtual HSM using enclaves plus certified HSM roots of trust
  • Positions itself for high-volume automation, embedded-wallet use cases, and broader digital-asset lifecycle management
  • Maintains public SDKs and repositories in TypeScript, Go, and Rust, including older multichain / cross-chain developer tooling under the broader Cubist brand
• Key claims:
  • Homepage says Cubist is securing over $11 billion in customer assets and offers a SOC2-compliant infrastructure layer for orchestrating, governing, and securing onchain activity
  • Product copy frames CubeSigner around combining tamper-resistant hardware, audit trails, and programmable compliance controls
  • Security architecture materials describe a stack consisting of an authentication layer, policy engine, and virtual HSM
  • Public SDK READMEs describe CubeSigner as hardware-backed and non-custodial, using HSM-sealed Nitro Enclaves to combine cold-wallet security with hot-wallet speed and simplicity
  • GitHub organization copy claims CubeSigner improves performance versus status-quo key-management setups while serving security-critical use cases such as DeFi, staking, and cross-chain bridging
  • Public SDK examples show org / role / session abstractions, scoped signing permissions, transaction-receiver policies, and raw-blob-signing restrictions
• Whitepaper: No classic whitepaper or litepaper was found during this pass. Primary-source snapshots were saved in ../whitepapers/cubist-primary-sources-2026-04-22.md.
• Sources:
  • https://cubist.dev/
  • https://cubist.dev/about
  • https://cubist.dev/product-security
  • https://github.com/cubist-labs
  • https://github.com/cubist-labs/CubeSigner-TypeScript-SDK
  • https://github.com/cubist-labs/CubeSigner-Go-SDK
  • https://github.com/cubist-labs/cubist

Internal linkages

• Best upward reads for app-owned signer control planes: turnkey, dfns, and fireblocks.

Control surface

• The leverage sits in org and session issuance, policy templates, receiver restrictions, approval paths, and how much trust a customer places in Cubist’s enclave-plus-HSM operating model.

• Cubist is operator-side signing infrastructure. It helps run keys and workflows; it is not the account substrate.

• Last reviewed: 2026-06-17 UTC