From d75e1a7ba8dd5921d4b7ab5d922dde3bf3a1c4cd Mon Sep 17 00:00:00 2001 From: Adeyemi Ademola Date: Tue, 2 Aug 2022 20:52:37 +0100 Subject: [PATCH] Chakita Changes --- ...panding_Bitcoin_Transactions_with_Schnorr.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 X_0_Expanding_Bitcoin_Transactions_with_Schnorr.md diff --git a/X_0_Expanding_Bitcoin_Transactions_with_Schnorr.md b/X_0_Expanding_Bitcoin_Transactions_with_Schnorr.md new file mode 100644 index 000000000..ba3cc795e --- /dev/null +++ b/X_0_Expanding_Bitcoin_Transactions_with_Schnorr.md @@ -0,0 +1,17 @@ +# Chapter X: Expanding Bitcoin Transactions with Schnorr +The traditionally used ECDSA signatures in Bitcoin for authenticating transactions are standardized but have a number of downsides like non-linearity, signature malleability, to name a few. +These issues do not exist in the case of Schnorr signatures. Schnorr, being inherently non-malleable and linear, allows usage of various cryptographic tools in Bitcoin like MuSig, Adopter Signature and Cross-Input signature aggregation. This section aims to develop an understanding of Schnorr Signatures and their usage in Bitcoin transactions. +## Objectives for This Section +After working through this chapter, a developer will be able to: + * Understand the Math of Schnorr and it's advantages + * Sign, Add and Read a Schnorr Signature + + +Supporting objectives include the ability to: + * Use Schnorr with Taproot + * Understand the Use of Adapter Signatures + * Support MuSig with Schnorr +## Table of Contents + + * [Section One: Understanding Schnorr Signatures]() + * [Section Two: Using Schnorr Signatures]()