From da006d423f7dab7b046a9032ee9c25e4ba102eb7 Mon Sep 17 00:00:00 2001 From: Hugo Doyon Date: Thu, 14 May 2020 13:17:49 -0400 Subject: [PATCH] publicly insteat of pubicly publicly insteat of pubicly --- ch03.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch03.asciidoc b/ch03.asciidoc index 71f04d8..6feee8d 100644 --- a/ch03.asciidoc +++ b/ch03.asciidoc @@ -301,7 +301,7 @@ If the channel partner is known to you, maybe it is even a friend of yours, you ===== Examining the ugly way - protocol breach In case your channel partner tries to cheat you - whether deliberately or not - by publishing an outdated commitment transaction, you will be able to use the timelock to detect this attempt to cheat. If you are watchful you will detect the protocol breach, i.e. the attempt to cheat, and as reward you will take the funds from the cheater. -On the contrary, if you are not vigilant you will not look out for the pubicly visible protocol breach and the cheater will steal funds from you. +On the contrary, if you are not vigilant you will not look out for the publicly visible protocol breach and the cheater will steal funds from you. If you are watchful, you observe the breach and following the protocol you are permitted to collect on the outputs by using the revocation secret you had previously received to negotiate a newer state of the channel. That means you can claim the funds from the cheating channel partner.