11.2 奇亚矿池协议 1.0 规范

Chia Pool Protocol 1.0 Specification

这是奇亚矿池协议的初始版本。它被设计成简单的，以后会被扩展。它依赖于拥有智能币（在 GUI + CLI 中称为图块 NFT）的农民，这允许他们通过在区块链上进行交易来在池之间切换。此外，它减少了对区块生产池的依赖，因为该协议只处理奖励的分配，并且可以防止矿池或农民的恶意行为。

原文参考

This is the initial version of the Chia Pool Protocol. It is designed to be simple, and to be extended later. It relies on farmers having smart coins (referred to as plot NFTs in GUI + CLI) which allow them to switch between pools by making transactions on the blockchain. Furthermore, it decreases the reliance on pools for block production, since the protocol only handles distribution of rewards, and it protects against pools or farmers acting maliciously.

安全考虑#

矿池必须确保部分快速到达，快于包含到区块链中的 28 秒时间限制。这允许设置缓慢的农民检测问题。

池服务器必须检查 pool_contract_puzzle_hash aka 是否 p2_singleton_puzzle_hash 与他们期望的谜语匹配。否则，矿池无法保证用户不会尝试为自己索取区块奖励，并立即离开矿池，这是提供的智能合约所阻止的。

奇亚客户端必须仅通过 TLS >= 1.2 上的 HTTPS 连接到池配置 URL。这是为了防止会话劫持，导致用户资金被盗。

原文参考

Security considerations#

The pool must ensure that partials arrive quickly, faster than the 28 second time limit of inclusion into the blockchain. This allows farmers that have slow setups to detect issues.

The Pool server must check that the pool_contract_puzzle_hash a.k.a. p2_singleton_puzzle_hash matches the puzzle that they expect. Otherwise, the pool has no guarantee that users will not attempt to claim block rewards for themselves, and immediately leave the pool, something that the provided smart contract prevents.

The Chia client must only connect to the pool configuration URL via HTTPS over TLS >= 1.2. This is to prevent session hijacking, leading to user funds being stolen.

部分#

参与矿池协议的各方是池运营商和农民。每个农民都在运行一个农民进程，以及连接到该农民进程的任意数量的收割机进程。完整节点可以由农民运行（奇亚 GUI 应用程序中的默认设置），也可以由矿池操作员运行。如果农民不想运行全节点，他们可以配置他们的节点以连接到远程全节点。

矿池运营商可以支持任意数量的农民。

原文参考

Parties#

The parties involved in the pool protocol are the pool operator and farmers. Each farmer is running a farmer process, and any number of harvester processes connected to that farmer process. The full node can either be run by the farmer (the default in the Chia GUI application), or run by the pool operator. If the farmer does not want to run a full node, they can configure their node to connect to a remote full node.

A pool operator can support any number of farmers.

农民身份#

一个农民可以通过区块链上农民单例硬币的标识符来唯一标识，这就是 launcher_id 所指。该 launcher_id 可被用作在一个数据库中的主密钥。矿池必须定期检查区块链上的单例硬币的状态，以验证它正在向矿池转移，而不是离开或转向另一个矿池。

原文参考

Farmer identification#

A farmer can be uniquely identified by the identifier of the farmer's singleton on the blockchain, this is what launcher_id refers to. The launcher_id can be used as a primary key in a database. The pool must periodically check the singleton's state on the blockchain to validate that it's farming to the pool, and not leaving or farming to another pool.

农民认证#

为了让农场主对池进行身份验证，必须将以下基于时间的身份验证令牌方案添加到某些端点的签名消息中。

authentication_token = current_utc_minutes / authentication_token_timeout

authentication_token_timeout 是矿池的配置参数，该参数也包含在 GET /pool_info 响应中，农民必须遵守该参数。而在签名 current_utc_minutes 时以分钟为单位的本地 UTC 时间戳。理想情况下，本地时钟应与时间同步协议（例如 NTP）同步。身份验证令牌通常包含在签名的有效负载中。

原文参考

Farmer authentication#

For the farmer to authenticate to the pool the following time based authentication token scheme must be added to the signing messages of some endpoints.

authentication_token = current_utc_minutes / authentication_token_timeout

Where authentication_token_timeout is a configuration parameter of the pool which is also included in the GET /pool_info response that must be respected by the farmer. Whereas current_utc_minutes is the local UTC timestamp in minutes at the moment of signing. The local clock should ideally be in sync with a time synchronization protocol e.g., NTP. The authentication token is usually included in a signed payload.

HTTPS 端点摘要#

矿池协议由几个返回 JSON 响应的 HTTPS 端点组成。HTTPS 服务器可以在任何端口上运行，但必须在启用 TLS（使用 CA 批准的证书）和启用流水线的情况下运行。所有字节值都编码为十六进制，前面有可选的 0x。客户端也应该使用流水线运行。

