Skip to content

Commit bbd0daf

Browse files
committed
News178: edits to glozow section
1 parent 640be31 commit bbd0daf

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

_posts/en/newsletters/2021-12-08-newsletter.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ and notable changes to popular infrastructure projects.
3737
meeting, highlighting some of the important questions and answers. Click on a
3838
question below to see a summary of the answer from the meeting.*
3939

40-
[Treat Taproot as always active][review club #23512] is a PR by Marco Falke to
41-
make transactions spending taproot outputs standard, regardless of taproot
40+
[Treat taproot as always active][review club #23512] is a PR by Marco Falke to
41+
make transactions spending [taproot][topic taproot] outputs standard, regardless of taproot
4242
deployment status.
4343

4444
{% include functions/details-list.md
@@ -63,9 +63,9 @@ deployment status.
6363

6464
q2="Are there any theoretical issues with the change? For wallet users, is
6565
it possible to lose money?"
66-
a2="With this change, the wallet allows importing taproot descriptors at any
66+
a2="With this change, the wallet allows importing taproot [descriptors][topic descriptors] at any
6767
time, i.e., even when taproot is not active and v1 segwit outputs can be spent
68-
by anyone). This means it's possible to receive bitcoin at a taproot address
68+
by anyone. This means it's possible to receive bitcoin to a taproot output
6969
without taproot being active yet; if the chain also reorgs to a block prior to
7070
709,632, miners (or someone who can get a nonstandard transaction confirmed) can
7171
steal those UTXOs."

0 commit comments

Comments
 (0)