1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-22 16:18:11 +00:00

Edited ch06_transactions.adoc with Atlas code editor

This commit is contained in:
clenser 2023-10-19 00:40:54 +00:00
parent a762197f1c
commit 4b142b0a7d

View File

@ -190,7 +190,7 @@ encoded as a compactSize unsigned integer.
.CompactSize Unsigned Integers .CompactSize Unsigned Integers
**** ****
Unsigned integers in Bitcoin that often have low values, but which may Unsigned integers((("compactSize unsigned integers", id="compactsize")))((("unsigned integers", id="unsigned"))) in Bitcoin that often have low values, but which may
sometimes have high values, are usually encoded using the compactSize sometimes have high values, are usually encoded using the compactSize
data type. CompactSize is a version of a variable-length integer, so data type. CompactSize is a version of a variable-length integer, so
it's sometimes called var_int or varint (see, for example, documentation it's sometimes called var_int or varint (see, for example, documentation
@ -207,7 +207,7 @@ nBits field in a Bitcoin block header is encoded using a custom data
type known as +Compact+, which is unrelated to compactSize. When type known as +Compact+, which is unrelated to compactSize. When
talking about the variable length integers used in Bitcoin transaction talking about the variable length integers used in Bitcoin transaction
serialization and other parts of the Bitcoin P2P protocol, we will serialization and other parts of the Bitcoin P2P protocol, we will
always use the full name compactSize. always use the full name((("compactSize unsigned integers", startref="compactsize")))((("unsigned integers", startref="unsigned"))) compactSize.
==== ====
For numbers from 0 to 252, compactSize unsigned integers are identical For numbers from 0 to 252, compactSize unsigned integers are identical