diff options
| author | Ava Chow <github@achow101.com> | 2024-05-01 18:00:38 -0400 |
|---|---|---|
| committer | Ava Chow <github@achow101.com> | 2024-05-01 18:00:38 -0400 |
| commit | 3bd457c595a9a24ce9fedb38f0df2df659eb9974 (patch) | |
| tree | 5035d6bed3e827bd952b6e6d6eeb3e80e1987a3d /bip-0310.mediawiki | |
| parent | e155b58f1370dd90f0b2020862dff7dd43d891f2 (diff) | |
310: Fix incorrectly formatted link
Diffstat (limited to 'bip-0310.mediawiki')
| -rw-r--r-- | bip-0310.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0310.mediawiki b/bip-0310.mediawiki index 6104015..34522be 100644 --- a/bip-0310.mediawiki +++ b/bip-0310.mediawiki @@ -190,7 +190,7 @@ send the mask, in this case a default full mask is used. * '''"version-rolling.mask"''' (REQUIRED, ''TMask'') ::- Bits set to 1 are allowed to be changed by the miner. If a miner changes bits with mask value 0, the server will reject the submit. -::- The server SHOULD return the largest mask possible (as many bits set to 1 as possible). This can be useful in a mining proxy setup when a proxy needs to negotiate the best mask for its future clients. There is a [Draft BIP](https://github.com/bitcoin/bips/pull/661/files) describing available nVersion bits. The server SHOULD pick a mask that preferably covers all bits specified in the BIP. +::- The server SHOULD return the largest mask possible (as many bits set to 1 as possible). This can be useful in a mining proxy setup when a proxy needs to negotiate the best mask for its future clients. There is a [https://github.com/bitcoin/bips/pull/661/files Draft BIP] describing available nVersion bits. The server SHOULD pick a mask that preferably covers all bits specified in the BIP. * '''"version-rolling.min-bit-count"''' (REQUIRED, ''TMask'') ::- The miner also provides a minimum number of bits that it needs for efficient version rolling in hardware. Note that this parameter provides important diagnostic information to the pool server. If the requested bit count exceeds the limit of the pool server, the miner always has the chance to operate in a degraded mode without using full hashing power. The pool server SHOULD NOT terminate miner connection if this rare mismatch case occurs. |