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

Create claim module #27

Closed
aaronc opened this issue Mar 30, 2019 · 0 comments · Fixed by #30
Closed

Create claim module #27

aaronc opened this issue Mar 30, 2019 · 0 comments · Fixed by #30
Assignees

Comments

@aaronc
Copy link
Member

aaronc commented Mar 30, 2019

This is to replace or at least complement the current esp module with something more generic, offloading the responsibility of whether a claim is valid to other logic.

Use Cases and Rationale:
The claims model is a generic way to represent who said what and why. The what is contained in the data graph - the claim itself, and who is managed by the claims module which allows many entities to assert the same claim. Many times claims are going to be signed by trusted third parties. So what creates the audit trail if that is not contained in the claim? This is where evidence fits in - oftentimes there might be off-chain data that is even just scanned paper documents which represents what the claim means or somebody has done thorough investigation and produced a report. These can all be linked to a claim via evidence which is the "why the claim is true" and the claim signature effectively who said what and why.

Claims themselves will now to be stored in the data module which will eventually abstract "graph descriptors" that include what the graph schema and subjects (i.e GeoAddress's or sdk.AccAddress's. The claim module just includes a very basic apparatus for signing claims.

A claim signature includes three basic pieces of data:

  • the claim itself (a DataAddress)
  • the signer(s) ([]sdk.AccAddress)
  • any supporting evidence ([]DataAddress) - on or off chain graphs, and importantly off-chain raw data which could be photographs, PDFs, etc.
  • event/claim time - the time which the ecological claim refers to e.g. when a farmer received organic certification.
  • blockchain time - the time the claim signature was recorded on (and off) chain

One important piece of behavior:
Given an existing claim that is already signed
When somebody tries to sign the same claim
Then new evidence and/or signatures will be recorded if any

@aaronc aaronc added this to the 0.4 milestone Mar 30, 2019
@aaronc aaronc added the backlog label Mar 30, 2019
aaronc added a commit that referenced this issue Apr 1, 2019
@ghost ghost assigned aaronc Apr 1, 2019
@ghost ghost added Status: In Progress and removed backlog labels Apr 1, 2019
@aaronc aaronc modified the milestones: 0.4, 0.5 Apr 8, 2019
aaronc added a commit that referenced this issue Apr 10, 2019
aaronc added a commit that referenced this issue Apr 25, 2019
@ghost ghost removed the Status: In Progress label Apr 25, 2019
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

Successfully merging a pull request may close this issue.

1 participant