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 a end-user facing demo decentralized application, dapp, on top of Linnia Smart Contract #18

Closed
godfreyhobbs opened this issue Mar 2, 2018 · 10 comments

Comments

@godfreyhobbs
Copy link
Contributor

godfreyhobbs commented Mar 2, 2018

Gitcoin Funding Amount: 0.7 ETH

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 create a new end-user facing demo decentralized application, the dapp, on top of Linnia Smart Contract. We will be awarding the best submission for this task a .7 ETH prize, assuming the below requirements are met.
The dapp must be in the spirit of the following two Linnia papers;

  1. https://github.com/ConsenSys/linnia-resources/blob/master/Technical-Whitepaper.md
  2. 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

  1. Share the answer to riddles with friends via the smart contract permissions
  2. Upload and share data from a fitness tracker API such as the Fitbit API

Requirements

  1. You have read and understood the WIP nature expressed in the README.md
  2. Code must be in a public github repo
  3. Use the Linnia Smart Contracts for some non-trivial end-user facing functionality
  4. Consider use of encryption to keep data secret
  5. Be prepared to present your submission to the linnia team
  6. Be prepared for a review of your code by the linnia team
  7. Open source your solution
  8. Finally, use your imagination
@godfreyhobbs godfreyhobbs changed the title Draft issue create a end-user facing demo decentralized application, dapp, on top of Linnia Smart Contract Mar 6, 2018
@gitcoinbot
Copy link

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

  • If you would like to work on this issue you can claim it here.
  • If you've completed this issue and want to claim the bounty you can do so here
  • Questions? Get help on the Gitcoin Slack
  • $6669.56 more Funded OSS Work Available at: https://gitcoin.co/explorer

@godfreyhobbs godfreyhobbs changed the title create a end-user facing demo decentralized application, dapp, on top of Linnia Smart Contract Create a end-user facing demo decentralized application, dapp, on top of Linnia Smart Contract Mar 6, 2018
@gitcoinbot
Copy link

gitcoinbot commented Mar 10, 2018

Work has been started on the 0.7 ETH (446.54 USD @ $637.91/ETH) funding by:

  1. @DeusEx-Machina
  2. @ottodevs
  3. @himanshupnt
  4. @vaibhavb
  5. @lookfwd

Please work together and coordinate delivery of the issue scope. Gitcoin doesn't know enough about everyones skillsets / free time to say who should work on what, but we trust that the community is smart and well-intentioned enough to work together. As a general rule; if you start work first, youll be at the top of the above list ^^, and should have 'dibs' as long as you follow through.

On the above list? Please leave a comment to let the funder (@owocki) and the other parties involved what you're working, with respect to this issue and your plans to resolve it. If you don't leave a comment, the funder may expire your submission at their discretion.

@godfreyhobbs
Copy link
Contributor Author

Q: Any specific style guide or front-end framework to use?

A: First of all, there is no requirement to submit a web app

However, if you are building a web app then we like the following:

  1. React / redux
  2. material ui (e.g. https://material-ui-next.com/)

@vs77bb
Copy link

vs77bb commented Apr 8, 2018

@DeusEx-Machina @ottodevs @himanshupnt @zoek1 @vaibhavb How goes progress on this one?

@godfreyhobbs Any updates you've received on your side? Happy to pub this out, if it makes sense 🙂

@gitcoinbot
Copy link

Work for 0.7 ETH (301.13 USD @ $430.18/ETH) has been submitted by:

  1. @lookfwd

Submitters, please leave a comment to let the funder (@owocki) (and the other parties involved) that you've submitted you work. If you don't leave a comment, the funder may expire your submission at their discretion.

@lookfwd
Copy link

lookfwd commented Apr 9, 2018

P.S. The submitted code is here.

@lookfwd
Copy link

lookfwd commented Apr 9, 2018

Added Linnia changes that would enable deeper integration section:

Linnia changes that would enable deeper integration

  • The extended use of msg.sender in Linnia, to identify who makes the change, doesn't scale well, when a single caller contract does the changes (in my case MapDomain). There could be a better way to register signatures for people and the ability for a single Provider to sign multiple times (ideally it would allow me to implement the state machine, I use used for). Also self-registered people (Patients) should have some provenance (see next).
  • I would like to map the price to irisScore, but there's not fine-grained control of provenance yet.
  • Accessing FileRecord values through records, is incomplete because of the mapping to tuple, the default getter does. Now I have to use (patient, sigCount, irisScore, recordType, ipfsHash, timestamp) = hub.recordsContract().records(resourceId) but this means that a) I lose signatures, which might be ok, but also b) if the order changes there might be a problem.
  • I would like to map endpoint to some userdata in FileRecord. It could also be stored in metadata somehow.
  • I now have my own metadata structure. Metadata (both Contextual and Quality) as described in Data and Metadata sound like exactly what I try to do with that data structure. If we were generalising to create a News Portal (see below) such metadata would be the taxonomy of the article as well as the teaser (thumbnail and first few lines of the text).

Note that the theme here is, in general, generic web content "gating" by using single-use URLs that consume credits as you browse. It's easy to adapt the code of Zelp to create e.g. news portals or forums, where the visitor adds Ether and then browses the metadata (teaser) of the content and has to make micro-payments to access gated content. Further roles and access control (by mapping and extending the Patient/Provider roels) can enable/disable and rate content as e.g. Editors, moderators etc.

@godfreyhobbs
Copy link
Contributor Author

@DeusEx-Machina @ottodevs @himanshupnt @zoek1 @vaibhavb @lookfwd @osamakhn
Please try to finish your work by the end of this week.

@gitcoinbot
Copy link

The funding of 0.7 ETH (446.54 USD @ $637.91/ETH) attached to this issue has been approved & issued to @lookfwd.

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

5 participants
@lookfwd @godfreyhobbs @vs77bb @gitcoinbot and others