notes on canonicalization, dag traversal order
- Dominant language
- Go
- Stars
- 175
- Forks
- 54
- Avg merge
- 6d 5h
- Merged PRs (30d)
- 4
Description
@whyrusleeping said (in the filecoin community slack)
---
@jbenet i’ll do a pass on canonicalization for the car format, but one thing i’m thinking through right now is that you can’t just naively CAR things up and store them in a sector.
For example if you tried to store the filecoin blockchain this way, it would include all the state trees, and even (depending on a few things) all the data in the network
my question about traversal order is because we need to be able to have a specific traversal order to ensure CAR files are deterministically generated
so the thing being referenced needs to be a selector
@hannahhoward Does the ipld selectors work strictly define graph traversal order?
my question about traversal order is because we need to be able to have a specific traversal order to ensure CAR files are deterministically generated
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.