Skip to content
New issue

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

optimising fork reference interpretation #33

Open
nugaon opened this issue Feb 11, 2022 · 0 comments
Open

optimising fork reference interpretation #33

nugaon opened this issue Feb 11, 2022 · 0 comments
Labels

Comments

@nugaon
Copy link
Member

nugaon commented Feb 11, 2022

By default, the serialized fork reference is pointing to another Mantaray node.
Nevertheless, in plenty of cases, the leaf nodes only have address to a content saved on Swarm and its corresponding metadata can be serialized under forkMetadata.
mantaray-js could stick to a metadata format in forks that change the default fork reference interpretation in order to save unnecessary Mantaray node creations.

The applied metadata format has to be approved in Fair Data Improvement Proposals

@bee-runner bee-runner bot added the issue label Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant