Copper adds Hyperliquid trading to its institutional control platform

Copper launched a Hyperliquid trading interface on 1 October, adding API and in-platform order entry to its existing HyperCore and HyperEVM support. Institutions can manage the activity alongside their other connected venues, with Copper’s permissions, approval workflows and audit trail applied to access.[1]

The operating change is in how an institution authorises and records trading. A desk can place the execution route inside its established control process, giving operations staff a common place to inspect permissions and activity. That can simplify governance without establishing that execution prices or investment outcomes have improved.

The agent can trade, but cannot withdraw

Copper’s integration guide requires a service-user API key and an activated, funded HyperCore wallet. The client acknowledges a legal addendum, then signs an MPC-wallet transaction granting an agent trading authority for up to 180 days. One agent wallet can serve each portfolio. Its authority is revocable and excludes withdrawals, but covers trading with funds in the master wallet’s HyperCore balance.[2]

That distinction gives treasury and trading teams separate control boundaries. Preventing a trading credential from withdrawing assets does not prevent it from opening losing positions or consuming margin. Portfolio allocation, instrument permissions and trading limits still determine the economic exposure entrusted to the desk.

The API schema routes an action using the client’s organisation and portfolio identifiers. The action itself follows Hyperliquid’s specification. Copper’s proxy handles the signing and nonce process described in its guide, so an existing integration retains the order instructions while changing its authentication and routing.[3][2]

The agent-wallet reference exposes portfolio identity, activation status, expiry and any pending revocation order. These fields provide a basis for checking which delegation is active and whether a requested removal remains in progress.[4]

One interface does not make every collateral pool interchangeable

The release includes access to selected tradeXYZ HIP-3 instruments referencing equities, commodities and indices. It describes a non-custodial MPC infrastructure and limits availability to eligible institutional and professional clients outside restricted jurisdictions, including the United States.[1]

Hyperliquid’s HIP-3 specification gives each deployed perpetuals market operator responsibility for contract definitions, oracle prices, leverage limits and settlement. Each deployed exchange has its own margining, order books and settings, and can use a qualifying quote asset as collateral. Cross-margin support depends on the market’s eligibility and settings.[5]

A common screen therefore needs to preserve the identity of each market, its collateral asset and the amount actually available to support its positions. A firm cannot infer from shared access that collateral committed to one deployment is freely usable on every other deployment or on a centralised exchange.

The cost comparison needs both the interface and venue charges

Copper’s guide discloses an on-chain charge for maintenance and order execution without publishing its amount on that page. A desk evaluating the route needs that contracted charge alongside the venue tariff.[2]

Hyperliquid determines tiers using rolling 14-day weighted volume. HIP-3 deployers can add a fee share, while growth mode and collateral-related discounts can alter the result. The relevant comparison is the specific instrument and client tier, rather than a single platform-wide headline rate.[6]

For an institution, the launch creates another controlled route into an existing derivatives market. The decision turns on whether the delegated authority, collateral allocation and complete execution bill fit the desk’s operating model.

Report an error or submit an update