From 8eb7a5ac43ffde4d1aaf83c8825bdba742085673 Mon Sep 17 00:00:00 2001 From: "George C. Knee" Date: Tue, 29 Aug 2023 11:29:23 +0100 Subject: [PATCH] Update 0080-defunding-a-channel.md --- docs/protocol-tutorial/0080-defunding-a-channel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/protocol-tutorial/0080-defunding-a-channel.md b/docs/protocol-tutorial/0080-defunding-a-channel.md index 207942ebc..f91402fd9 100644 --- a/docs/protocol-tutorial/0080-defunding-a-channel.md +++ b/docs/protocol-tutorial/0080-defunding-a-channel.md @@ -86,7 +86,7 @@ Visually, we can see some of the on-chain funding for the channel has been trans ### Tracking on-chain storage -When a channel has been partially defunded using `transfer`, the [on-chain storage](./0040-lifecycle-of-a-channel.md#adjudicator-storage) is updated. To continue the defunding process, it is necessary to track sufficient information to supply the new outcome for the next call to `transfer` (which could be made by a different party). +When a channel has been finalized, and also when a channel has been (partially) defunded using `transfer`, the [on-chain storage](./0040-lifecycle-of-a-channel.md#adjudicator-storage) is updated. To continue the defunding process, it is necessary to track sufficient information to supply the new outcome for the next call to `transfer` (which could be made by a different party). To do this, it is necessary to listen for `AllocationUpdated` events and to compute the new outcome using `computeTransferEffectsAndInteractions` off-chain helper function