原文参考

HTTPS Endpoints Summary#

The pool protocol consists of several HTTPS endpoints which return JSON responses. The HTTPS server can run on any port, but must be running with TLS enabled (using a CA approved certificate), and with pipelining enabled. All bytes values are encoded as hex with optional 0x in front. Clients are also expected to run with pipelining.

GET /pool_info
GET /farmer
POST /farmer
PUT /farmer
POST /partial
GET /login (Optional)

错误代码#

失败的端点将始终返回一个带有错误代码和英文错误消息的 JSON 对象，如下所示：

{"error_code": 0, "error_message": ""}

可能会出现以下错误：

错误代码	描述
0x01	提供的标牌点已恢复
0x02	收到部分太晚了
0x03	未找到
0x04	空间证明无效
0x05	空间证明不够好
0x06	无效难度
0x07	无效签名
0x08	网络服务器引发异常
0x09	无效的谜语哈希
0x0A	农民不详
0x0B	农民已经知道
0x0C	无效的认证公钥
0x0D	无效的付款说明
0x0E	无效的单例硬币
0x0F	延迟时间太短
0x10	请求失败

原文参考

Error codes#

A failed endpoint will always return a JSON object with an error code and an english error message as shown below:

{"error_code": 0, "error_message": ""}

The following errors may occur:

Error code	Description
0x01	The provided signage point has been reverted
0x02	Received partial too late
0x03	Not found
0x04	Proof of space invalid
0x05	Proof of space not good enough
0x06	Invalid difficulty
0x07	Invalid signature
0x08	Web-Server raised an exception
0x09	Invalid puzzle hash
0x0A	Farmer not known
0x0B	Farmer already known
0x0C	Invalid authentication public key
0x0D	Invalid payout instructions
0x0E	Invalid singleton
0x0F	Delay time too short
0x10	Request failed

签名验证#

大多数端点都需要签名验证。验证需要对端点有效负载进行序列化以计算消息哈希，其完成方式如下：

message_hash = sha256(serialized_payload)

序列化的有效负载必须遵循此处 可流式传输 定义的标准。

原文参考

Signature validation#

Most of the endpoints require signature validation. The validation requires serialization of the endpoints payloads to calculate the message hash which is done like:

message_hash = sha256(serialized_payload)

The serialized payload must follow the Streamable standard defined here.

矿池 URL#

矿池 URL 是农民用来连接到矿池的 URL。子域、端口和路径是可选的。如果没有端口，客户端将使用 443。请注意，尾随斜杠不得存在。一切都必须小写。

https://subdomain.domain.tld:port/path

原文参考

Pool URL#

The pool URL is the url that farmers use to connect to the pool. The subdomains, port, and path are optional. The client will use 443 if there is no port. Note that the trailing slash must NOT be present. Everything must be lower case.

https://subdomain.domain.tld:port/path

获取矿池信息#

这不需要任何参数，并允许客户端获取有关矿池的信息。它在加入矿池之前被调用，当农民将池 URL 输入客户端时。这允许农民查看有关矿池的信息，并决定是否加入。它还允许农民在区块链上的单例硬币中设置正确的参数。对客户端实现者的警告：如果显示任何此类信息，请确保考虑恶意脚本和 JS 融入。它返回带有以下数据的 JSON 响应：

{    "description": "(example) The Reference Pool allows you to pool with low fees, paying out daily using Chia.",    "fee": 0.01,    "logo_url": "https://www.chia.net/img/chia_logo.svg",    "minimum_difficulty": 10,    "name": "The Reference Pool",    "protocol_version": 1,    "relative_lock_height": 100,    "target_puzzle_hash": "0x344587cf06a39db471d2cc027504e8688a0a67cce961253500c956c73603fd58",    "authentication_token_timeout": 5}

描述#

描述是一个简短的段落，当农民输入一个矿池 URL 时，它可以显示在 GUI 中。

费用#

矿池默认收取的费用，介于 0.0 (0.0%) 和 1.0 (100.0%) 之间的数字。这不包括区块链交易费用。

logo_url#

客户端可以在 UI 中显示的池徽标的 URL。这对于 v1.0 是可选的。

最小难度#

矿池支持的最低难度。这也将是农民开始发送证明的默认设置。

名称#

矿池名称，仅供展示，不上链。

协议版本#

矿池支持的矿池协议版本。

relative_lock_height#

用户在开始逃离矿池的时间点和他们可以完成矿池切换的时间点之间必须等待的块（确认）数。必须小于 4608（大约 24 小时）。

target_puzzle_hash#

这是从单例硬币发送奖励的目标。由矿池控制。

authentication_token_timeout#

有效的时间（以分钟为单位） authentication_token ，请参阅农民身份验证。

原文参考

GET /pool_info#

This takes no arguments, and allows clients to fetch information about a pool. It is called right before joining a pool, when the farmer enters the pool URL into the client. This allows the farmer to see information about the pool, and decide whether or not to join. It also allows the farmer to set the correct parameters in their singleton on the blockchain. Warning to client implementers: if displaying any of this information, make sure to account for malicious scripts and JS injections. It returns a JSON response with the following data:

{    "description": "(example) The Reference Pool allows you to pool with low fees, paying out daily using Chia.",    "fee": 0.01,    "logo_url": "https://www.chia.net/img/chia_logo.svg",    "minimum_difficulty": 10,    "name": "The Reference Pool",    "protocol_version": 1,    "relative_lock_height": 100,    "target_puzzle_hash": "0x344587cf06a39db471d2cc027504e8688a0a67cce961253500c956c73603fd58",    "authentication_token_timeout": 5}

description#

The description is a short paragraph that can be displayed in GUIs when the farmer enters a pool URL.

fee#

The fee that the pool charges by default, a number between 0.0 (0.0%) and 1.0 (100.0%). This does not include blockchain transaction fees.

logo_url#

A URL for a pool logo that the client can display in the UI. This is optional for v1.0.

minimum_difficulty#

The minimum difficulty that the pool supports. This will also be the default that farmers start sending proofs for.

name#

Name of the pool, this is only for display purposes and does not go on the blockchain.

protocol_version#

The pool protocol version supported by the pool.

relative_lock_height#

The number of blocks (confirmations) that a user must wait between the point when they start escaping a pool, and the point at which they can finalize their pool switch. Must be less than 4608 (approximately 24 hours).

target_puzzle_hash#

This is the target of where rewards will be sent to from the singleton. Controlled by the pool.

authentication_token_timeout#

The time in minutes for an authentication_token to be valid, see Farmer authentication.

获取/农民#

获取农民的最新信息。

请求参数：

- launcher_id- authentication_token- signature

示例请求：

https://poolurl.com/farmer/launcher_id=:launcher_id&authentication_token=:token&signature=:signature

成功回复：

{    "authentication_public_key": "0x970e181ae45435ae696508a78012dc80548c334cf29676ea6ade7049eb9d2b9579cc30cb44c3fd68d35a250cfbc69e29",    "payout_instructions": "0xc2b08e41d766da4116e388357ed957d04ad754623a915f3fd65188a8746cf3e8",    "current_difficulty": 10,    "current_points": 10}

参数#

launcher_id#

农民单例硬币的唯一标识，见农民身份。

authentication_token#

请参阅农民身份验证以了解 authentication_token .

签名#

这是按给定顺序对以下数据进行哈希序列化的 BLS 签名：

元素	类型
方法名称	字符串
launcher_id	字节32
target_puzzle_hash	字节32
authentication_token	uint64

其中 method_name 必须是序列化字符串 "get_farmer" ，参数必须根据签名验证进行序列化和哈希，签名必须由 authentication_public_key 使用 BLS IETF 规范中的增强方案的私钥签名。

其中参数必须根据签名验证进行序列化和哈希，签名必须由 authentication_public_key 使用 BLS IETF 规范中的增强方案的私钥签名。

注意：矿池必须返回当前的积分余额，这是自该用户上次付款以来找到的积分总数。

原文参考

GET /farmer#

Get the latest information for a farmer.

Request parameter:

- launcher_id- authentication_token- signature

Example request:

https://poolurl.com/farmer/launcher_id=:launcher_id&authentication_token=:token&signature=:signature

Successful response:

{    "authentication_public_key": "0x970e181ae45435ae696508a78012dc80548c334cf29676ea6ade7049eb9d2b9579cc30cb44c3fd68d35a250cfbc69e29",    "payout_instructions": "0xc2b08e41d766da4116e388357ed957d04ad754623a915f3fd65188a8746cf3e8",    "current_difficulty": 10,    "current_points": 10}

Parameter#
launcher_id#

The unique identifier of the farmer's singleton, see Farmer identification.

authentication_token#

See Farmer authentication for the specification of authentication_token.

signature#

This is a BLS signature of the hashed serialization of the following data in the given order:

Element	Type
method_name	string
launcher_id	bytes32
target_puzzle_hash	bytes32
authentication_token	uint64

where method_name must be the serialized string "get_farmer", the parameters must be serialized and hashed according to Signature validation and the signature must be signed by the private key of the authentication_public_key using the Augmented Scheme in the BLS IETF spec.

where the parameter must be serialized and hashed according to Signature validation and the signature must be signed by the private key of the authentication_public_key using the Augmented Scheme in the BLS IETF spec.

