From 3f8084760fcac2a29c70e1b9dfee512a8aba4181 Mon Sep 17 00:00:00 2001 From: Patrick Lemke Date: Thu, 20 Feb 2020 17:45:16 +0100 Subject: [PATCH] duplicate words --- ch03.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch03.asciidoc b/ch03.asciidoc index fa26618..3fec302 100644 --- a/ch03.asciidoc +++ b/ch03.asciidoc @@ -159,7 +159,7 @@ Naturally one would assume that Alice should still be in the possession of the 1 This can actually be easily achieved with the following construction: . Alice creates a new private / public key pair and informs Bob that she wishes to open a channel via the `open_channel` message. -. Bob also creates a new private / public key pair and agrees to Alice to accept a channel from Alice while sending his public key to Alice via the `accept_channel` message. +. Bob also creates a new private / public key pair and agrees to accept a channel from Alice while sending his public key to Alice via the `accept_channel` message. . Alice now creates a funding transaction from her wallet that sends 10 mBTC to the multisignature address with a locking script `2 2 CHECKMULTISIG`. . Alice does not broadcast the funding transaction but informs Bob about the transaction id of the funding transaction by sending a `funding_created` message. . Both Alice and Bob create their version of a commitment transaction. This Transaction will spend from the funding transaction and send all the bitcoin back to an address controlled by Alice.