From 1eca5e41e04944c6c058ba0ef0b80f673239f53d Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Fri, 24 Jan 2020 08:57:53 -1000 Subject: [PATCH] Update 08_4_Scripting_a_Multisig.md --- 08_4_Scripting_a_Multisig.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/08_4_Scripting_a_Multisig.md b/08_4_Scripting_a_Multisig.md index 9695e7b..d6de621 100644 --- a/08_4_Scripting_a_Multisig.md +++ b/08_4_Scripting_a_Multisig.md @@ -1,6 +1,6 @@ # 8.4: Scripting a Multisig -> **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. +> :information_source: **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. Before we close out this intro to P2SH scripting, it's worth examining a more realistic example. Ever since [ยง6.1](06_1_Sending_a_Transaction_to_a_Multisig.md), we've been casually saying that the `bitcoin-cli` interface wraps its multisig transaction in a P2SH transaction. In fact, this is the standard methodology for creating multisigs on the Blockchain. Here's how that works, in depth.