Skip to content

Commit 16f2dc7

Browse files
committed
better integrated with updated scripts chapter
1 parent 15eefa2 commit 16f2dc7

2 files changed

Lines changed: 11 additions & 9 deletions

File tree

docs/09_1_Sending_a_Transaction_with_a_Locktime.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -34,20 +34,20 @@ and it's available through `bitcoin-cli` (which is why it's the only
3434
timelock covered in this section). A parallel method, which locks a
3535
transaction with a relative time, is defined in [BIP
3636
68](https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki)
37-
and covered in [§11.3: Using CSV in
38-
Scripts](11_3_Using_CSV_in_Scripts.md).
37+
and covered in [§13.3: Using CSV in
38+
Scripts](13_3_Using_CSV_in_Scripts.md).
3939

40-
> Bitcoin Script further empowers both sorts of timelocks, allowing
41-
for the locking of individual outputs instead of entire
42-
transactions. Absolute timelocks do so with the Script opcode
40+
> Bitcoin Script and its "opcodes" further empowers both sorts of
41+
timelocks, allowing for the locking of individual outputs instead of
42+
entire transactions. Absolute timelocks do so with the Script opcode
4343
OP_CHECKLOCKTIMEVERIFY, which is defined in [BIP
4444
65](https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki)
45-
and covered in [§11.2: Using CLTV in
46-
Scripts](11_2_Using_CLTV_in_Scripts.md), while relative timelocks aare
45+
and covered in [§13.2: Using CLTV in
46+
Scripts](13_2_Using_CLTV_in_Scripts.md), while relative timelocks aare
4747
linked to the Script opcode OP_CHECKSEQUENCEVERIFY, which is defined
4848
in [BIP
4949
112](https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki)
50-
and also covered in [§11.3](11_3_Using_CSV_in_Scripts.md).
50+
and also covered in [§13.3](13_3_Using_CSV_in_Scripts.md).
5151

5252
## Create a Locktime Transaction
5353

docs/09_2_Sending_a_Transaction_with_Data.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,9 @@
33
The final way to vary how you send a basic transaction is to use the
44
transaction to send data instead of funds (or really, in addition to
55
funds). This gives you the ability to embed information in the
6-
blockchain. It is done through a special `OP_RETURN` command.
6+
blockchain. It is done through a special `OP_RETURN` command, which is
7+
another opcode, an element of Bitcoin scripts that we'll meet in
8+
[§11.1](11_1_Understanding_the_Foundation_of_Transactions).
79

810
The catch? It's controversial. Many people think you shouldn't put
911
data onto the Bitcoin chain at all. For a long time, `OP_RETURN` was

0 commit comments

Comments
 (0)