Note: The pool MUST return the current points balance, which is the total number of points found since the last payout for that user.

POST/农民#

在矿池中注册一个农民。在提交第一个部分之前需要一次。

要求：

{    "payload": {        "launcher_id": "0xae4ef3b9bfe68949691281a015a9c16630fc8f66d48c19ca548fb80768791afa",        "authentication_token": 27062279,        "authentication_public_key": "0x970e181ae45435ae696508a78012dc80548c334cf29676ea6ade7049eb9d2b9579cc30cb44c3fd68d35a250cfbc69e29",        "payout_instructions": "0xc2b08e41d766da4116e388357ed957d04ad754623a915f3fd65188a8746cf3e8",        "suggested_difficulty": 10    },    "signature": "0xa078dc1462bbcdec7cd651c5c3d7584ac6c6a142e049c7790f3b0ee8768ed6326e3a639f949b2293469be561adfa1c57130f64334994f53c1bd12e59579e27127fbabadc5e8793a2ef194a5a22ac832e92dcb6ad9a0d33bd264726f6e8df6aad"}

成功回复：

{"welcome_message" : "Welcome to the reference pool. Happy farming."}

成功的响应必须始终包含必须由矿池定义的欢迎消息。

有效载荷#

payload.launcher_id#

农民单例硬币的唯一标识，见农民身份。

payload.authentication_token#

请参阅农民身份验证以了解 authentication_token .

payload.authentication_public_key#

身份验证密钥的公钥，这是农民用来签署对池的请求的临时密钥。它是由 owner_key 授权的，这样可以更加安全地保存所有者密钥。矿池应拒绝使用过时的 authentication_keys 发出的请求。可以使用 PUT/farmer 更改这些密钥，该密钥使用所有者密钥进行签名。

payload.payout_instructions#

这些是关于农民希望如何获得报酬的说明。默认情况下，这将是一个 XCH 地址，但它可以设置为小于 1024 个字符的任何字符串，因此它可以代表另一个区块链或支付系统标识符。

payload.suggested_difficulty#

农民要求更新难度。可以被矿池忽略或尊重。但是，只有当认证公钥是该农民看到的最新公钥时，才应遵守这一点。

有关难度影响的更多详细信息，请参阅难度。

签名#

这是有效载荷散列序列化的 BLS 签名：

sha256(PostFarmerPayload)

由 owner_public_key 使用 BLS IETF 规范中的增强方案的私钥签名。

见可流式传输类 PostFarmerPayload 的矿池协议和农民身份验证的规格 authentication_token 。

原文参考

POST /farmer#

Request:

{    "payload": {        "launcher_id": "0xae4ef3b9bfe68949691281a015a9c16630fc8f66d48c19ca548fb80768791afa",        "authentication_token": 27062279,        "authentication_public_key": "0x970e181ae45435ae696508a78012dc80548c334cf29676ea6ade7049eb9d2b9579cc30cb44c3fd68d35a250cfbc69e29",        "payout_instructions": "0xc2b08e41d766da4116e388357ed957d04ad754623a915f3fd65188a8746cf3e8",        "suggested_difficulty": 10    },    "signature": "0xa078dc1462bbcdec7cd651c5c3d7584ac6c6a142e049c7790f3b0ee8768ed6326e3a639f949b2293469be561adfa1c57130f64334994f53c1bd12e59579e27127fbabadc5e8793a2ef194a5a22ac832e92dcb6ad9a0d33bd264726f6e8df6aad"}

Successful response:

{"welcome_message" : "Welcome to the reference pool. Happy farming."}

A successful response must always contain a welcome message which must be defined by the pool.

payload#
payload.launcher_id#

The unique identifier of the farmer's singleton, see Farmer identification.

payload.authentication_token#

See Farmer authentication for the specification of authentication_token.

payload.authentication_public_key#

The public key of the authentication key, which is a temporary key used by the farmer to sign requests to the pool. It is authorized by the owner_key, so that the owner key can be kept more secure. The pool should reject requests made with outdated authentication_keys. These key can be changed using PUT /farmer, which is signed with the owner key.

payload.payout_instructions#

These are the instructions for how the farmer wants to get paid. By default this will be an XCH address, but it can be set to any string with a size of less than 1024 characters, so it can represent another blockchain or payment system identifier.

payload.suggested_difficulty#

A request from the farmer to update the difficulty. Can be ignored or respected by the pool. However, this should only be respected if the authentication public key is the most recent one seen for this farmer.

See Difficulty for more details about the impact of the difficulty.

signature#

This is a BLS signature of the hashed serialization of the payload:

sha256(PostFarmerPayload)

signed by the private key of the owner_public_key using the Augmented Scheme in the BLS IETF spec.

See the streamable class PostFarmerPayload in the pool protocol and Farmer authentication for the specification of authentication_token.

