Closed godfreyhobbs closed 6 years ago
This issue now has a funding of 0.7 ETH (589.11 USD @ $841.58/ETH) attached to it.
Work has been started on the 0.7 ETH (446.54 USD @ $637.91/ETH) funding by:
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.
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:
@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 🙂
Work for 0.7 ETH (301.13 USD @ $430.18/ETH) has been submitted by:
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.
Added Linnia changes that would enable deeper integration section:
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).irisScore
, but there's not fine-grained control of provenance
yet.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.endpoint
to some userdata
in FileRecord
. It could also be stored in metadata
somehow.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.
@DeusEx-Machina @ottodevs @himanshupnt @zoek1 @vaibhavb @lookfwd @osamakhn Please try to finish your work by the end of this week.
The funding of 0.7 ETH (446.54 USD @ $637.91/ETH) attached to this issue has been approved & issued to @lookfwd.
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;
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
Requirements