Clarify need for Commitment Input on input side

iotaledger · Mar 5, 2024 · 84dad0e · 84dad0e
1 parent 7d7cbf0
commit 84dad0e
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/tips/TIP-0038/tip-0038.md b/tips/TIP-0038/tip-0038.md
@@ -513,7 +513,7 @@ defined in the <i>Timelock Unlock Condition</i>.
 
 #### Additional Transaction Semantic Validation Rules
 
-- A _Commitment Input_ must be present.
+- If an input of a transaction contains a _Timelock Unlock Condition_ a _Commitment Input_ must be present.
 - Let `Future Bounded Slot Index` be given by `Commitment Index + Min Committable Age` where `Commitment Index` is the
   slot index of the commitment input.
 - An output that has a <i>Timelock Unlock Condition</i> specified must only be consumed and unlocked in a transaction if
@@ -569,7 +569,7 @@ For the rationale behind the index choices for the slot index conditions in this
 
 #### Additional Transaction Semantic Validation Rules
 
-- A _Commitment Input_ must be present.
+- If an input of a transaction contains an _Expiration Unlock Condition_ a _Commitment Input_ must be present.
 - Let `Future Bounded Slot Index` be given by `Commitment Index + Min Committable Age`, where `Commitment Index` is the
   slot index of the commitment input.
 - Let `Past Bounded Slot Index` be given by `Commitment Index + Max Committable Age`, where `Commitment Index` is the