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 manifest MVP #499

Open
a-stacey opened this issue Jul 10, 2019 · 0 comments
Open

Implement manifest MVP #499

a-stacey opened this issue Jul 10, 2019 · 0 comments
Labels

Comments

@a-stacey
Copy link
Contributor

a-stacey commented Jul 10, 2019

Up until now we have had 3 major practicality issues:

  • Walking the supply chain.
  • Authorization Model
  • Data sharing

Manifests are one solution to walking the supply chain.

We propose that the manifests structure looks like:
[ParentSignature] -> [] = new manifest / first entry in a manifest, [a] = normal transaction, [a, ...] = aggregation event.
EventID
Timestamp
GLN
EventHash (Possibly)
Signature -> (Composite of all the other fields in the event structure signed with the organisations public key)

We intend to provide an MVP solution of/for Manifests as an enabler of discovering solutions for the other problems and to see if this solution works in practice and so that we can demonstrate our proposed architecture.

@a-stacey a-stacey added the Epic label Jul 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant