-
We currently include return values in receipts but not their codecs.
The last part of https://github.com/filecoin-project/ref-fvm/issues/987.
-
As alluded to in #262 we'd like to describe our services using IPLD schemas. We are however unable to fully describe protocol because there is no notion of function so it is impossible to describe a t…
-
This issue is to track progress of IPLD and WebAssembly integration.
Stuff to track:
- WASM ABIs for reading IPLD nodes
- WASM ABIs for representing IPLD nodes for ADLs
- Signaling WASM when pas…
-
This is somewhat relates to #63 as it could be an alternative or one could be enabled by the other. At the moment with IPLD all the links are public even if content it links to isn't. However as I poi…
-
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…
-
The homepage https://ipld.io refers to "IPLD". This should be defined on first use as "InterPlanetary Linked Data".
-
In theory the Filecoin network supports retrieving partial data using IPLD selectors.
This is a cost-effective way to retrieve only the data we need from a Piece.
-
We have an [IPLD schema language](https://ipld.io/docs/schemas/) and [JS tooling](https://github.com/ipld/js-ipld-schema) around it. We should find a way to integrate it into this library, specificall…
-
One of the ideas of IPLD is that it defines a Data Model that is independent of the underlying codec. You can leverage existing formats like CBOR, JSON or Protocol Buffers or create your own special p…
-
It's important for content-addressing to have the same endianness for We should either have a generic rule or have every codec should have a section about endianness.
I propose that we write in a …