From 4b142b0a7d45ece190e99243b997b36a01fe90f1 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 00:40:54 +0000 Subject: [PATCH] Edited ch06_transactions.adoc with Atlas code editor --- ch06_transactions.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc index a7573b5b..56effd0a 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -190,7 +190,7 @@ encoded as a compactSize unsigned integer. .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 data type. CompactSize is a version of a variable-length integer, so 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 talking about the variable length integers used in Bitcoin transaction 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