Skip to content

Commit 09bd00e

Browse files
committed
add taproot module and update utxo topic
1 parent 53a4b5e commit 09bd00e

15 files changed

+256
-373
lines changed

decoding/inputs.mdx

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,4 +11,13 @@ images: ["/bitcoin-topics/static/images/topics/thumbnails/musig-thumbnail.webp"]
1111
parent: "transaction-structure"
1212
---
1313

14-
(coming soon)
14+
<TransactionCreation
15+
enabledFields={[
16+
"input_count",
17+
"txid",
18+
"vout",
19+
"scriptsig_size",
20+
"scriptsig",
21+
"sequence"
22+
]}
23+
/>

decoding/introduction-taproot.mdx

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: "Introduction to Taproot"
3+
date: 2024-01-25T15:32:14Z
4+
lastmod: "2024-07-26"
5+
draft: false
6+
category: Taproot
7+
layout: TopicBanner
8+
order: 7
9+
icon: "FaHashtag"
10+
images: ["/bitcoin-topics/static/images/topics/thumbnails/musig-thumbnail.webp"]
11+
---
12+
13+
(coming soon)

decoding/marker-flag.mdx

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,14 +16,13 @@ parent: "transaction-structure"
1616

1717
<TransactionCreation enabledFields={["marker", "flag"]} />
1818

19-
The marker and flag are optional fields introduced with **SegWit**.
19+
The marker and flag are **optional** fields introduced with **SegWit**.
2020

21-
They indicate that a transaction uses the segregated witness structure defined in **BIP144**.
22-
Witness data is required for inputs locked by **P2WPKH**, **P2WSH**, or **P2TR**.
21+
They indicate that a transaction uses the segregated witness structure defined in **BIP144** (Witness data is required for inputs locked by **P2WPKH**, **P2WSH**, or **P2TR**).
2322

2423
## Marker
2524

26-
Marker indicates that the transaction uses the extended format.
25+
Marker indicates that the transaction uses the SegWit transaction format (also known as the extended format).
2726

2827
- Marker is **1 byte**.
2928
- Must always be `0x00` to signal a SegWit transaction.
@@ -46,9 +45,4 @@ Marker indicates that the transaction uses the extended format.
4645

4746
How do old nodes treat marker and flag for SegWit transactions?
4847

49-
<a
50-
href="https://chat.bitcoinsearch.xyz/?author=holocat&question=How%2520do%2520old%2520nodes%2520treat%2520marker%2520and%2520flag%2520for%2520SegWit%2520transactions%253F"
51-
target="_blank"
52-
>
53-
Answer here
54-
</a>
48+
-> <a href="https://chat.bitcoinsearch.xyz/?author=holocat&question=How%2520do%2520old%2520nodes%2520treat%2520marker%2520and%2520flag%2520for%2520SegWit%2520transactions%253F" target="_blank" rel="noopener noreferrer">Answer here</a>

decoding/musig.mdx

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,11 @@ title: "MuSig"
33
date: 2024-01-25T15:32:14Z
44
lastmod: "2024-07-26"
55
draft: false
6-
category: Scripts
6+
category: Taproot
77
layout: TopicBanner
8-
order: 7
9-
icon: "FaUsers"
8+
order: 5
9+
icon: "FaHashtag"
1010
images: ["/bitcoin-topics/static/images/topics/thumbnails/musig-thumbnail.webp"]
11-
parent: taproot
1211
---
1312

1413
By the end of this article, we want Alice, Bob, and Carol to sign a transaction using MuSig.

decoding/nonce-reuse-attack.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,14 @@ title: "Nonce Reuse Attack"
33
date: 2024-01-25T15:32:14Z
44
lastmod: "2024-07-26"
55
draft: false
6-
category: Scripts
6+
category: Taproot
77
layout: TopicBanner
8-
order: 3
8+
order: 4
9+
icon: "FaHashtag"
910
images:
1011
[
1112
"/bitcoin-topics/static/images/topics/thumbnails/nonce-reuse-attack-thumbnail.webp"
1213
]
13-
parent: taproot
1414
---
1515

1616
### What is a Nonce in Digital Signatures?

decoding/schnorr-signature.mdx

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,10 @@ title: "Schnorr Signature"
33
date: 2024-01-25T15:32:14Z
44
lastmod: "2024-07-26"
55
draft: false
6-
category: Scripts
6+
category: Taproot
77
layout: TopicBanner
8-
order: 2
9-
icon: "FaUsers"
10-
parent: taproot
8+
order: 3
9+
icon: "FaHashtag"
1110
images:
1211
[
1312
"/bitcoin-topics/static/images/topics/thumbnails/schnorr-signature-thumbnail.png"

decoding/tagged-hashes.mdx

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,15 +3,14 @@ title: "Tagged Hashes"
33
date: 2024-01-25T15:32:14Z
44
lastmod: "2024-07-26"
55
draft: false
6-
category: Scripts
6+
category: Taproot
77
layout: TopicBanner
8-
order: 1
9-
icon: "FaUsers"
8+
order: 2
9+
icon: "FaHashtag"
1010
images:
1111
[
1212
"/bitcoin-topics/static/images/topics/thumbnails/tagged-hashes-thumbnail.jpg"
1313
]
14-
parent: taproot
1514
---
1615

1716
Tagged hashes are used throughout the Taproot/Schnorr specification.

decoding/taproot-roadmap.mdx

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
title: "Taproot Roadmap"
3+
date: 2024-01-25T15:32:14Z
4+
lastmod: "2024-07-26"
5+
draft: false
6+
category: Taproot
7+
layout: TopicBanner
8+
order: 1
9+
icon: "FaHashtag"
10+
images:
11+
[
12+
"/bitcoin-topics/static/images/topics/thumbnails/taproot-roadmap-thumbnail.webp"
13+
]
14+
---
15+
16+
<div className="full-width">
17+
<div className="w-full">
18+
<div className="dark:hidden w-full rounded-lg">
19+
<SvgDisplay
20+
src="/bitcoin-topics/static/images/topics/taproot/taproot-roadmap.svg"
21+
height="auto"
22+
/>
23+
</div>
24+
<div className="hidden dark:block w-full rounded-lg">
25+
<SvgDisplay
26+
src="/bitcoin-topics/static/images/topics/taproot/taproot-roadmap.svg"
27+
height="auto"
28+
/>
29+
</div>
30+
</div>
31+
</div>

decoding/taproot.mdx

Lines changed: 0 additions & 51 deletions
This file was deleted.

decoding/transaction-structure.mdx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,11 @@ To get the raw transaction data, run:
4040

4141
The output will be the serialized transaction format (A long hexadecimal string representing all transaction data).
4242

43+
<CodeSnippet
44+
code="010000000114e68f759adcfe66c6aa77d38dc0816cbecf3e9e12d76794f3f9e34c9b1a6e5e000000006b483045022100b18dd5124cf2fcd31af3747a55ed941867f781c340007d9d86dae9e04fa8933f02200bdf817b2e6122ba97b8de40541728ead3988df7462241d6ce70e0f6788e126c012102cd3dfbe89ebca9ee2cfeb5d36234c7d33bce1c329f8a0a318271a48fb9d259d2ffffffff0132aa3200000000002251205805e61a8cc830846e039fa137e791c65b489c9083d14d05a26caebb10d9bf7600000000"
45+
language="text"
46+
showLineNumbers={false}
47+
/>
4348
<ExpandableAlert title="What is Serialization?" type="info" expandable={false}>
4449
Serialization is the process of converting structured data into a compact
4550
format (in this case, a hex string) that can be easily stored and

0 commit comments

Comments
 (0)