We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
There's a standard for self-describing hashes called Multihash.
A multihash follows the TLV (type-length-value) pattern.
For example, the multihash value 122041dd7b6443542e75701aa98a0c235951a28a0d851b11564d20022ab11d2589a8 indicates:
122041dd7b6443542e75701aa98a0c235951a28a0d851b11564d20022ab11d2589a8
12
20
41dd7b6443542e75701aa98a0c235951a28a0d851b11564d20022ab11d2589a8
This is already used in IPFS, but is intended for wider adoption to support portability and future-proofing.
It would be great to have an encoding block for producing a multihash of a byte string.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There's a standard for self-describing hashes called Multihash.
A multihash follows the TLV (type-length-value) pattern.
For example, the multihash value
122041dd7b6443542e75701aa98a0c235951a28a0d851b11564d20022ab11d2589a8
indicates:12
indicates that the hash function variant is sha2-25620
indicates that hash length is 32 bytes41dd7b6443542e75701aa98a0c235951a28a0d851b11564d20022ab11d2589a8
is the hash valueThis is already used in IPFS, but is intended for wider adoption to support portability and future-proofing.
It would be great to have an encoding block for producing a multihash of a byte string.
The text was updated successfully, but these errors were encountered: