Add Commitment Input to header commitment rule

iotaledger · Feb 15, 2024 · 688788a · 688788a
1 parent 6607da5
commit 688788a
Showing 1 changed file with 10 additions and 7 deletions.
diff --git a/tips/TIP-0046/tip-0046.md b/tips/TIP-0046/tip-0046.md
@@ -151,7 +151,8 @@ The string format of a Slot Commitment ID is the hexadecimal encoding of the Slo
 
 ## Block Signature
 
-The [_Ed25519 Signature_](https://github.com/iotaledger/tips/blob/tip38/tips/TIP-0038/tip-0038.md#ed25519-signature) is supported.
+The [_Ed25519 Signature_](https://github.com/iotaledger/tips/blob/tip38/tips/TIP-0038/tip-0038.md#ed25519-signature) is
+supported.
 
 ### Signature Creation
 
@@ -455,8 +456,9 @@ syntactically valid if all of the following conditions hold:
 - If a _Basic Block_ contains a transaction payload, the block is valid only if all of the following conditions hold:
   - The Slot Index `Block Slot` corresponding to the `Issuing Time` of a block must be greater or equal than the
     `Creation Slot` of the contained transaction.
-  - If the transaction includes a `Commitment Input`, the `Slot Index` field of the commitment to which the input
-    resolves must be in the closed interval `[Block Slot - Max Committable Age, Block Slot - Min Committable Age]`.
+  - If the transaction includes a `Commitment Input`, then the `Slot Index` from the contained `Commitment ID`:
+    - must be in the closed interval `[Block Slot - Max Committable Age, Block Slot - Min Committable Age]`.
+    - must not exceed the `Slot Index` field of the `Slot Commitment ID` from the block's `Header`.
 
 ### Semantic Validation
 
@@ -471,9 +473,9 @@ information. As such, blocks usually contain a payload. The detailed specificati
 of this TIP. The following table lists all currently specified payloads that can be part of a block and links to their
 specification:
 
-| Payload Name           | Type Value | TIP                                                                               |
-| ---------------------- | ---------- | --------------------------------------------------------------------------------- |
-| No Payload             | -          | -                                                                                 |
+| Payload Name           | Type Value | TIP                                                                                                                               |
+| ---------------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| No Payload             | -          | -                                                                                                                                 |
 | Tagged Data            | 0          | [TIP-53](https://github.com/iotaledger/tips/blob/tip53/tips/TIP-0053/tip-0053.md)                                                 |
 | Transaction            | 1          | [TIP-45](https://github.com/iotaledger/tips/blob/tip45/tips/TIP-0045/tip-0045.md)                                                 |
 | Candidacy Announcement | 2          | [TIP-40 (Candidacy Announcement)](https://github.com/iotaledger/tips/blob/tip40/tips/TIP-0040/tip-0040.md#candidacy-announcement) |
@@ -488,7 +490,8 @@ Let the work score of a _Basic Block_ be defined as follows.
   - If the type is _Candidacy Announcement_ the work score is
     `Work Score Parameters::Data Byte * Candidacy Announcement Size` where:
     - `Candidacy Announcement Size` is the size of the serialized _Candidacy Announcement_.
-  - If the type is _Transaction_ the work score is defined in [TIP-45 (Work Score)](https://github.com/iotaledger/tips/blob/tip45/tips/TIP-0045/tip-0045.md#work-score).
+  - If the type is _Transaction_ the work score is defined in
+    [TIP-45 (Work Score)](https://github.com/iotaledger/tips/blob/tip45/tips/TIP-0045/tip-0045.md#work-score).
 - Return `Work Score Parameters::Block + Payload Score`.
 
 ## Validation Block