超流動治理回饋

這封信是寫給 Hyperliquid 開發團隊的，希望團隊能花時間審查 Hyperliquid 區塊鏈治理的回饋。

This letter is addressed to the Hyperliquid development team, hoping that the team can take the time to review this feedback regarding the governance of the Hyperliquid blockchain.

這封信是寫給 Hyperliquid 開發團隊的，希望團隊能花時間審查 Hyperliquid 區塊鏈治理的回饋。

I started using Hyperliquid in December 2023 and it is an amazing crypto app. It is easy to use, has a great user experience, and offers some unique features like the vault and the famous HLP. Currently, HLP has over $350 million in assets under management, and anyone can participate in Hyperliquid in a passive way.

我於 2023 年 12 月開始使用 Hyperliquid，這是一款令人驚嘆的加密應用程式。它易於使用，具有出色的用戶體驗，並提供一些獨特的功能，例如保險庫和著名的 HLP。目前，HLP 管理的資產超過 3.5 億美元，任何人都可以被動參與 Hyperliquid。

After seeing how great the platform is and knowing that Hyperliquid is running as its own L1 blockchain, I wanted Chorus One (Staking Solutions) to participate as an operator on the Hyperliquid chain. I am an employee of Chorus One, one of the largest node operators in the space. Chorus One has been active in the Proof of Stake industry since 2018.

在看到這個平台有多出色並知道 Hyperliquid 正在作為自己的 L1 區塊鏈運行後，我希望 Chorus One（質押解決方案）作為 Hyperliquid 鏈上的運營商參與其中。我是 Chorus One 的員工，該公司是該領域最大的節點營運商之一。 Chorus One 自 2018 年以來一直活躍在權益證明行業。

Chorus One joined the Hyperliquid testnet after being whitelisted on October 17 last year. I wanted to share our overall experience on the testnet with the Hyperliquid engineering team, as we have not had the opportunity to interact with them even after joining the testnet for nearly 3 months.

Chorus One 在去年 10 月 17 日被列入白名單後加入了 Hyperliquid 測試網。我想與 Hyperliquid 工程團隊分享我們在測試網路上的整體經驗，因為即使加入測試網近 3 個月了，我們也沒有機會與他們互動。

During this time, we have witnessed one of the most successful token launches of 2024: the launch of the HYPE token. At the same time, we have also experienced an interesting and challenging testnet environment. I would like to mention some of the issues I observed, and I hope that these issues will be addressed in the coming days, weeks, or months.

在此期間，我們見證了 2024 年最成功的代幣發行之一：HYPE 代幣的發行。同時，我們也經歷了有趣且富有挑戰性的測試網環境。我想提一下我觀察到的一些問題，我希望這些問題能在未來幾天、幾週或幾個月內解決。

**Testnet Experience**

**測試網體驗**

The testnet experience has been extremely challenging so far. Operators have little knowledge of how to run a node, and the resources available are limited. In addition to this, we are basically exploring in the dark, and we have found multiple issues, including the following:

到目前為止，測試網的體驗極具挑戰性。營運商對如何運行節點知之甚少，可用資源也有限。除此之外，我們基本上都在摸索，發現了多個問題，包括以下幾個：

* Frequent jail time for unknown reasons

* 常因不明原因入獄

At first, we were jailed multiple times, but we didn’t understand why. Since the code was not open source, we couldn’t accurately assess the reasons. The only thing we could do was to communicate with other validators on Discord and guess the reasons together. After talking to multiple validators, we found that everyone was jailed frequently, and they didn’t fully understand why.

起初，我們多次入獄，但我們不明白為什麼。由於程式碼未開源，我們無法準確評估原因。我們唯一能做的就是與 Discord 上的其他驗證者進行溝通，共同猜測原因。在與多個驗證者交談後，我們發現每個人都經常被監禁，但他們並不完全理解為什麼。

* Node location

* 節點位置

We later discovered that the jailing issue was probably because we didn’t run a node in Tokyo. Moving the node to Tokyo might have helped. Unfortunately, the team never made this clear and we only discovered this after running into a lot of issues.

