Copper

  • Name: Copper
  • URL: https://copper.co/
  • Category: institutional custody / prime services / off-exchange settlement / collateral-management operating stack
  • Tags: bitcoin-ecosystem ethereum-ecosystem
  • Summary: Copper belongs as an entity note, not a protocol note. The useful question is who controls the company-run operating stack that combines MPC custody, ClearLoop venue connectivity, collateral routing, organizational permissions, address-book policy, trading objects, and lending workflow under one institutional shell. The practical leverage is not just custody; it is that a named company can sit between an institution and its exchanges, collateral locations, counterparties, and day-to-day treasury operations.
  • What it does:
    • Provides institutional digital-asset custody built around Copper’s MPC wallet architecture and organization / portfolio / wallet model
    • Runs ClearLoop, an off-exchange settlement and exchange-connectivity surface that lets institutions trade on centralized venues without pre-funding those venues directly from exchange-held balances
    • Exposes a broad API surface for wallets, portfolios, orders, loans, address-book entries, deposit targets, counterparties, and ClearLoop settlements
    • Packages collateral management, lending, and related post-trade workflow into the same operating platform as custody and settlement
    • Sells the whole stack as institutional infrastructure rather than as one narrow signing SDK or one isolated exchange-integration product
  • Key claims:
    • The homepage presents Copper as Building the institutional standard for digital assets and groups Institutional custody, prime services and collateral management under one company surface
    • The homepage also calls ClearLoop The market's first off-exchange settlement solution and says institutions can trade on centralized exchanges without moving assets from Copper’s MPC custody, which is unusually explicit operator-boundary language
    • The developer introduction says Copper offers both integration guides and an OpenAPI-based API description, which matters because it shows the company expects customers to wire custody, settlement, and related operations directly into their own systems
    • The docs’ entity model spans organization, portfolio, wallet, order, loan, crypto-address, and deposit-target objects, which is much broader than a simple wallet API
    • Copper’s public llms.txt index exposes first-class API families for ClearLoop actions / balances / exchanges / settlements as well as lending, order, counterparty, and address-book operations, reinforcing that the live product is an institutional workflow graph, not a standalone protocol primitive
  • Whitepaper: No classic standalone whitepaper is the point here. The clearest primary materials remain Copper’s official website, developer portal, and the earlier primary-source capture in ../whitepapers/copper-primary-sources-2026-04-26.md.
  • Sources:

Internal linkages

  • Project-layer alias: copper.
  • Keep the comparison set on the clearest adjacent institutional operator reads: bitgo, fireblocks, and anchorage-digital.
  • Useful contrast where more authority can stay with the application operator instead of the institutional workflow vendor: turnkey.

Control surface

  • Authority sits in workspace and organization structure, wallet and address-book policy, counterparty and venue connectivity, ClearLoop settlement workflow, collateral routing, API credentials, and the operational vocabulary customers build around Copper’s platform objects.

  • The sticky dependency is not only key storage. Once orders, loans, exchange settlement, and collateral movement all run through the same company-managed object model, institutions start inheriting Copper’s workflow assumptions as part of daily operations.

  • Treat Copper as institutional operator infrastructure first. Custody is only one entry point into a broader company-run treasury, settlement, and collateral control plane.

  • Last reviewed: 2026-08-05 UTC