From 5e2cdf38e5670a953fbc13b6e8e2e20e3c57ff9b Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 18:13:58 +0000 Subject: [PATCH] Edited ch14_applications.adoc with Atlas code editor --- ch14_applications.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch14_applications.adoc b/ch14_applications.adoc index a66695aa..e5c29030 100644 --- a/ch14_applications.adoc +++ b/ch14_applications.adoc @@ -450,7 +450,7 @@ image::images/mbc3_1401.png["A payment channel between Bob and Alice, showing th ==== Simple Payment Channel Example To -explain state channels, we start with a very simple example. We +explain ((("payment channels", "example of", id="payment-channel-example")))state channels, we start with a very simple example. We demonstrate a one-way channel, meaning that value is flowing in one direction only. We will also start with the naive assumption that no one is trying to cheat, to keep things simple. Once we have the basic @@ -542,7 +542,7 @@ the commitment transactions that update the balance of the channel. In the end, only two transactions are recorded on the blockchain: the funding transaction that established the channel and a settlement -transaction that allocated the final balance correctly between the two +transaction that allocated the final balance correctly between((("payment channels", "example of", startref="payment-channel-example"))) the two participants. [[video_payment_channel]]