add feat: ipfs dag put #338
Open
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
|
Hey @DougAnderson444 ! I just DM'ed you on Twitter about this, so that we can perhaps find a time to discuss this PR and the general direction of the Arweave+IPFS bridge. Let me know! Thanks again for contributing, |
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 is a potential pull request to address #337 to add the feature of ipfs dag put (object) so we can enable Arweave nodes to also be ipfs object stores.
Note that my Erlang and Arweave node knowledge is minimal, but so are my changes. I did what I saw would be needed to add this feature within my knowledge of the IPFS DAG. Please review accordingly. Open to any editions you may deem fit.