From e7915f5f3abb0bd25382d607483676424898d6fb Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 18:00:42 +0000 Subject: [PATCH] Edited ch14_applications.adoc with Atlas code editor --- ch14_applications.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch14_applications.adoc b/ch14_applications.adoc index 77ee566e..e47b5148 100644 --- a/ch14_applications.adoc +++ b/ch14_applications.adoc @@ -197,7 +197,7 @@ coins are to be spent. That brings us to _pay to contract (P2C)_. 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 <>, where it became 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 -agree on some data, such as a contract, and then tweak Alice's public +agree on some data, such as a contract, and then((("key tweaks"))) tweak Alice's public key so that it commits to the contract. At any time, Bob can reveal Alice's underlying key and the tweak used to commit to the contract, proving that she received the funds. If Alice spends the funds, that