Skip to content

Conversation

kashepavadan
Copy link
Contributor

@kashepavadan kashepavadan commented Sep 25, 2025

1. What does this PR implement?

Solves issue #1749

2. Does the code have enough context to be clearly understood?

Yes, see issue

3. Who are the specification authors and who is accountable for this PR?

@megonen @danielSanchezQ @thomaslavaur

4. Is the specification accurate and complete?

Yes

5. Does the implementation introduce changes in the specification?

No, it aligns the code with the spec

Checklist

Warning

Do not merge the PR if any of the following is missing:

  • 1. The PR title follows the Conventional Commits specification.
  • 2. Description added.
  • 3. Context and links to Specification document(s) added.
  • 4. Main contact(s) (developers and specification authors) added
  • 5. Implementation and Specification are 100% in sync including changes. This is critical.
  • 6. Link PR to a specific milestone.

@kashepavadan kashepavadan changed the title Fix row commit hash to output 31 bytes fix(kzgrs): Fix row commit hash to output 31 bytes Sep 25, 2025
Copy link
Collaborator

@danielSanchezQ danielSanchezQ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch @kashepavadan !

@danielSanchezQ danielSanchezQ added this to the Iteration 15 milestone Sep 26, 2025
@kashepavadan kashepavadan reopened this Sep 26, 2025
@kashepavadan kashepavadan merged commit 2d16297 into master Sep 26, 2025
23 of 25 checks passed
@kashepavadan kashepavadan deleted the dank/h31 branch September 26, 2025 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants