Convert functions for IPFS CID v0 to 32 byte hex string and back #229
Conversation
This file contains 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
… `byte32_to_ipfscidv0`) - added `base58>=2.1.0` package to setup.py requirements - added tests to test/steps/steps.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 adds two functions to util.py module to convert between IPFS CID v0 strings to 32 bytes hex strings that fits Algorand Standard Asset's metadatahash field.
This very simple contribution (NO BOUNTY) tries to solve integration of IPFS content identifiers to ASA fields which is a better way in comparison to method already in practice (ASA transactions NOTE field to include IPFS CID).