Skip to content
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.

IPLD v2: Laying out Future plans #23

Closed
RichardLitt opened this issue Sep 23, 2016 · 1 comment
Closed

IPLD v2: Laying out Future plans #23

RichardLitt opened this issue Sep 23, 2016 · 1 comment
Labels
status/deferred Conscious decision to pause or backlog

Comments

@RichardLitt
Copy link
Contributor

I think it would be great if we could have a place to discuss future plans for IPLD. I propose we use this issue.

Specifically, I have seen transformations, programmable data & light verifiable proofs mentioned.

For example:

  • What are or could be important about proof-of-membership, proof-of-non-membership, proof-of-consistency?
  • How could we use transformations to do sharding, or computing on IPLD objects?
  • What other communities should we look at, to emulate going forward? (Such as distributed systems community mentioned, ie. Chord and Spark).

If there is a better way to phrase this issue, I am all-ears. Might be good to split it up into a few issues.

@nicola nicola changed the title Laying out Future plans IPLD v2: Laying out Future plans Sep 26, 2016
@nicola nicola mentioned this issue Oct 3, 2016
2 tasks
@daviddias daviddias added the status/deferred Conscious decision to pause or backlog label Mar 19, 2018
@rvagg
Copy link
Member

rvagg commented Aug 14, 2019

Closing due to staleness as per team agreement to clean up the issue tracker a bit (ipld/team-mgmt#28). This doesn't mean this issue is off the table entirely, it's just not on the current active stack but may be revisited in the near future. If you feel there is something pertinent here, please speak up, reopen, or open a new issue. [/boilerplate]

@rvagg rvagg closed this as completed Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status/deferred Conscious decision to pause or backlog
Projects
None yet
Development

No branches or pull requests

3 participants