bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 27쪽 중 2쪽
nto a wallet extension (e.g., [Rabby](https://support.rabby.io/en/articles/14120234-getting-started-with-rabby-extension#h_be51e8edb6), MetaMask), and connect it to testnet. 
# HyperCore
# Overview
### Consensus
Hyperliquid is secured by HyperBFT, a variant of HotStuff consensus. Like most proof-of-stake chains, blocks are produced by validators in proportion to the native token staked to each validator. 
### Execution
The Hyperliquid state consists of HyperCore and the general purpose HyperEVM. 
HyperCore includes margin and matching engine state. Importantly, HyperCore does not rely on the crutch of off-chain order books. A core design principle is full decentralization with one consistent order of transactions achieved through HyperBFT consensus. 
### Latency
Consensus currently uses an optimized consensus algorithm called HyperBFT, which is optimized for end-to-end latency. End-to-end latency is measured as duration between sending request and receiving committed response. 
For an order placed from a geographically co-located client, end-to-end latency has a median 0.2 seconds and 99th percentile 0.9 seconds. This performance allows users to port over automated strategies from other crypto venues with minimal changes and gives retail users instant feedback through the UI.
### Throughput
Mainnet currently supports approximately 200k orders/sec. The current bottleneck is execution. The consensus algorithm and networking stack can scale to millions of orders per second once the execution can keep up. There are plans to further optimize the execution logic once the need arises. 
# USDC
USDC is natively minted on the Hyperliquid L1. Circle's contracts on HyperEVM can be found here: [https://hyperevmscan.io/token/0xb88339cb7199b77e23db6e890353e22632ba630f](https://hyperevmscan.io/token/0xb88339cb7199b77e23db6e890353e22632ba630f#transactions).
See <https://developers.circle.com/cctp/howtos/transfer-usdc-from-arbitrum-to-hypercore> for Circle's documentation on Arbitrum to HyperCore CCTP transfers.
The legacy Arbitrum bridge holds less than 10% of the USDC supply on HyperCore. The legacy bridge and its logic in relation to the L1 staking have been audited by Zellic. See the Hyperliquid GitHub repository for the full bridge code, and the [Audits](/hyperliquid-docs/audits) section for the audit reports.
# API servers
API servers listen to updates from a node and maintain the blockchain state locally. The API server serves information about this state and also forwards user transactions to the node. The API serves two sources of data: REST and WebSocket. 
When user transactions are sent to an API server, they are forwarded to the connected node, which then gossips the transaction as part of the HyperBFT consensus algorithm. Once the transaction has been included in a committed block on the L1, the API server responds to the original request with the execution response from the L1.
# Clearinghouse
The perps clearinghouse is a component of the execution state on HyperCore. It manages the perps margin state for each address, which includes balance and positions. 
Deposits are first credited to an address's cross margin balance. Positions by default are also opened in cross margin mode. Isolated margin is also supported, which allows users to allocate margin towards a specific position, disassociating the liquidation risk of that position from all other positions.
The spot clearinghouse analogously manages spot user state for each address, including token balances and holds.
# Oracle
The validators are responsible for publishing spot oracle prices for each perp asset every 3 seconds. The oracle prices are used to compute funding rates. They are also a component in the `mark price` which is used for margining, liquidations, and triggering TP/SL orders.
The spot oracle prices are computed by each validator as the weighted median of Binance, OKX, Bybit, Kraken, Kucoin, Gate IO, MEXC, and Hyperliquid spot mid prices for each asset, with weights 3, 2, 2, 1, 1, 1, 1, 1 respectively. Perps on assets which have primary spot liquidity on Hyperliquid (e.g. HYPE) do not include external sources in the oracle until sufficient liquidity is met. Perps on assets that have primary spot liquidity outside of Hyperliquid (e.g. BTC) do not include Hyperliquid spot prices in the oracle.
The final oracle price used by the clearinghouse is the weighted median of each validator's submitted oracle prices, where the validators are weighted by their stake.
# Order book
HyperCore state includes an order book for each asset. The order book works similarly to that of centralized exchanges. Orders are added where price is an integer multiple of the tick size, and size is an integer multiple of lot size. Orders are matched in price-time priority.
Operations on order books for perp assets take a reference to the clearinghouse, as all positions and margin checks are handled there. Margin checks happen on the opening of a new order, and again for the resting side at the matching of each order. This ensures that the margining system is consistent despite oracle price fluctuations after the resting order is placed.
One unique aspect of the Hyperliquid L1 is that the mempool and consensus logic are semantically aware of transactions that interact with HyperCore order books. Within a block, actions are sorted within each consensus batch (there are usually 1-2 consensus batches of actions in a block) as
1. Actions that do not send GTC or IOC orders to any book
2. Cancels
3. Actions that send at least one GTC or IOC
Within each category, actions are sorted in the order they were proposed by the block proposer. Modifies are categorized according to the new order they place.  
# Staking
### Basics
HYPE staking on Hyperliquid happens within HyperCore. Just as USDC can be transferred between perps and spot accounts, HYPE can be transferred between spot and staking accounts. 
Within the staking account, HYPE may be staked to any number of validators. Here and in other docs, *delegate* and *stake* are used interchangeably, as Hyperliquid only supports delegated proof-of-stake. 
Each validator has a self-delegation requirement of 10k HYPE to become active. The self-delegation requirement is locked for one year. Any time that the self-delegation for a validator drops below 10k HYPE, the validator enters undelegate-only mode (i.e., where all future delegations to this validator are disabled), so the validator's total stake can only decrease going forward. 
Once active, validators produce blocks and receive rewards proportional to their total delegated stake. Validators may charge a commission to their delegators. This commission cannot be increased unless the new commission is less than or equal to 1%. This prevents scenarios where a validator attracts a large amount of stake and then raises the commission significantly to take advantage of unaware stakers.
Delegations to a particular validator have a lockup duration of 1 day. After this lockup, delegations may be partially or fully undelegated at any time. Undelegated balances instantly reflect in staking account balance. 
Transfers from spot account to staking account are instant. However, transfers from staking account to spot account have a 7 day unstaking queue. Most other proof-of-stake chains have a similar mechanism, which ensures that large-scale consensus attacks are penalized by slashing or social layer mechanisms. There is currently no automatic slashing implemented. Each address may have at most 5 pending withdrawals in the unstaking queue. 
As an example, if you initiate a staking to spot transfer of 100 HYPE at 08:00:00 UTC on March 11 and a transfer of 50 HYPE at 09:00:00 UTC on March 12, the 100 HYPE transfer will be finalized at 08:00:01 UTC on March 18 and the 50 HYPE transfer will be finalized at 09:00:01 UTC on March 19. 
The staking reward rate formula is inspired by Ethereum, where the reward rate is inversely proportional to the square root of total HYPE staked. At 400M total HYPE staked, the reward rate is approximately 2.37% per year. Staking rewards come from the future emissions reserve.
Rewards are accrued every minute and distributed to stakers every day. Rewards are redelegated automatically to the staked validator, i.e., compounded. Rewards are based on the minimum balance that a delegator has staked during each staking epoch (100k rounds, as explained below).
### Technical Details
The notion of a *quorum* is essential to modern proof-of-stake consensus algorithms such as HyperBFT. A quorum is any set of validators that has more than ⅔ of the total stake in the network. The operating requirement of consensus is that a quorum of stake is honest (non-Byzantine). Therefore it is an essential responsibility of every staker to only delegate to trusted validators. 
HyperBFT consensus proceeds in *rounds*, which is a fundamental discrete bundle of transactions along with signatures from a quorum of validators. Each *round* may be *committed* after certain conditions are met, after which it is sent to the execution state for processing. A key property of the consensus algorithm is that all honest nodes agree on the ordered list of committed rounds.
Rounds may result in a new execution state block. Execution blocks are indexed by a separate increasing counter called *height*. Height only increments on consensus rounds with at least one transaction.
The validator set evolves in epochs of 100k rounds, which is approximately 90 minutes on mainnet. The validators and consensus stakes are static for each staking epoch.
Validators may vote to jail peers that do not respond with adequate latency or frequency to the consensus messages of the voter. Upon receiving a quorum of jail votes, a validator becomes *jailed* and no longer participates in consensus. A jailed validator does not produce rewards for its delegators. A validator may unjail itself by diagnosing and fixing the causes, subject to onchain unjailing rate limits. Note that jailing is not the same as slashing, which is reserved for provably malicious behavior such as double-signing blocks at the same round. 
# Vaults
Vaults are a general case of the powerful functionality that HyperEVM enables via CoreWriter and precompiles. Builders can create and tokenize vaults on the HyperEVM with fully customizable accounting. Builders can follow specs such as <https://eips.ethereum.org/EIPS/eip-4626> with the added benefit of trustless read and write operations on HyperCore. For example, vaults can trade onchain via CoreWriter, or they can delegate any number of authorized agents using CoreWriter. The net result is fully onchain accounting via precompiles, and full access to Core features including spot and HIP-3 in all quote assets. 
This is a strict improvement over the "legacy" HyperCore vaults, which were introduced in 2023 and do not support HIP-3 or spot trading.
# Protocol vaults
Hyperliquidity Provider (HLP) is a protocol vault that provides liquidity to Hyperliquid through multiple market making strategies, performs liquidations, supplies USDC in Earn, and accrues a portion of trading fees.
HLP democratizes strategies typically reserved for privileged parties on other exchanges. The community can provide liquidity for the vault and share its pnl. HLP is fully community-owned.
The deposit lock-up period is 4 days. This means you can withdraw 4 days after your most recent deposit. E.g., if you deposited on Sep 14 at 08:00, you would be able to withdraw on Sep 18 at 08:00.
# HyperCore vaults (legacy)
HyperCore supports a limited set of functionality for onchain vaults, but additional features should be built permissionlessly by builders on the HyperEVM. See [here](/hyperliquid-docs/hypercore/vaults) for more details.
Vault owners receive 10% of the total profits. Note that protocol vaults do not have any fees or profit share. Vaults can be managed by an individual trader or automated by a market maker. All strategies come with their own risk, and users should carefully assess the risks and performance history of a vault before depositing.  
# For vault leaders (legacy)
### What are the benefits of creating a vault as a leader?
Vault leaders receive a 10% profit share for managing the vault. Traders can share their approach to trading with their community via vaults.  
### How do I create a vault?
Anyone can create a vault: 
1. Choose a name and write a description for your vault. Note that this cannot be changed later. 
2. Deposit a minimum of 100 USDC into your vault.
Creating a vault requires a 10k USDC gas fee, which is distributed to the protocol in the same manner as trading fees.
To ensure vault leaders have skin in the game, you must maintain ≥5% of the vault at all times. You cannot withdraw from your vault if it would cause your share to fall below 5%. 
### How do I manage my vault?
On the Trade page, select the address dropdown in the navigation bar. Select the vault you want to trade on behalf of in the dropdown. Now, all trades you make will apply to your vault, and everything on the Trade page will reflect your vault. 
To switch back to your personal account, select "Master" at the top of the address dropdown.  
### What assets can a vault trade? 
Vaults can trade validator-operated perps. They cannot trade spot or HIP-3 perps. 
### How do I close my vault?
On your vault’s dedicated page, click the Leader Actions dropdown and select “Close Vault.” A modal will appear to confirm that you want to close your vault. All positions must be closed before the vault can close. All depositors will receive their share of the vault when it is closed.
### What happens to open positions in a vault when someone withdraws?
When someone withdraws from a vault, if there is enough margin to keep the open positions according to the leverages set, the withdrawal does not affect open positions.
If there is not enough margin available, open orders that are using margin will be canceled. Orders will be canceled in increasing order of margin used.  
If there is still not enough margin available, 20% of positions are automatically closed. This is repeated until enough margin is freed up such that the user's withdrawal can be processed. Vault leaders can also set vaults to always proportionally close positions on withdrawals to maintain similar liquidation prices for positions.
# For vault depositors (legacy)
### What are the benefits of depositing into a vault?
By depositing, you earn a share of the profits, or losses, of the vault. You can deposit into the vault of a specific trader to get exposure to their trading approach.  
Let’s say you deposit 100 USDC into a vault, whose total deposits are 900 USDC. The vault total is now 1,000 USDC, and you represent 10% of the vault. Over time, the vault grows to be 2,000 USDC, while no one else has deposited or withdrawn from the vault. You withdraw 200 USDC (10%) less 10 USDC (10% profit share to the leader), which totals 190 USDC. There may be some slippage as you withdraw and open positions are closed. 
Note that trading is inherently risky, and vaults’ past performance is not a guarantee of future returns. 
### How do I find a vault to deposit into?
On <https://app.hyperliquid.xyz/vaults>, you can view statistics of different vaults, including APY and total deposits (TVL). 
You can click on a specific vault to see more information, such as pnl, max drawdown, volume, open positions, and trade history. You can see how many people have deposited into the vault and for how long they’ve been supporting the vault. 
### How do I deposit into a vault?
On a vault’s dedicated page, click the Deposit button, then enter the amount you would like to deposit and click “Deposit.”
### How do I check the performance of vaults I’ve deposited into?
You can track any vault’s performance on its dedicated page. Select the “Your Performance” heading to see how your deposits have performed. 
On the Portfolio page, you’ll find your total balance across all vaults. 
### How do I withdraw from a vault?
On a vault’s dedicated page, click the Withdraw button, then enter the amount you would like to withdraw and click “Withdraw.”
HLP has a lock-up period of 4 days. User vaults have a lock-up period of 1 day. 
# Multi-sig
Advanced Feature
HyperCore supports native multi-sig actions. This allows multiple private keys to control a single account for additional security. Unlike other chains, multi-sig is available as a built-in primitive on HyperCore as opposed to relying on smart contracts. 
The multi-sig workflow is described below:
* To convert a user to a multi-sig user, the user sends a `ConvertToMultiSigUser` action with the authorized users and the minimum number of authorized users required to sign an action. Authorized users must be existing users on Hyperliquid. Once a user has been converted into a multi-sig user, all its actions must be sent via multi-sig. 
* To send an action, each authorized user must sign a payload to produce a signature. A `MultiSig` action wraps around any normal action and includes a list of signatures from authorized users. 
* The `MultiSig` payload also contains the target multi-sig user and the authorized user who will ultimately send the `MultiSig` action to the blockchain. The sender of the final action is also known as the `leader` (transaction lead address) of the multi-sig action.
* When a multi-sig action is sent, only the nonce set of the authorized user who sent the transaction is validated and updated.
* Similar to normal actions, the leader can also be an API wallet of an authorized user. In this case, the nonce of the API wallet is checked and updated. 
* A multi-sig user's set of authorized users and/or the threshold may be updated by sending a `MultiSig` action wrapping a `ConvertToMultiSigUser` action describing the new state.
* A multi-sig user can be converted back to a normal user by sending a `ConvertToMultiSigUser` via multi-sig. In this case, the set of authorized users can be set to empty and conversion to a normal user will be performed.
Miscellaneous notes: 
* The leader (transaction lead address) must be an authorized user, not the multi-sig account
* Each signature must use the same information, e.g., same nonce, transaction lead address, etc. 
* The leader must collect all signatures before submitting the action 
* A user can be a multi-sig user and an authorized user for another multi-sig user at the same time. A user may be an authorized user for multiple multi-sig users. The maximum allowed number of authorized users for a given multi-sig user is 10. 
Important for HyperEVM users: Converting a user to a multi-sig still leaves the HyperEVM user controllable by the original wallet. CoreWriter does not work for multi-sig users. In general, multi-sig users should not interact with the HyperEVM before or after conversion.
See the Python SDK for code examples.
# Permissionless spot quote assets
Becoming a spot quote asset is permissionless. 
The requirements for becoming a permissionless spot quote asset are as follows:
1. Wei decimals of 8 and size decimals of 2
2. Zero deployer fee share on the quote token
3. 200k HYPE staked, subject to the following slashing criteria based on validator voting: 
1. A peg mechanism to a price of 1 USD. A future network upgrade could increase the scope to other non-dollar stable assets 
1. QUOTE/USDC should have 100k USDC size on both sides within the price range from 0.998 to 1.002, inclusive 
2. QUOTE/USDC should have 1M USDC size on both sides within 0.99 and 1.01, inclusive 
2. A liquid HYPE/QUOTE boo프로젝트로 돌아가기