Copper Integration for Trading Firms That Use ClearLoop
Firms that custody assets at Copper and trade through ClearLoop need their own ledger to book each delegation and settlement instruction. Copper leaves that booking to them, along with requesting trading-vault signatures in time. Protofire builds both. In 2021 we built the DEX core and subgraph for Swarm Markets.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
ClearLoop delegations and what your ledger must show
Copper's screens show each ClearLoop movement, and your Copper integration decides what that movement means in your books. For example, your desk delegates assets to an exchange before the morning's trading. By lunch your ledger has to say what you hold, and where.
Copper keeps delegated assets in custody, in vaults whose keys are split into three shards (Copper). The exchange credits a virtual balance to trade, and "no actual transfer occurs until settlement" (Copper). Settlement follows at intervals of 2, 4 or 24 hours, depending on the exchange.
Who runs each part of a ClearLoop cycle
Each delegation into Copper follows your limits, and you trade the virtual balance. ClearLoop then settles the exchange's P&L back into custody. Your ledger receives each movement through settlement records and webhooks.
Desk and ledger
Account Controllers and your shard
Vaults and ClearLoop settlement
Connected exchange
Delegation orders
Settlement booking and signature requests
Webhook intake and order polling
Why ClearLoop positions are hard to book
A ClearLoop delegation appears as a withdrawal order, a locked amount in the wallet record and a virtual balance at the exchange.Copper sends a delegation as a withdrawal order paired with a deposit order (Copper). Read alone, the withdrawal looks like money leaving. The locked field covers "the funds delegated to all sub-accounts" (Copper). If your ledger counts that locked amount beside the virtual balance, the position doubles.
At the end of each cycle, ClearLoop returns a settlement instruction per client account and currency. The P&L comes from the exchange, and Copper states that "Copper does not act as a calculation agent" (Copper). An account can also be left out of a cycle. One documented reason is "Trading vault signature required on previous settlement" (Copper). Your ledger books each instruction or records why it is missing.
Between cycles, gains and losses exist on the exchange's books alone. Copper's disclosures say your firm remains "subject to counterparty and settlement risk in relation to any unsettled profits" (Copper). If your ledger records no amount due from or to the exchange, that exposure is visible only on a screen. Finance may then have to rebuild the position by hand at month-end.
In March 2023, Copper wrote that it holds ClearLoop assets in a trust setup (Copper). The trust setup is meant to govern how the assets are returned if a connected exchange or Copper becomes insolvent. How it applies to your firm is a reading your counsel makes against your ClearLoop agreement.
What Copper returns for ClearLoop and what you book
Copper returns each ClearLoop move as orders and settlement records with their own IDs.Your ledger decides what each record means.
Delegation
What Copper returns: Copper sends two linked orders, a withdrawal and a deposit, joined by withdrawOrderId and depositOrderId.
What your books record: The pair is booked as one internal move keyed on both IDs, so the asset remains a Copper holding marked as delegated.
Settlement P&L
What Copper returns: The exchange calculates the P&L, and Copper returns a settlementInstructionId per client account, currency and cycle (docs).
What your books record: Each instruction gets one posting, matched to the exchange's statement for the same window.
Exclusions
What Copper returns: When an account is left out of a cycle, for example for a frozen portfolio, Copper returns an exclusionReason and an exclusionSettlementId.
What your books record: The desk gets an alert, and an open item remains until that settlement record shows its order complete.
Delegated balance
What Copper returns: Copper's totals "may not immediately reflect recent activity on the exchange" (docs).
What your books record: A delegated position is kept per exchange and checked against Copper's figure, with its possible lag in mind.
Copper custody and ClearLoop facts
- Custody model
- Each vault key has three shards, held by the client, Copper and a third party, and two are needed to sign. A Policy Engine covers roles, limits, time windows and approvals (Copper).
- ClearLoop
- Delegated funds are locked at Copper, and the exchange shows a virtual balance. Settlement runs at intervals of 2, 4 or 24 hours, depending on the exchange (docs). Copper's Swiss site listed eight ClearLoop exchanges in November 2026 (Copper).
- United States
- Copper Markets (US), Inc. is a broker-dealer registered with the SEC, a member of FINRA and a member of SIPC (Copper).
- Rate limits
- Copper allows 1,000 requests per 5 minutes per user and organization (docs).
Checked November 2026 against Copper's developer documentation and its disclosures. Protofire integrates Copper for firms that have chosen it.
What Protofire builds for your Copper integration
Delegations booked as internal moves
Each delegation becomes one internal move, so the asset remains a Copper holding marked as delegated to one exchange. Protofire builds the delegation service, which creates orders within your limits per exchange. Each order has an externalOrderId. Before the service sends a timed-out order again, it looks that order up.
Settlement instructions booked once, with exclusion reasons
Each settlement instruction is booked once. An account left out of a cycle is recorded with Copper's own reason. Protofire builds the settlement booking, which matches each instruction to the exchange's report and keeps a break list for exclusions.
Trading-vault signatures requested before the next cycle
Settlements from a trading vault need your signature (docs). A missing signature excludes the account from the next cycle. Protofire builds a relay that spots the waiting order and asks your signer. Each request is logged with the time it was answered.
Policy Engine rules from your mandate register
Your mandate register becomes Policy Engine roles, limits, time windows and approvals, and your Account Controllers enter them. Each automated job gets its own service account. Protofire runs the whole set on Copper's demo environment first.
Order states recorded even when a webhook is lost
Protofire builds a receiver that verifies the signature of each webhook. A poll of orders by updatedSince runs beside the receiver. Both write to one store that drops repeats, and the polling is kept within Copper's rate limit.
Month-end balance reports at your local cut-off
Copper's Balance Report runs per portfolio and takes a dateFrom and dateTo window in UTC milliseconds (docs). So your local cut-off is converted first. Wallet reads pass a portfolioId, and ClearLoop's locked amounts are shown apart from free balances.
Who holds the key shards and approvals
Copper, a third party and your firm each hold one shard of a vault key.Two of the three shards sign a transfer (Copper). Hot vault transactions are signed automatically. Cold vault transactions "require client-side and Copper authorization", so the vault setup decides whether someone at your firm acts before each signature.
You export your shard from CU Desktop as a password-encrypted backup. You then mount the shard in Copper Unlimited Online, which listens on port 3010 (docs). The host, the backup file and the password are kept in your infrastructure. Your security team owns patching, access and backups. Port 3010 has no authentication of its own, so your network admits only your signer (docs).
Protofire's operators read through a service account. Your Account Controllers pick the permissions of that service account on the Copper Platform. After launch, Protofire holds no Account Controller role and no Approver permission. Protofire also holds no key shard, shard password or master password. Your runbook names who holds the master password.
Our record: the Swarm Markets DEX core and subgraph
Protofire's record covers a venue's trading core and its data layer.
A DEX core and subgraph for Swarm Markets, 2021
In 2021 we built the DEX core, a Balancer-fork AMM, and the subgraph of Swarm Markets and contributed to dOTC.At launch, Swarm Markets was a BaFin-licensed DEX where only KYC-verified wallets could trade. Swarm held the license and ran KYC and permissioning.
Steps to the first booked ClearLoop cycle
- Step 1
First, the settlement schedule and the booking
Protofire's booking service reads each exchange's settlement frequency and nextSettlementTimestamp from GET /clearloop/exchanges and stores both. It then books each instruction once per settlementInstructionId, as an amount due from or to the exchange. If the exchange lacks collateral for all clients, Copper issues a margin call. Client orders then "remain pending until the exchange tops up its account" (Copper). Until the exchange tops up, the ledger records the amount as unsettled with that exchange. - Step 2
Next, delegation orders and signature requests
A delegation change still in progress at cycle time is itself an exclusion reason: "Delegation or undelegation in progress" (docs). So the delegation service keeps new delegations clear of the next settlement. Protofire's signing relay watches for orders that are waiting for your signer. - Step 3
Partial and failed cycles are handled before launch
A cycle can end partially completed, failed or excluded. Each open instruction remains on the break list until a later read shows its order complete. Attribution windows run in UTC milliseconds, so a firm that closes on local time maps each instruction to a business day. - Step 4
Your staff enter the exchange API keys
Your own staff enter the exchange API keys that bind each ClearLoop account in the Copper Platform.
How a Copper project with Protofire starts
You send us the exchanges you bind to ClearLoop, your Copper account structure and the ledger that the settlement instructions must reach.The delegation service and the signing relay run in your environment. Both use API keys of service accounts that only your Account Controllers can create, and your staff keep those keys. Both services act within the limits that your Account Controllers set. If Protofire operates a service once it is live, a written scope limits that service to reading settlements, receiving events and producing balance reports.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
Copper setups that Alloy, Wyden or the Copper Platform already cover
Some Copper setups already run their ClearLoop work through a trading platform or the Copper Platform screens.An integration project adds little to those setups.
- Your portfolio and order management runs on Alloy. Since October 2024, Alloy lets clients "manage both Copper Custody and access ClearLoop directly within Alloy" (Copper, 2 October 2024).
- Your desk trades on Wyden, which integrated Copper's custody and ClearLoop in October 2023 (Copper, 31 October 2023).
- You delegate a few times a week. The Copper Platform interface offers delegation and the settlement-cycle view.
Protofire holds no financial or crypto-asset license. How Copper's regulatory status applies to your custody, and the structure of your ClearLoop agreement, are for your counsel.
FAQ
What is a Copper integration?
Who can build a Copper integration for a trading firm?
Why was our account left out of a ClearLoop settlement cycle?
Why can we undelegate less than the exchange shows?
Do delegated assets leave Copper?
Can we get Copper balances at our own month-end cut-off?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