我們後來發現，監禁問題可能是因為我們沒有在東京運行節點。將節點移至東京可能會有所幫助。不幸的是，團隊從未明確說明這一點，我們只是在遇到很多問題後才發現這一點。

After moving the node to Tokyo, the situation improved. This is probably because many testnet nodes with a large amount of staked tokens are also located in Tokyo, so our node can miss fewer blocks and keep up with the pace. However, even after moving the node, we still continue to encounter jail time issues, and we still don’t know the exact reason. This problem is mainly due to the fact that the code is not open source.

將節點移至東京後，情況有所改善。這可能是因為許多擁有大量質押代幣的測試網節點也位於東京，因此我們的節點可以錯過更少的區塊並跟上步伐。然而，即使在移動節點之後，我們仍然繼續遇到監獄時間問題，而且我們仍然不知道確切的原因。這個問題主要是因為程式碼不開源造成的。

* Depends on the automatic jailbreak script

* 取決於自動越獄腳本

We realized that maintaining good uptime on the Hyperliquid testnet depended on how quickly the script could automatically jailbreak nodes. The only way to improve uptime was to rely on scripts that could automatically jailbreak nodes quickly. Validators could not fully understand or fix the underlying issue and could only automatically jailbreak nodes without a deep understanding.

我們意識到，在 Hyperliquid 測試網路上保持良好的正常運行時間取決於腳本自動越獄節點的速度。提高正常運行時間的唯一方法是依靠可以快速自動越獄節點的腳本。驗證者無法完全理解或修復根本問題，只能在沒有深入理解的情況下自動越獄節點。

* Centralized Hyperliquid API as a single point of failure

* 集中式 Hyperliquid API 作為單點故障

On several occasions, our jailbreak attempts failed because the Hyperliquid API was down. If the API is down, validators cannot get out of jail on their own because they have to send a request to the Hyperliquid server to get out.

有幾次，我們的越獄嘗試失敗了，因為 Hyperliquid API 已關閉。如果 API 宕機，驗證者無法自行越獄，因為他們必須向 Hyperliquid 伺服器發送請求才能越獄。

The team may be aware of this, but this design needs to be reconsidered because it makes the API a major single point of failure for the network. If the goal is to build a Byzantine fault-tolerant system, there should not be any nodes with special permissions, such as those that rely on a centralized API.

團隊可能意識到了這一點，但這種設計需要重新考慮，因為它使 API 成為網路的主要單點故障。如果目標是建構拜占庭容錯系統，則不應存在任何具有特殊權限的節點，例如依賴集中式 API 的節點。

**Mainnet Validator Selection**

**主網驗證者選擇**

Hyperliquid recently selected about 16 validators in the process of decentralizing its validator set. Previously, Hyperliquid was managed by 4 validators from the core team, which attracted a lot of criticism. Recently, Hyperliquid took a major step and expanded the number of validators from 4 to 16.

Hyperliquid 最近在去中心化其驗證器集的過程中選擇了大約 16 個驗證器。在此之前，Hyperliquid 由核心團隊的 4 名驗證者管理，這引起了許多批評。最近，Hyperliquid 邁出了重大一步，將驗證器的數量從 4 個擴大到 16 個。

Regarding the selection of validators, 4 validators were announced via the following post on Discord:

關於驗證人的選擇，4 位驗證者透過 Discord 上的以下貼文公佈：

```

````

The four validators are Validao, Bharvest, Hypurrstake, and Prrposefulnode. They were selected based on uptime, and they have managed to maintain more than 90% uptime in the past 7 or 30 days.

這四個驗證器分別是 Validao、Bharvest、Hypurrstake 和 Prrposefulnode。他們是根據正常運行時間選擇的，並且在過去 7 或 30 天內成功保持了 90% 以上的正常運行時間。

This is a remarkable achievement for many reasons, primarily because validator performance is also impacted by external factors, such as glitches in the Hyperliquid API, jail issues, and persistent binary crashes, which all have a significant impact on performance.

出於多種原因，這是一項了不起的成就，主要是因為驗證器效能也受到外部因素的影響，例如 Hyperliquid API 中的故障、監獄問題和持續的二進位崩潰，這些都會對效能產生重大影響。

```

````

In addition to these four validators selected

除了選擇的這四個驗證器之外