From 59bf76585b73e7b2cc021b5fd496e0449a95e3ce Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Fri, 24 Jan 2020 09:46:46 -1000 Subject: [PATCH] Update 10_1_Using_Script_Conditionals.md Fix per @Janaka-Steph --- 10_1_Using_Script_Conditionals.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10_1_Using_Script_Conditionals.md b/10_1_Using_Script_Conditionals.md index e66ea34..9a66711 100644 --- a/10_1_Using_Script_Conditionals.md +++ b/10_1_Using_Script_Conditionals.md @@ -73,7 +73,7 @@ ENDIF ``` The `True` or `False` statement is placed on the stack _prior_ to running the `IF`, then the correct block of code is run based on that result. -This particular example code is intended as a poor man's 1-of-2 multisignature. The owner of `` would put ` True` in his locking script, while the owner of `` would put ` False` in her locking script. That trailing `True` or `False` is what's checked by the `IF`/`ELSE` statement. It tells the script which public-key hash to check against, then the `OP_EQUALVERIFY` and the `OP_CHECKSIG` at the end do the real work. +This particular example code is intended as a poor man's 1-of-2 multisignature. The owner of `` would put ` True` in his unlocking script, while the owner of `` would put ` False` in her unlocking script. That trailing `True` or `False` is what's checked by the `IF`/`ELSE` statement. It tells the script which public-key hash to check against, then the `OP_EQUALVERIFY` and the `OP_CHECKSIG` at the end do the real work. ### Run an If/Then Multisig