PUT/农民#

允许农民更新他们关于矿池的信息。

要求：

{    "payload": {        "launcher_id": "0xae4ef3b9bfe68949691281a015a9c16630fc8f66d48c19ca548fb80768791afa",        "authentication_token": 27062279,        "authentication_public_key": "0x970e181ae45435ae696508a78012dc80548c334cf29676ea6ade7049eb9d2b9579cc30cb44c3fd68d35a250cfbc69e29",        "payout_instructions": "0xc2b08e41d766da4116e388357ed957d04ad754623a915f3fd65188a8746cf3e8",        "suggested_difficulty": 10    },    "signature": "0xa078dc1462bbcdec7cd651c5c3d7584ac6c6a142e049c7790f3b0ee8768ed6326e3a639f949b2293469be561adfa1c57130f64334994f53c1bd12e59579e27127fbabadc5e8793a2ef194a5a22ac832e92dcb6ad9a0d33bd264726f6e8df6aad"}

有关请求正文条目的描述，请参阅 POST/农民中的相应密钥。随密钥/值对提供的值用于更新服务器上的现有值。所有条目，除了 launcher_id，都是可选的，但必须至少有一个。

见可流式传输类 PutFarmerPayload 在矿池协议的细节和农民身份验证的规格 authentication_token 。

成功回复：

{  "authentication_public_key": true,  "payout_instructions": true,  "suggested_difficulty": true}

对于请求正文中提供的每个条目，成功的响应必须始终包含一个密钥/值对。true 如果条目已更新或 false 该值与当前值相同，则该值必须为。

请参阅下面的示例正文以仅更新身份验证密钥：

更新示例 authentication_public_key ：

{    "payload": {        "launcher_id": "0xae4ef3b9bfe68949691281a015a9c16630fc8f66d48c19ca548fb80768791afa",        "authentication_public_key": "0x970e181ae45435ae696508a78012dc80548c334cf29676ea6ade7049eb9d2b9579cc30cb44c3fd68d35a250cfbc69e29"    },    "signature": "0xa078dc1462bbcdec7cd651c5c3d7584ac6c6a142e049c7790f3b0ee8768ed6326e3a639f949b2293469be561adfa1c57130f64334994f53c1bd12e59579e27127fbabadc5e8793a2ef194a5a22ac832e92dcb6ad9a0d33bd264726f6e8df6aad"}

原文参考

PUT /farmer#

Allows farmers to update their information on the pool.

Request:

{    "payload": {        "launcher_id": "0xae4ef3b9bfe68949691281a015a9c16630fc8f66d48c19ca548fb80768791afa",        "authentication_token": 27062279,        "authentication_public_key": "0x970e181ae45435ae696508a78012dc80548c334cf29676ea6ade7049eb9d2b9579cc30cb44c3fd68d35a250cfbc69e29",        "payout_instructions": "0xc2b08e41d766da4116e388357ed957d04ad754623a915f3fd65188a8746cf3e8",        "suggested_difficulty": 10    },    "signature": "0xa078dc1462bbcdec7cd651c5c3d7584ac6c6a142e049c7790f3b0ee8768ed6326e3a639f949b2293469be561adfa1c57130f64334994f53c1bd12e59579e27127fbabadc5e8793a2ef194a5a22ac832e92dcb6ad9a0d33bd264726f6e8df6aad"}

For a description of the request body entries see the corresponding keys in POST /farmer. The values provided with the key/value pairs are used to update the existing values on the server. All entries, except launcher_id, are optional but there must be at least one of them.

See the streamable class PutFarmerPayload in the pool protocol for details and Farmer authentication for the specification of authentication_token.

Successful response:

{  "authentication_public_key": true,  "payout_instructions": true,  "suggested_difficulty": true}

A successful response must always contain one key/value pair for each entry provided in the request body. The value must be true if the entry has been updated or false if the value was the same as the current value.

See below for an example body to only update the authentication key:

Example to update authentication_public_key:

{    "payload": {        "launcher_id": "0xae4ef3b9bfe68949691281a015a9c16630fc8f66d48c19ca548fb80768791afa",        "authentication_public_key": "0x970e181ae45435ae696508a78012dc80548c334cf29676ea6ade7049eb9d2b9579cc30cb44c3fd68d35a250cfbc69e29"    },    "signature": "0xa078dc1462bbcdec7cd651c5c3d7584ac6c6a142e049c7790f3b0ee8768ed6326e3a639f949b2293469be561adfa1c57130f64334994f53c1bd12e59579e27127fbabadc5e8793a2ef194a5a22ac832e92dcb6ad9a0d33bd264726f6e8df6aad"}

POST/部分#

这是农民向矿池运营商提交的部分内容。

要求：

