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 precise sharing permissions through decentralized policy-based permissions. The current contract, LinniaPermissions.sol, only supports (True|False) permissions. We want your help to improve this. We are expecting the improvements in the code plus an explanation document. Decentralized policy-based permissions 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 policy-based permissions algorithm must be in the spirit of the following two Linnia papers;

https://github.com/ConsenSys/linnia-resources/blob/master/Technical-Whitepaper.md
https://github.com/ConsenSys/linnia-resources/blob/master/Introducing%20Linnia.pdf

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

Policy-based permissions could include time-limited sharing
Policy-based permissions could include geography limited sharing
Policy-based permissions may consider data governance rules such as HIPAA or GDPR
Policy-based permissions may include at rest and in-flight restrictions

Requirements

You have read and understood the WIP nature expressed in the README.md
The algorithm must:
1. Leverage the power of decentralization
2. Encompass the consumer incentives of the Linnia data marketplace
3. Allow trustless interaction
4. Be usable and easy to understand
It must be impossible for any party to game policy-based permissions
The various parties involved in policy-based permissions include the following;
1. Individual peers
2. Social groups or communities
3. Connected devices (e.g. IoT, Bluetooth)
4. Central authorities hosted on digital platforms (i.e. apps)
5. Central authorities hosted on physical platforms using IT (i.e. doctors, government)
6. AI and Machine learning platforms with or without blind computation capabilities
7. Decentralized applications
The person owning the data must remain 100% in control at all times policy-based permissions algorithm must be end-to-end
Must NOT be limited to the medical
Your ideas must be submitted as Documentation and Code in a fork of this repo
Consider 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
Provide two or three real-world non-trivial end-user facing use cases for your policy-based permissions algorithm
Be prepared to present your submission to the Linnia team and the Linnia community
Be prepared for a review of your code by the Linnia team and the Linnia community
Finally, use your imagination and have fun

Jun 01 '18 18:06 godfreyhobbs

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 0.7 ETH (397.16 USD @ $567.38/ETH) attached to it.

If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
Questions? Checkout Gitcoin Help or the Gitcoin Slack
$25,900.02 more funded OSS Work available on the Gitcoin Issue Explorer

Jun 10 '18 13:06 gitcoinbot

Really excited about Linnia as a whole - would love to get started with contributing by doing some work on this. How about a spec proposal to start (which would likely turn into the documentation component)? And then after some feedback I could provide an implementation?

Jul 01 '18 17:07 willdeuschle

@godfreyhobbs mind responding to @willdeuschle here? Know we're a bit late to the party here 🙂

Aug 10 '18 22:08 gitcoinbot

Is this still open for contribution?

Sep 28 '18 07:09 pranay01

@pranay01 yes

Oct 01 '18 00:10 godfreyhobbs

hey @pranay01 - Frank from Gitcoin here - are you still interested in working on the bounty?

Oct 24 '18 23:10 frankchen07

Consider runing this as cooperative instead of Traditional

Oct 28 '18 21:10 adamskrodzki

@adamskrodzki Let me know if you need help getting started. Are you at Devcon?

Oct 30 '18 12:10 godfreyhobbs

Unfortunately I'm not. I will later this week dive into this contracts

Oct 30 '18 20:10 adamskrodzki

@adamskrodzki Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] warning (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

Nov 04 '18 17:11 gitcoinbot

@adamskrodzki Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] warning (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

Nov 04 '18 17:11 gitcoinbot

Yes I'm working on issue

Nov 04 '18 20:11 adamskrodzki

Hey @adamskrodzki any updates on this?

Nov 21 '18 08:11 spm32

Hey there, I have some thoughts on this subject. I just wanted to check if the issues addressed in this bounty are still relevant as it's been some time.

Feb 13 '19 17:02 tspoff

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Workers have applied to start work.

These users each claimed they can complete the work by 1 year, 6 months ago. Please review their action plans below:

1) kitsanatanchai has applied to start work (Funders only: approve worker | reject worker).

ผมต้องทำยังไงถึงจะได้เงินมาใช้

Learn more on the Gitcoin Issue Details page.

Jan 27 '20 21:01 gitcoinbot