Clarify representation of cryptographic hash length. #88
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
msporny
requested review from
TallTed,
brentzundel,
decentralgabe,
dlongley,
iherman,
jandrieu,
longpd and
selfissued
decentralgabe
approved these changes
Sep 2, 2024
selfissued
requested changes
Sep 2, 2024
iherman
approved these changes
Sep 3, 2024
dlongley
approved these changes
Sep 3, 2024
TallTed
reviewed
Sep 3, 2024
msporny
force-pushed
the
msporny-hash-length
branch
from
5b29fa2 to
29f350c
Compare
Co-authored-by: Dave Longley <dlongley@digitalbazaar.com>
iherman
approved these changes
Sep 8, 2024
|
Editorial, multiple reviews, changes requested and made, no objections, merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is an attempt to address issue #65 by clarifying the cryptographic hash length and encoding.
Preview | Diff