develop
Clare Laylock 6 months ago
parent 4f5c3554ae
commit f623a5b172

@ -100,7 +100,7 @@ Although these earlier digital currencies worked, they were centralized and, as
Bitcoin was((("Bitcoin", "history of")))((("history", "of Bitcoin", secondary-sortas="Bitcoin")))((("Nakamoto, Satoshi"))) first described in 2008 with the publication of a
paper titled "Bitcoin: A Peer-to-Peer Electronic Cash
System,"footnote:[https://oreil.ly/KUaBM["Bitcoin: A Peer-to-Peer Electronic Cash System"],
Satoshi Nakamoto (see <<satoshi_whitepaper>>).] written under the
Satoshi Nakamoto.] written under the
alias of Satoshi Nakamoto (see <<satoshi_whitepaper>>). Nakamoto
combined several prior inventions such as digital signatures and Hashcash to create
a completely decentralized electronic cash system that does not rely on
@ -122,11 +122,8 @@ increased exponentially, and their combined computational power now
exceeds the combined number of computing operations of the
world's top supercomputers.
++++
<p class="fix_tracking">
Satoshi Nakamoto withdrew from the public in April 2011, leaving the responsibility of developing the code and network to a thriving group of volunteers. The identity of the person or people behind Bitcoin is still unknown. However, neither Satoshi Nakamoto nor anyone else exerts individual control over the Bitcoin system, which operates based on fully transparent mathematical principles, open source code, and consensus among participants. The invention itself is groundbreaking and has already spawned new science in the fields of distributed computing, economics, and econometrics.
</p>
++++
.A Solution to a Distributed Computing Problem
****

@ -843,6 +843,7 @@ halts execution if one of the following occurs:
* The top stack item is greater than the transaction's lock time field.
* The sequence field of the input is 0xffffffff.
[role="less_space pagebreak-before"]
[[timelock_conflicts]]
.Timelock Conflicts
****
@ -1676,6 +1677,7 @@ our tree with this knowledge as shown in <<diagram_mast3>>.
.A MAST with the most-expected script in the best position.
image::images/mbc3_0707.png["A MAST with the most-expected script in the best position"]
[role="less_space pagebreak-before"]
Now we only need to provide two commitments for the common case (saving 32
bytes), although we still need three commitments for the less common cases.
If you know (or can guess) the probabilities of

@ -937,27 +937,27 @@ differences:
<tbody>
<tr>
<td><p class="right">0</p></td>
<td><p>6</p></td>
<td><p class="right">6</p></td>
</tr>
<tr>
<td><p>1</p></td>
<td><p>10</p></td>
<td><p class="right">1</p></td>
<td><p class="right">10</p></td>
</tr>
<tr>
<td><p>2</p></td>
<td><p>8</p></td>
<td><p class="right">2</p></td>
<td><p class="right">8</p></td>
</tr>
<tr>
<td><p>3</p></td>
<td><p>6</p></td>
<td><p class="right">3</p></td>
<td><p class="right">6</p></td>
</tr>
<tr>
<td><p>4</p></td>
<td><p>4</p></td>
<td><p class="right">4</p></td>
<td><p class="right">4</p></td>
</tr>
<tr>
<td><p>5</p></td>
<td><p>2</p></td>
<td><p class="right">5</p></td>
<td><p class="right">2</p></td>
</tr>
</tbody>
</table>

@ -439,6 +439,9 @@ An extended comment in Bitcoin Core's source code, reproduced here with slight r
significant problem in the design of Bitcoin's duplication of odd
elements in its merkle tree:
++++
<p data-type="attribution">Bitcoin Core <em>src/consensus/merkle.cpp</em></p>
++++
[quote,Bitcoin Core src/consensus/merkle.cpp]
____
WARNING! If you're reading this because you're learning about crypto

@ -397,7 +397,7 @@ The calculation can be seen in function +GetBlockSubsidy+ in the Bitcoin
Core client, as shown in <<getblocksubsidy_source>>.
[[getblocksubsidy_source]]
.Calculating the block reward&#x2014;Function [.plain]#+GetBlockSubsidy+,# Bitcoin Core Client, main.cpp
.Calculating the block reward&#x2014;Function [.plain]#+GetBlockSubsidy+,# Bitcoin Core Client, [.plain]#main.cpp#
====
[role="c_less_space"]
[source, cpp]

@ -21,11 +21,11 @@ pre[data-type="programlisting"] {
/*--Adjusting padding in index to avoid bad break--*/
@page index:first { /* first page */
padding-bottom: 0.1in;
padding-bottom: 0.4in;
}
@page index: {
padding-bottom: 0.1in;
padding-bottom: 0.3in;
}

Loading…
Cancel
Save