Finshing touches

Author: moonsettler

bip-0442.md

@@ -33,7 +33,7 @@ Stack operation:
 - Pop `x2` and `x1` from the stack.
 - Push `pc` onto the stack.
 
-[^1]: The number of SHA256 blocks is minimized in typical use cases. The tag can be pre-computed as a SHA256 mid-state, requiring only 2 hash cycles for two 32-byte items, or 1 for two smaller items.
+[^1]: The number of SHA256 blocks is minimized in typical use cases. The tag can be precomputed as a SHA256 mid-state, requiring only two hash cycles for two 32-byte items, or one for two smaller items.
 
 ## Motivation
 
@@ -86,7 +86,7 @@ OP_CHECKLOCKTIMEVERIFY                 # <1>, <S+1>
 OP_DROP                                # <1>
 ```
 
-*Note: `state-n-hash` commits to a specific `nLockTime` value for the transaction through `OP_CHECKTEMPLATEVERIFY`; `OP_CHECKLOCKTIMEVERIFY` ensures that the state progression can only go forward (transaction needs to have greater `nLockTime` value than the intermediate state being spent).*
+*Note: `state-n-hash` commits to a specific `nLockTime` value for the transaction through `OP_CHECKTEMPLATEVERIFY`; `OP_CHECKLOCKTIMEVERIFY` ensures that the state progression can only go forward (the transaction needs to have greater `nLockTime` value than the intermediate state being spent).*
 
 #### Channel update script (pseudo-code):
 
@@ -107,6 +107,8 @@ OP_ELSE
 OP_ENDIF
 ```
 
+*Note: `OP_0NOTEQUAL` can be omitted (any non-zero value left on the stack would be accepted by the script interpreter).*
+
 These constructions ensure both parties sign the same pair hash, requiring inclusion of both update and settlement hashes in the witness.
 
 ### In MATT
@@ -213,6 +215,7 @@ This document is licensed under the 3-clause BSD license.
 6. OP_CHECKCONTRACTVERIFY: [BIP-443]
 7. OP_INTERNALKEY: [BIP-349], [BIN-2024-0004]
 8. Tagged hash: [BIP-340]
+9. MuSig2: [BIP-327]
 
 [lnhance]: https://github.com/lnhance/bitcoin
 [eltoo]: https://github.com/instagibbs/bolts/blob/eltoo_draft/XX-eltoo-transactions.md