Skip to content

Added some clarity to the Right-most-output-bits #1601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
livebe01 merged 1 commit into from
Aug 13, 2025
Merged

Added some clarity to the Right-most-output-bits #1601

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/xof/sections/04-testtypes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ MCT(Msg, MaxOutLen, MinOutLen, OutLenIncrement)
}
----

NOTE: For the "Rightmost_Output_bits % Range" operation, the Rightmost_Output_bits bit string should be interpretted as a little endian-encoded number.
NOTE: For the "Rightmost_Output_bits % Range" operation, the Rightmost_Output_bits bit string should be interpreted as a little endian-encoded number, where the first 8-bits are the most-siginicant byte.

[[ParallelHash-MCT]]
==== ParallelHash Monte Carlo Test
Expand Down Expand Up @@ -89,7 +89,7 @@ MCT(Msg, MaxOutLen, MinOutLen, OutLenIncrement, MaxBlockSize, MinBlockSize)
}
----

NOTE: For the "Rightmost_Output_bits % Range" operation, the Rightmost_Output_bits bit string should be interpretted as a little endian-encoded number. For "Right(Rightmost_Output_bits, 8) % BlockRange", the bit string resulting from the "Right(Rightmost_Output_bits, 8)" operation should be interpretted as a little endian-encoded number.
NOTE: For the "Rightmost_Output_bits % Range" operation, the Rightmost_Output_bits bit string should be interpreted as a little endian-encoded number, where the first 8-bits are the most-siginicant byte. For "Right(Rightmost_Output_bits, 8) % BlockRange", the bit string resulting from the "Right(Rightmost_Output_bits, 8)" operation should be interpreted as a little endian-encoded number.

[[TupleHash-MCT]]
==== TupleHash Monte Carlo Test
Expand Down Expand Up @@ -129,7 +129,7 @@ MCT(Tuple, MaxOutLen, MinOutLen, OutLenIncrement)
}
----

NOTE: For "Left(workingBits, 3) % 4", the bit string resulting from the "Left(workingBits, 3)" operation should be interpretted as a little endian-encoded number. For the "Rightmost_Output_bits % Range" operation, the Rightmost_Output_bits bit string should be interpretted as a little endian-encoded number.
NOTE: For "Left(workingBits, 3) % 4", the bit string resulting from the "Left(workingBits, 3)" operation should be interpreted as a little endian-encoded number. For the "Rightmost_Output_bits % Range" operation, the Rightmost_Output_bits bit string should be interpreted as a little endian-encoded number, where the first 8-bits are the most-siginicant byte.

[xof-mct-functions]
==== Functions Used in the Monte Carlo Tests for XOFs
Expand Down