arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-22 16:18:11 +00:00
Code Issues Releases Wiki Activity

Edited ch14_applications.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-19 18:00:02 +00:00
parent e506a6ae25
commit 9bdf491393
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ch14_applications.adoc
View File

@ -194,7 +194,7 @@ coins are to be spent. That brings us to _pay to contract (P2C)_.
[[p2c_for_colored_coins]] [[p2c_for_colored_coins]]
==== Pay to Contract (P2C) ==== Pay to Contract (P2C)
We previously learned about P2C in <<pay_to_contract>>, where it became We ((("colored coins application", "P2C (pay to contract)", id="color-coin-p2c")))((("P2C (pay to contract)", id="p2c-color-coin")))previously learned about P2C in <<pay_to_contract>>, where it became
part of the basis for the taproot upgrade to Bitcoin's consensus rules. part of the basis for the taproot upgrade to Bitcoin's consensus rules.
As a short reminder, P2C allows a spender (Bob) and receiver (Alice) to As a short reminder, P2C allows a spender (Bob) and receiver (Alice) to
agree on some data, such as a contract, and then tweak Alice's public agree on some data, such as a contract, and then tweak Alice's public
@ -226,7 +226,7 @@ spends and Alice has tweaked her public key by the contract terms.
Because full nodes don't (and can't) validate that the contract is Because full nodes don't (and can't) validate that the contract is
followed correctly, we need to figure out who is responsible for followed correctly, we need to figure out who is responsible for
validation. That brings us to _client-side validation._ validation. That brings ((("colored coins application", "P2C (pay to contract)", startref="color-coin-p2c")))((("P2C (pay to contract)", startref="p2c-color-coin")))us to _client-side validation._
==== Client-Side Validation ==== Client-Side Validation