# Canonical: https://www.uddalak.xyz/hyperliquid-academy/article/124-qualified-custody-vs-self-custody-hype
# Author: Uddalak Das
# Last source: https://www.uddalak.xyz/hyperliquid-academy/article/124-qualified-custody-vs-self-custody-hype

---
title: "Qualified Custody vs Self-Custody for HYPE"
description: "Qualified or regulated custody transfers key-control responsibilities to a regulated provider; self-custody preserves direct control but moves operational security and governance onto the institution."
pillar: "Institutional & Regulatory"
track: "Institutional & Regulatory"
cluster: "Institutional & Regulatory"
level: "Advanced"
primary_icp: ["institutional decision-maker", "fund"]
secondary_icp: ["treasury"]
content_type: "comparison"
reading_time: "3 min"
last_reviewed: "2026-09-07"
last_verified: "2026-09-07"
volatile: true
prerequisites: ["122-institutional-custody-for-hype"]
related: ["125-funds-subaccounts-api-wallets", "127-counterparty-risk-vs-smart-contract-risk-vs-protocol-risk"]
---

# Qualified Custody vs Self-Custody for HYPE

Qualified custody and self-custody are not a simple security ranking. A regulated custodian can provide legal, operational, and audit controls that many institutions require. Self-custody can provide direct protocol access and eliminate a custodian as a withdrawal gate. The correct model depends on mandate, jurisdiction, required Hyperliquid actions, and the institution's ability to operate keys safely.

## Custodian model

The institution relies on the provider's key management, internal controls, legal entity, recovery process, and supported transaction set. This can simplify governance but adds service-provider and operational dependency.

## Self-custody model

The institution controls signing infrastructure directly. It can interact with HyperCore and HyperEVM without waiting for a provider to add support, but it must design access control, key recovery, transaction policy, monitoring, and incident response itself.

## Protocol access

A provider may support HYPE custody on HyperEVM yet not every HyperCore action, staking workflow, or DeFi contract. A self-custody address has broader technical flexibility but also broader ability to make a catastrophic mistake.

## Hybrid model

Keep strategic cold reserves with a regulated custodian while allocating a bounded operational balance to policy-controlled self-custody for trading or staking. Rebalance under explicit approval limits.

This separates treasury preservation from active protocol risk.

## Decision framework

Evaluate legal requirements, bankruptcy remoteness, insurance, chain/action coverage, withdrawal SLA, policy controls, key architecture, recovery, staff capability, and capital-at-risk limits. Document why each pool of HYPE uses its selected model.

## How this connects

Start with [Institutional Custody for HYPE](/hyperliquid-academy/article/122-institutional-custody-for-hype) if the underlying concept is unfamiliar. Related reading: [How Funds Can Structure Hyperliquid Subaccounts and API Wallets](/hyperliquid-academy/article/125-funds-subaccounts-api-wallets), [Counterparty Risk vs Smart Contract Risk vs Protocol Risk on Hyperliquid](/hyperliquid-academy/article/127-counterparty-risk-vs-smart-contract-risk-vs-protocol-risk).

## Sources

- https://www.bitgo.com/resources/blog/institutional-hype-staking-now-available-at-bitgo
- https://www.sec.gov/Archives/edgar/data/1682639/000110465926095181/hypd-20260630x10q.htm