Skip to content
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: LNP-BP/LNPBPs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: a89f3986dcee688db784d9c26c5850f6c63c569e
Choose a base ref
..
head repository: LNP-BP/LNPBPs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: a76d796bd867e1038d19e6076f441229aa5b451a
Choose a head ref
Showing with 3 additions and 3 deletions.
  1. +3 −3 lnpbp-0006.md
6 changes: 3 additions & 3 deletions lnpbp-0006.md
Original file line number Diff line number Diff line change
@@ -44,11 +44,11 @@ TBD

Tapret commitment is structured as an `OP_RETURN`-based script, containing the
commitment to the LNPBP-4 message, constructed under multiple protocols. The
commitment script (**tapret leaf script**) always consists of 64
bytes[why-64-bytes].
commitment script (**tapret leaf script**) always consists of
[64 bytes][why-64-bytes].

The leaf with the tapret leaf script is always put into the same depth of the
taproot script tree, and this depth is 1[why-depth-1] (in 0-based indexing of
taproot script tree, and this [depth is 1][why-depth-1] (in 0-based indexing of
depth levels, where depth 0 corresponds to the merkle tree root). The commitment
is always put into the rightmost node of the tree by using consensus ordering
of the nodes, as it is defined in BIP-341 merkle path construction