ConsenSysMesh / ConsenSysMesh/Stow-Smart-Contracts

Help create Linnia IRIS (InfoRmation Integrity Score) score algorithm

Open
#33 19 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
55
Forks
33
PR merge metrics
No merged PRs in 30d

Description

# Context
Linnia is a core component of the future of the web; Web 3.0. Linnia is a new Ethereum Blockchain protocol that brings the power of decentralization to your lifetime data. The Linnia protocol provides the foundation for secure decentralized applications in multiple spheres including the sphere of electronic healthcare records.
# What
We would like to incentivize you, as a member of the Gitcoin/Bounties family, to innovate and help create the Linnia IRIS score algorithm. The IRIS stands for **InfoRmation Integrity Score**. The Linnia IRIS score is a critical part of the linnia protocol. We will be awarding the submission for this task a .7 ETH bounty, assuming the below requirements are met.
The proposed Linnia IRIS score algorithm must be in the spirit of the following two Linnia papers;
1. https://github.com/ConsenSys/linnia-resources/blob/master/Technical-Whitepaper.md
1. https://github.com/ConsenSys/linnia-resources/blob/master/Introducing%20Linnia.pdf

In particular, the following section describes the IRIS score:

1. https://github.com/ConsenSys/linnia-resources/blob/master/Technical-Whitepaper.md#6-quality-scoring-with-iris

Note: Linnia is a WORK IN PROGRESS. The Linnia smart contracts are only a small subset of what is described in these papers.

# Our Ideas

1. IRIS score should increase as the number of attestations increase
1. IRIS score may consider the following:
1. Attestations
1. Provenance
1. Metadata including keywords
1. User Roles
1. IRIS score of zero indicates junk or garbage data
1. IRIS score must reflect a real-world value

# Requirements

1. You have read and understood the WIP nature expressed in the README.md
1. It must be impossible to `game` the IRIS score algorithm
1. IRIS score algorithm must work end-to-end
1. Must NOT be limited to the medical
1. Your ideas must be submitted as Documentation and Code in a fork of this repo
1. Consider the use of encryption to keep data secure. The computation must not leak or reveal any information related to the nature of the underlying encrypted data
1. Provide two or three real-world non-trivial end-user facing use cases for your IRIS score algorithm
1. Be prepared to present your submission to the Linnia team and the Linnia community
1. Be prepared for a review of your code by the Linnia team and the Linnia community
1. Finally, use your imagination

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.