-
We’ve done a lot to solidify the concepts in IPLD and the tools for working with it in Go and JS.
It’s time to take what we’ve learned and create a much improved “Getting Started” section of the RE…
-
At the moment IPLD only supports inline definitions for
- maps
- lists
- links
https://github.com/ipld/ipld/blob/d8bac572573a30ab49f9aa9d071448b919c84f43/specs/schemas/schema-schema.ipldsch.js…
-
In the space of a few weeks we have two separate discussion about needing a place to define entries in the multicodec table, including test fixtures:
* Murmur3 specifics needing to be pinned down p…
rvagg updated
12 months ago
-
Link to CAR file needs to be updated from old to:
https://ipld.io/specs/transport/car/
-
The block sending side in CAR mirror sends CAR files. However, some implementations require a header to have at least one root CID (iroh-car being one of them). It's somewhat unclear whether CAR files…
-
My understanding is that the idea behind `{"/": }` is when Cid are represented as links. Should they _always_ be serialized like this. In many cases a Cid acts more as an identifier than a link.
…
-
Explorer should show `mtime` and `mode` when present in `dag-pb`, to make it easy to spot difference in optional metadata.
Right now two CIDs can have the same files but different `mtime`/`mode` an…
lidel updated
11 months ago
-
Currently, Graphsync is specified as a Protobuf based protocol. This was done to fit the spec at the time it was written and because IPLD CBOR tooling was still incomplete. Now those, we've made a lot…
-
This is because dag-pb stores links under `Links` key, which the spec in this repo doesn't check for. See https://github.com/ipld/js-ipld-dag-pb/blob/master/src/resolver.js#L28 for how this is handled…
-
In https://github.com/ipld/specs/pull/282 I'm claiming that the `map` (`bitfield`) is addressed here in the same way as the specification, and therefore the reference implementation for the IPLD HashM…
rvagg updated
4 years ago