From 84dad0eaff8867951b197e5aaad6388eb3141085 Mon Sep 17 00:00:00 2001 From: Philipp Gackstatter Date: Tue, 5 Mar 2024 08:31:56 +0800 Subject: [PATCH] Clarify need for Commitment Input on input side --- tips/TIP-0038/tip-0038.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tips/TIP-0038/tip-0038.md b/tips/TIP-0038/tip-0038.md index 40dea5a09..1d7d82976 100644 --- a/tips/TIP-0038/tip-0038.md +++ b/tips/TIP-0038/tip-0038.md @@ -513,7 +513,7 @@ defined in the Timelock Unlock Condition. #### 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 Timelock Unlock Condition 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