{  "payload": {    "launcher_id": "0xae4ef3b9bfe68949691281a015a9c16630fc8f66d48c19ca548fb80768791afa",    "authentication_token": 27062279,    "proof_of_space": {      "challenge": "0xe0e55d45eef8d53a6b68220abeec8f14f57baaa80dbd7b37430e42f9ac6e2c0e",      "pool_contract_puzzle_hash": "0x9e3e9b37b54cf6c7467e277b6e4ca9ab6bdea53cdc1d79c000dc95b6a3908a3b",      "plot_public_key": "0xa7ad70989cc8f18e555e9b698d197cdfc32465e0b99fd6cf5fdbac8aa2da04b0704ba04d2d50d852402f9dd6eec47a4d",      "size": 32,      "proof": "0xb2cd6374c8db249ad3b638199dbb6eb9eaefe55042cef66c43cf1e31161f4a1280455d8b53c2823c747fd4f8823c44de3a52cc85332431630857c359935660c3403ae3a92728d003dd66ef5966317cd49894d265a3e4c43f0530a1192874ed327e6f35862a25dfb67c5d0d573d078b4b8ba9bfb1cce52fd17939ae9d7033d3aa09d6c449e392ba2472a1fecf992abcc51c3bf5d56a72fef9900e79b8dba88a5afc39e04993325a0cd6b67757355b836f"    },    "sp_hash": "0x4c52796ca4ff775fbcdac90140c12270d26a37724ad77988535d58b376332533",    "end_of_sub_slot": false,    "harvester_id": "0xb9d8de98ec5c026f1167b0b587715d7137f43b6d1d40b81d9aac6dc8355fde28"  },  "aggregate_signature": "0xa078dc1462bbcdec7cd651c5c3d7584ac6c6a142e049c7790f3b0ee8768ed6326e3a639f949b2293469be561adfa1c57130f64334994f53c1bd12e59579e27127fbabadc5e8793a2ef194a5a22ac832e92dcb6ad9a0d33bd264726f6e8df6aad"}

成功回复：

{"new_difficulty": 10}

一个成功的反应必须始终包含农民必须尊重的新困难。

有效载荷#

这是部分的主要负载，由两个密钥签名：authentication_key 和 plot_key 。

payload.launcher_id#

农民单例硬币的唯一标识，见农民身份。

payload.authentication_token#

请参阅农民身份验证以了解 authentication_token .

payload.proof_of_space#

奇亚区块链格式的空间证明。

payload.proof_of_space.challenge#

空间证明的挑战，从标牌点或子时隙的末端计算。

payload.proof_of_space.pool_contract_puzzle_hash#

在图中编码的谜语哈希，相当于 p2_singleton_puzzle_hash。如果这个证明获胜，这是 7/8 奖励在区块链中获得的第一个地址。该值可以从 launcher_id 派生，并且必须对所有部分都有效。

payload.proof_of_space.plot_public_key#

与图块关联的公钥。（可以是图块本地密钥和农民之间的 2/2 BLS，但不一定）。

payload.proof_of_space.size#

K 大小，必须至少为 32。

payload.proof_of_space.proof#

64 x 值编码空间的实际证明，必须有效对应于 sp_hash。

payload.sp_hash#

这是标牌点输出的哈希值，或者子时隙的挑战哈希，如果它是子时隙挑战的结束。这必须是区块链上尚未恢复的有效标志点。矿池必须在处理部分后几分钟检查它没有在区块链上恢复。

payload.end_of_sub_slot#

如果为 true，则标牌点哈希对子时隙的挑战哈希进行编码。

聚合签名#

这是有效载荷哈希序列化的 2/2 BLS 签名：

sha256(PostPartialPayload)

使用 BLS IETF 规范中的增强方案由以下密钥的私钥签名：

plot_public_key
authentication_public_key

见可流式传输类 PostPartialPayload 在矿池协议的细节和农民身份验证的的规格 authentication_token 。

如果 BLS 签名未验证，则必须完全拒绝部分。

原文参考

POST /partial#

This is a partial submission from the farmer to the pool operator.

Request:

