diff options
| author | cocoyeal <ricodigging@gmail.com> | 2024-05-29 16:18:11 +0800 |
|---|---|---|
| committer | cocoyeal <ricodigging@gmail.com> | 2024-05-29 16:18:11 +0800 |
| commit | 46a2440718ce96681155e4c96bfc373d079d2eef (patch) | |
| tree | b49a43a013d085727b1ffe38f7a83031ac4f45c0 /bip-0115.mediawiki | |
| parent | 758a58ab54fddce0c6d062ed8fdf2b28c2eb7790 (diff) | |
| download | bips-46a2440718ce96681155e4c96bfc373d079d2eef.tar.xz | |
remove duplicated words
Diffstat (limited to 'bip-0115.mediawiki')
| -rw-r--r-- | bip-0115.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0115.mediawiki b/bip-0115.mediawiki index 8bc90f6..042d057 100644 --- a/bip-0115.mediawiki +++ b/bip-0115.mediawiki @@ -98,7 +98,7 @@ What if ParamBlockHash has leading zeros? Should this be prevented? * If leading zeros are included, they should be compared to the actual block hash. (If they were truncated, fewer bytes would be compared.) * It is unlikely that the leading zeros will ever be necessary for sufficient precision, so the additional space is not a concern. -* Since all block hashes are in principle shorter than than 29 bytes, ParamBlockHash may not be larger than 28 bytes. +* Since all block hashes are in principle shorter than 29 bytes, ParamBlockHash may not be larger than 28 bytes. Why is it safe to allow checking blocks as recently as the immediate previous block? |