Skip to content

Commit ffb696e

Browse files
jrakibijrakibi
committed
add transaction modules content ( 8 new topics)
1 parent 279be43 commit ffb696e

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+1501
-4
lines changed

‎decoding/bitcoin-history.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Bitcoin History"
33
date: 2024-07-05T15:32:14Z
44
lastmod: "2024-07-06"
55
draft: false
6-
category: History
6+
category: Introduction
77
layout: TopicLayout
88
icon: "FaHistory"
99
order: 2

‎decoding/fee-calculation.mdx

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

‎decoding/fee-rate.mdx

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

‎decoding/inputs.mdx

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

‎decoding/locktime.mdx

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

‎decoding/marker-flag.mdx

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
title: "Marker and Flag"
3+
date: 2024-01-25T15:32:14Z
4+
lastmod: "2024-07-26"
5+
draft: false
6+
category: Transactions
7+
layout: TopicBanner
8+
order: 3.2
9+
icon: "FaClipboardList"
10+
images: ["/bitcoin-topics/static/images/topics/thumbnails/musig-thumbnail.webp"]
11+
parent: "transaction-structure"
12+
---
13+
14+
<TransactionCreation enabledFields={["marker", "flag"]} />
15+
16+
The marker and flag are optional fields introduced with **SegWit**.
17+
18+
They indicate that a transaction uses the segregated witness structure defined in **BIP144**.
19+
Witness data is required for inputs locked by **P2WPKH**, **P2WSH**, or **P2TR**.
20+
21+
## Marker
22+
23+
Marker indicates that the transaction uses the extended format.
24+
25+
- Marker is **1 byte**.
26+
- Must always be `0x00` to signal a SegWit transaction.
27+
28+
## Flag
29+
30+
- The flag is **1 byte**.
31+
- It is currently set to `0x01` in all SegWit transactions.
32+
- Future upgrades may use different flags.
33+
34+
<ExpandableAlert
35+
title="Note: Legacy Compatibility"
36+
type="info"
37+
expandable={false}
38+
>
39+
If a transaction doesn’t include witness data, marker and flag are omitted.
40+
</ExpandableAlert>
41+
42+
### Question
43+
44+
How do old nodes treat marker and flag for SegWit transactions?
45+
46+
<a
47+
href="https://chat.bitcoinsearch.xyz/?author=holocat&question=How%2520do%2520old%2520nodes%2520treat%2520marker%2520and%2520flag%2520for%2520SegWit%2520transactions%253F"
48+
target="_blank"
49+
>
50+
Answer here
51+
</a>

‎decoding/musig.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -438,7 +438,11 @@ Where:
438438
### Final Signature
439439

440440
The final aggregate signature is:
441-
<code>(R<span className="text-xs align-sub">agg</span>, s<span className="text-xs align-sub">agg</span>)</code>
441+
442+
<code>
443+
(R<span className="text-xs align-sub">agg</span>, s
444+
<span className="text-xs align-sub">agg</span>)
445+
</code>
442446

443447
This pair can be verified using <code>P<span className="text-xs align-sub">agg</span></code> and the message `m`.
444448

‎decoding/network-propagation.mdx

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

‎decoding/outputs.mdx

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

‎decoding/pushdata-opcodes.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,10 @@ In bitcoin's scripting language, several opcodes are used to push data onto the
2323
4. **OP_1NEGATE**: Pushes the number -1 onto the stack.
2424

2525
<ExpandableAlert title="Maximum Data Size" type="warning" expandable={false}>
26-
Due to practical limitations and security considerations, the maximum amount of data that can be pushed in a single operation is **520
27-
bytes**. As such, the **OP_PUSHDATA4** opcode is never used in practice (it allows for pushing 65536-4294967295 bytes).
26+
Due to practical limitations and security considerations, the maximum amount
27+
of data that can be pushed in a single operation is **520 bytes**. As such,
28+
the **OP_PUSHDATA4** opcode is never used in practice (it allows for pushing
29+
65536-4294967295 bytes).
2830
</ExpandableAlert>
2931

3032
<ExpandableAlert

0 commit comments

Comments
 (0)