{  "payload": {    "launcher_id": "0xae4ef3b9bfe68949691281a015a9c16630fc8f66d48c19ca548fb80768791afa",    "authentication_token": 27062279,    "proof_of_space": {      "challenge": "0xe0e55d45eef8d53a6b68220abeec8f14f57baaa80dbd7b37430e42f9ac6e2c0e",      "pool_contract_puzzle_hash": "0x9e3e9b37b54cf6c7467e277b6e4ca9ab6bdea53cdc1d79c000dc95b6a3908a3b",      "plot_public_key": "0xa7ad70989cc8f18e555e9b698d197cdfc32465e0b99fd6cf5fdbac8aa2da04b0704ba04d2d50d852402f9dd6eec47a4d",      "size": 32,      "proof": "0xb2cd6374c8db249ad3b638199dbb6eb9eaefe55042cef66c43cf1e31161f4a1280455d8b53c2823c747fd4f8823c44de3a52cc85332431630857c359935660c3403ae3a92728d003dd66ef5966317cd49894d265a3e4c43f0530a1192874ed327e6f35862a25dfb67c5d0d573d078b4b8ba9bfb1cce52fd17939ae9d7033d3aa09d6c449e392ba2472a1fecf992abcc51c3bf5d56a72fef9900e79b8dba88a5afc39e04993325a0cd6b67757355b836f"    },    "sp_hash": "0x4c52796ca4ff775fbcdac90140c12270d26a37724ad77988535d58b376332533",    "end_of_sub_slot": false,    "harvester_id": "0xb9d8de98ec5c026f1167b0b587715d7137f43b6d1d40b81d9aac6dc8355fde28"  },  "aggregate_signature": "0xa078dc1462bbcdec7cd651c5c3d7584ac6c6a142e049c7790f3b0ee8768ed6326e3a639f949b2293469be561adfa1c57130f64334994f53c1bd12e59579e27127fbabadc5e8793a2ef194a5a22ac832e92dcb6ad9a0d33bd264726f6e8df6aad"}

Successful response:

{"new_difficulty": 10}

A successful response must always contain the new difficulty which must be respected by the farmer.

payload#

This is the main payload of the partial, which is signed by two keys: authentication_key and plot_key.

payload.launcher_id#

The unique identifier of the farmer's singleton, see Farmer identification.

payload.authentication_token#

See Farmer authentication for the specification of authentication_token.

payload.proof_of_space#

The proof of space in chia-blockchain format.

payload.proof_of_space.challenge#

The challenge of the proof of space, computed from the signage point or end of subslot.

payload.proof_of_space.pool_contract_puzzle_hash#

The puzzle hash that is encoded in the plots, equivalent to the p2_singleton_puzzle_hash. This is the first address that the 7/8 rewards get paid out to in the blockchain, if this proof wins. This value can be derived from the launcher_id, and must be valid for all partials.

payload.proof_of_space.plot_public_key#

Public key associated with the plot. (Can be a 2/2 BLS between plot local key and farmer, but not necessarily).

payload.proof_of_space.size#

K size, must be at least 32.

payload.proof_of_space.proof#

64 x values encoding the actual proof of space, must be valid corresponding to the sp_hash.

payload.sp_hash#

This is either the hash of the output for the signage point, or the challenge_hash for the sub slot, if it's an end of sub slot challenge. This must be a valid signage point on the blockchain that has not been reverted. The pool must check a few minutes after processing the partial, that it has not been reverted on the blockchain.

payload.end_of_sub_slot#

If true, the sp_hash encodes the challenge_hash of the sub slot.

aggregate_signature#

This is a 2/2 BLS signature of the hashed serialization of the payload:

sha256(PostPartialPayload)

signed by the private keys of the following keys using the Augmented Scheme in the BLS IETF spec:

plot_public_key
authentication_public_key

See the streamable class PostPartialPayload in the pool protocol for details and Farmer authentication for the specification of authentication_token.

A partial must be completely rejected if the BLS signature does not validate.

获取/登录#

如果池支持，这允许用户登录到 Web 界面，请参阅 GET/矿池信息中的服务标志。农夫软件必须提供一种生成和显示登录链接的方法，或者提供一个生成链接的按钮，然后只需在默认浏览器中打开它。该链接遵循以下规范。

请注意，没有明确的帐户创建。农民可以在使用 POST/农民在矿池中公开自己的身份后登录。

请求参数：

- launcher_id- authentication_token- signature

示例请求：

https://poolurl.com/login?launcher_id=:launcher_id&authentication_token=:token&signature=:signature

launcher_id#

农民单例硬币的唯一标识，见农民身份。

authentication_token#

请参阅农民身份验证以了解 authentication_token .

签名#

这是按给定顺序对以下数据进行散列序列化的 BLS 签名：

元素	类型
方法名称	字符串
launcher_id	字节32
target_puzzle_hash	字节32
authentication_token	uint64

method_name 必须是序列化的字符串 "get_login"，target_puzzle_hash 是矿池的目标谜语哈希（参见 GET/矿池信息）。参数必须根据签名验证进行序列化和散列，签名必须由 authentication_public_key 使用 BLS IETF 规范中的增强方案的私钥签名。

其中参数必须根据签名验证进行序列化和散列，签名必须由 authentication_public_key 使用 BLS IETF 规范中的增强方案的私钥签名。

原文参考

GET /login#

This allows the user to log in to a web interface if the pool supports it, see service flags in GET /pool_info. The farmer software must offer a way to generate and display a login link or provide a button which generates the link and then just opens it in the default browser. The link follows the specification below.

