1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-01-23 14:11:00 +00:00

CH07: correction: the utxo set is not stored in ram

This commit is contained in:
David A. Harding 2023-03-14 09:44:29 -10:00
parent 245adc151d
commit 38dd2398ae

View File

@ -477,9 +477,9 @@ ability to create custom transaction scripts, and each customer would
have to understand how to create a transaction using custom scripts. have to understand how to create a transaction using custom scripts.
Furthermore, the resulting transaction would be about five times larger Furthermore, the resulting transaction would be about five times larger
than a simple payment transaction, because this script contains very than a simple payment transaction, because this script contains very
long public keys. The burden of that extra-large transaction would be long public keys. The burden of that extra data would be
borne by the customer in the form of fees. Finally, a large transaction borne by the customer in the form of extra transaction fees. Finally, a large transaction
script like this would be carried in the UTXO set in RAM in every full script like this would be carried in the UTXO set in every full
node, until it was spent. All of these issues make using complex scriptPubKeys node, until it was spent. All of these issues make using complex scriptPubKeys
difficult in practice. difficult in practice.
@ -734,7 +734,7 @@ UTXO set. +RETURN+ outputs are recorded on the blockchain, so they
consume disk space and contribute to the increase in the blockchain's consume disk space and contribute to the increase in the blockchain's
size, but they are not stored in the UTXO set and therefore do not bloat size, but they are not stored in the UTXO set and therefore do not bloat
the UTXO memory pool and burden full nodes with the cost of more the UTXO memory pool and burden full nodes with the cost of more
expensive RAM. expensive database operations.
+RETURN+ scripts look like this: +RETURN+ scripts look like this: