summaryrefslogtreecommitdiff
path: root/bip-0112.mediawiki
diff options
context:
space:
mode:
Diffstat (limited to 'bip-0112.mediawiki')
-rw-r--r--bip-0112.mediawiki4
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0112.mediawiki b/bip-0112.mediawiki
index 1c53561..c7ee45e 100644
--- a/bip-0112.mediawiki
+++ b/bip-0112.mediawiki
@@ -80,9 +80,9 @@ of some future event. However, given the immutable nature of the blockchain, it
is practically impossible to retroactively invalidate a previous commitment that
has already confirmed. The only mechanism we really have for retroactive
invalidation is blockchain reorganization which, for fundamental security
-reasons, is designed to be very hard and very expensive to deliberately pull off.
+reasons, is designed to be very hard and very expensive to do.
-Despite this limitation, we do have a way to provide something functionally similar
+Despite this limitation, we do have a way to provide something functionally similar to retroactive invalidation while preserving irreversibility of past commitments
using CHECKSEQUENCEVERIFY. By constructing scripts with multiple branches of
execution where one or more of the branches are delayed we provide
a time window in which someone can supply an invalidation condition that allows the