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

Implement Unpublished Immutable Data #4

Open
lionel-faber opened this issue May 21, 2019 · 1 comment
Open

Implement Unpublished Immutable Data #4

lionel-faber opened this issue May 21, 2019 · 1 comment

Comments

@lionel-faber
Copy link
Owner

  • Add structure for Unpublished Immutable data
  • Implement name function that derives data address using the hash of the data and the owner.
  • GET requests must be signed. Only the owner should be able to fetch the data from the network.

Questions:

  • Will this require changes/additions in self_encryption?

Note:

  • The data type must move into the new data types crate
  • All RPCs are between clients and vaults
  • Routing will include only a send(src, dest, payload) API
  • Ownership of the data is non-transferrable
@nbaksalyar
Copy link

To answer one of the questions:

Will this require changes/additions in self_encryption?

No, since self_encryption is agnostic to data types.

It might require some changes in SCL code interfacing with self_encryption, as e.g.: https://github.com/maidsafe/safe_client_libs/blob/11ab01de08ef8ea82852bbb19f06e54b2fa88106/safe_core/src/immutable_data.rs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants