> For the complete documentation index, see [llms.txt](https://docs.v2.like.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v2.like.co/zh/general-guides/governance/what-is-a-validator.md).
# 驗證人
驗證人 ( Validators ) 是什麼？
{% hint style="warning" %}
此文檔只適用於 Liker Land 和 LikeCoin v2。如需了解 [3ook.com](http://3ook.com/) 和 LikeCoin v3，請至 [docs.3ook.com](http://docs.3ook.com/) 及 [dao.like.co](https://dao.like.co/)。
{% endhint %}
## 銀行+立委
[LikeCoin](https://like.co/) DAO 的驗證人同時擔當「銀行」及「立法委員」的角色。
驗證人 ( Validators ) 負責 7x24 營運伺服器群以核實所有 Likers 的資料記錄，包括代幣轉賬、內容發佈、投票動作等。LikeCoin DAO 的驗證人同時擔當銀行及立法委員的角色。
### **負責記帳（銀行）**
傳統做法，我們需要一些有公信力的機構，例如銀行或政府，收取服務費去處理帳目記錄。在 LikeCoin DAO，帳目以分散對等的方式，由 Likers 授權的「驗證人」負責記錄，每筆操作只需 5 秒且成本極低。
### **負責動議及投票（立法委員）**
Likers 透過委託的方法授權給驗證人。委託 LikeCoin 代表 Liker 信任驗證人的技術能力、知識及誠信，並同意由他代表。
{% content-ref url="/pages/-MjCyIwTkfX8KgrzJpFy" %}
[持份者直接投票](/zh/general-guides/governance/direct-vote.md)
{% endcontent-ref %}
## 驗證人狀態
### 活躍驗證人 ( Active Validator)
履行[驗證交易](/zh/general-guides/dapp/background.md#9e68)責任，並在 LikeCoin DAO 憲法界定下的活躍驗證人數目內獲得最多委託的驗證人。
### 閒置驗證人 ( Inactive Validator )
驗證人並無履行驗證交易責任正在「坐牢」( Jailed ) ，又或者在 LikeCoin DAO 憲法界定下的活躍驗證人數目以外，委託量不足的驗證人。
## 成為驗證人
{% content-ref url="/pages/1FlUlQTNg5T2scMAvPTj" %}
[成為驗證人](/zh/general-guides/governance/what-is-a-validator/become-a-validator.md)
{% endcontent-ref %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.v2.like.co/zh/general-guides/governance/what-is-a-validator.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.