超流动治理反馈

这封信是写给 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

除了选择的这四个验证器之外