Note that there is no explicit account creation. A farmer can log in after making their self known at the pool with POST /farmer.

Request parameters:

- launcher_id- authentication_token- signature

Example request:

https://poolurl.com/login?launcher_id=:launcher_id&authentication_token=:token&signature=:signature

launcher_id#

The unique identifier of the farmer's singleton, see Farmer identification.

authentication_token#

See Farmer authentication for the specification of authentication_token.

signature#

This is a BLS signature of the hashed serialization of the following data in the given order:

Element	Type
method_name	string
launcher_id	bytes32
target_puzzle_hash	bytes32
authentication_token	uint64

where method_name must be the serialized string "get_login" and target_puzzle_hash is pool's target puzzle hash (see GET /pool_info). The parameters must be serialized and hashed according to Signature validation and the signature must be signed by the private key of the authentication_public_key using the Augmented Scheme in the BLS IETF spec.

难度#

难度允许矿池操作员控制他们每天从每个农民那里收到多少部分。可以为每个农民单独调整难度。一个合理的目标是每天 300 个部分，以确保对农民的频繁反馈和低可变性。难度为 1 会导致每个 k32 图每天大约有 10 个部分。这是协议的 V1 支持的最小难度为1。但是，为了效率，矿池可以设置更高的最小难度。在计算证明质量是否足以获得积分时，矿池应使用 sub_slot_iters=37600000000 。如果农户提交的证明对当前难度不够好，则矿池应通过 current_difficulty 在响应中设置来响应。

原文参考

Difficulty#

The difficulty allows the pool operator to control how many partials per day they are receiving from each farmer. The difficulty can be adjusted separately for each farmer. A reasonable target would be 300 partials per day, to ensure frequent feedback to the farmer, and low variability. A difficulty of 1 results in approximately 10 partials per day per k32 plot. This is the minimum difficulty that the V1 of the protocol supports is 1. However, a pool may set a higher minimum difficulty for efficiency. When calculating whether a proof is high quality enough for being awarded points, the pool should use sub_slot_iters=37600000000. If the farmer submits a proof that is not good enough for the current difficulty, the pool should respond by setting the current_difficulty in the response.

积分#

提交难度为 X 的部分会获得 X 分，这意味着分数与难度呈线性关系。例如，100 TiB 的空间每天应该产生大约 10,000 个点，无论难度设置为 100 还是 200。只要农民始终提交部分内容，为农民设置什么难度都没有关系。规范不要求矿池按积分按比例支付，但应向农民明确支付方案，并在响应中确认积分并返还累积积分。

原文参考

Points#

X points are awarded for submitting a partial with difficulty X, which means that points scale linearly with difficulty. For example, 100 TiB of space should yield approximately 10,000 points per day, whether the difficulty is set to 100 or 200. It should not matter what difficulty is set for a farmer, as long as they are consistently submitting partials. The specification does not require pools to pay out proportionally by points, but the payout scheme should be clear to farmers, and points should be acknowledged and accumulated points returned in the response.

安全考虑#

Security considerations#

部分#

Parties#

农民身份#

Farmer identification#

农民认证#

Farmer authentication#

HTTPS 端点摘要#

HTTPS Endpoints Summary#

错误代码#

Error codes#

签名验证#

Signature validation#

矿池 URL#

Pool URL#

获取矿池信息#

描述#

费用#

logo_url#

最小难度#

名称#

协议版本#

relative_lock_height#

target_puzzle_hash#

authentication_token_timeout#

GET /pool_info#

description#

fee#

logo_url#

minimum_difficulty#

name#

protocol_version#

relative_lock_height#

target_puzzle_hash#

authentication_token_timeout#

获取/农民#

参数#

launcher_id#

authentication_token#

签名#

GET /farmer#

Parameter#

launcher_id#

authentication_token#

signature#

POST/农民#

有效载荷#

payload.launcher_id#

payload.authentication_token#

payload.authentication_public_key#

payload.payout_instructions#

payload.suggested_difficulty#

签名#

POST /farmer#

payload#

payload.launcher_id#

payload.authentication_token#

payload.authentication_public_key#

payload.payout_instructions#

payload.suggested_difficulty#

signature#

PUT/农民#

PUT /farmer#

POST/部分#

有效载荷#

payload.launcher_id#

payload.authentication_token#

payload.proof_of_space#

payload.proof_of_space.challenge#

payload.proof_of_space.pool_contract_puzzle_hash#

payload.proof_of_space.plot_public_key#

payload.proof_of_space.size#

payload.proof_of_space.proof#

payload.sp_hash#

payload.end_of_sub_slot#

聚合签名#

POST /partial#

payload#

payload.launcher_id#