eoscostarica / lifebank Goto Github PK

create SQL function in hasura to query locations based on a lactation and distance radius. (using PostGIS)

https://hasura.io/blog/building-a-realtime-geolocation-app-with-hasura-graphql-and-postgis/

Use the webapp-boilerplate to create a new React Web Application for frontend.

In order to keep token scarcity and keep lifebanks from staying at top urgency level at all times

• Lifebanks can have a max supply of tokens issued, so they can run out of tokens issued, however they can recover tokens from sponsors

-sponsors can send the tokens they get from doners to the lifebank with the highest blood urgency.

for example: if there is a can area with a disaster then sponsors can send their tokens to that clinic to help with relief

If a life bank has a surplus of tokens they can send tokens to another lifebank that needs it more

Keosd runs on the backend server to server as a signature provider for users

users can access their wallet passwords using a 4 digit PIN

Wallet table permission

We need two icons for displaying locations on a map.

• LifeBank (Donation Center) Icon in SVG
• Sponsor (Small Business) Icon in SVG

provide users with a way to erase all of their records (similar to revoke)

they should be able to do this prom their profiles

@xavier506 is this on the database?

https://app.zeplin.io/project/5eb9dc41a992ec751f119b88/dashboard?sid=5ec711a6c6ae1047a347256c

As an user I want to login using my account name and secret provided in the signup process

As a logged in user I should see a page after I log in with a summary of my account (including token balances) and the actions I can perform

Attributes

• accountname
• community name
• fullname
• token balance
• informed consent status
• toggle consent
• tx history?

A lifebank must be invited by another one.

(to avoid spam creation of new accounts and ram waste)

Create a project logo and icons for the app

• KEOSD wallet service
• Hasura graphQL engine
• Postgres Database

Tokens should be automatically refreshed if a user is active so that thetr session dosen't expire.

These are the community smart contract actions :

Create a community (blood bank)

A community represents one or more blood banks in a given region.

A community has :

• token symbol name
• country

A community must have at least one clinic, upon creating a community you must then register a clinic.

Clinics Verify Blood Donation (mint and transfer tokens)

Clinic Account must verify that action of donating blood was completed , once a donor donates blood he/she will receive a token

donor account type receives token from clinic account type and may ONLY transfer token to sponsor account types.

Token Flow:

Clinic -> User -> Sponsor -> Savings

A clinic has :

• clinic name
• clinic description
• clinic location
• clinic phone number
• clinic schedule
• immunity test?
• blood urgency level

The community is composed of the clinic the donors , and the small business that sponsor the community.

Note: maybe clinics can then add new clinics within the same community?

Sign Up

Users sign up on the register page.

The register page creates a blockchain account and should help handle key management, all users need to remember is a an account name and 4 digit PIN

Register as a donor (individual person)

donors must have:

• name
• accountname
• Informed Consent

Clinic will manage all personal data and no personal data is stored on blockchain.

Register as a sponsor (small business)

• sponsor name
• covid impact
• description of benefit
• sponsor website
• telephone
• type
• schedule

Inspired by the bespiral community contract
https://github.com/cambiatus/contracts/tree/master/bespiral.community

In order to prevent massive amounts of signups from non-human blood donors we should have a captcha on signup

Create the user journey diagram for a clinic.

The clinic is the community creator and the issuer of a token

A new keypaidr under the active permission can be created to be used specifically with lifebank

As a donor or sponsor I should be able to register an account in the blockchain which I can access with a PIN number

Attributes for Sponsor and donor accounts are different

Backend service generate key pairs for new account, should create account on the blockchain , store keys in wallet and wallet password and pin in the postgres database.

Create a Database table to persist location data for easy query from frontend component

Tenemos que hacer una tabla que tenga:
name
latitude
longitude
type -> ENUM(SPONSOR | LIFE_BANK)

Once the potential donor user (PDU) visits the community donation center (CDC), they will need to complete the eligibility criteria for the specific donation. This will be handled as usual in person at the CDC before a blood donation. The donation center will also be able to post pre-requisites on their profile page so the potential donor can decide if they meet the criteria before visiting.

account names are being generated from a prefix + random letters

for example donor + random string made up from a-z, 1-5

In order to save ram and avoid asking users for theirfull names why not ask them for a 5 letter handle or username

so as a user I could choose my user "name" to be bobby and then the account would be donorbobby

This gives donor users a prefix and a suffix that they choose so that name along with their secret is all they need to remember in order to log in

We could shorten it to `don` para que suene a lo tico ... `doncostarica`  🥇 

• Informed Consent Smart Contact
• Each user must accept terms of service
• Users must also have a way of revoking their consent.
• Ricardian Clauses must be included

As a Clinic I want add a note to my token transfer so I can add a reference number to relate to my system and make sure that it's related to a real donation. Thus making the process more secure.

Create the user journey diagram for a blood donor.

Unable to add a new community on the jungle testnet

show the readme file some love

If users choose to leave an email address they can then recover their accountname or password.

Users can also choose e to log in with either email or account name once an email is set

LifeBank emphasises user experience over security If a user wants to recover their own private key they can also choose to do so. And interact with the smart contracts some other way.

Email address is not stored on the blockchain , only on our internal database (users should know this)

• Code desing to email
• Generate and encripted tempSecret
• Update tempSecret
• Create actions and querrys to change password
• Validate current password and change to new password
• Coding design recovery password page
• Send and coding design email to change password when is ok
• add validations to fields

If a user signs up and dosent use their account to donate blood in a time frame (say 1 month) then the account name can be assigned a new set of private keys and new users can use that account in order to avoid spending resources on accounts that are not being used

• Technical stuff
• UX stuff
• Content stuff

Medical procedures are inherently risky users must be informed and consent to the service

Users must also have a way of revoking their consent.

Each user must accept terms of service

once a users account is created and PIN is generated the user must sign a transaction declaring informed consent to use the app.

Informed consent table must have :

• data owner - doner account name
• data viewer - clinic account name
• hash - contract hash (helps to update version of contract agreed to)
• ricardian clauses

Life banks should have a dashboard with their token balances, they should be able to set their blood demand levels etc

https://hub.docker.com/_/vault
https://www.vaultproject.io/

As I user I should be able to toggle consent from my profile page.

As a user I should also have a way of erasing all my data and recovering the RAM only if a user has donated at least once.

Users can also request for their private keys once they have donated (via email? or on screen?) and revoke consent so that lifebank no longer holds their private keys

Create the user journey diagram for a sponsor or small business who is a member of the community who will revoke the token.

Lifebanks and sponsors should provide an email address when siging up

Create a 3 min video as a deliverable for the hackathon project

Set theme colors according to design.

• Remove duplicate titles

• Add icons

• Add ABI hash so it is visible for users

• Add clear explanation of what a Ricardian contract is

• add link to contract ABI in block explorer

Users can choose to use the native eosio wallet provided by lifebank or they can optionally use the wallet of their choice

Users sign up on the register page.

The register page creates a blockchain account and should help handle key management, all users need to remember is a an account name and secret

Register as a donor (individual person)

• name
• accountname
• Informed Consent
• secret

Clinic will manage all personal data and no personal data is stored on blockchain.

Register as a sponsor (small business)

• sponsor name
• covid impact
• description of benefit
• sponsor website
• telephone
• type
• schedule

Custom actions that generate and sign transactions

HASURA -> HAPI -> EOSIO TESTNET

Sopnsor sign up fields include a location selector, when a location is selected a hasura mutation should persist the location in the database

Users sign up on the register page.

The register page creates a blockchain account and should help handle key management, all users need to remember is a an account name and secret

Register as a sponsor (small business)

• sponsor name
• secret/password
• covid impact
• description of benefit
• sponsor website
• telephone
• type
• schedule
• latitude and logitude

Write ricardian clauses for the consent2life along with lifebankcode and lifebankcoin

These contract clauses must be shown to users when they accept

https://www.npmjs.com/package/react-qr-scanner

Slider component for LifeBanks to set the Blood Demand Level

Green 1 - token is issued to each doner
Yellow 2 - tokens issued to each doner
Red 3 - tokens issued to each doner

Once a token is transfers users should see a recipt . This receipt is made up of a blockchain transaction.

This would be a great component for our eoscr-components storybook , as we can use it to display transaction results for any EOSIO TX.

Servers design for

• Webapp
• Backend
  • Hasura
  • HAPI
  • Postgres
  • KEOSD

a starting point for communities https://lifebank.io

where you can learn about the app, login or sign up as a donor or sponsor

These are the following token contract actions:

Create a new currency

When a community is create a new EOSIO Token is configured.

• max supply
• expiration

Mint new compatible tokens

• Tokes must only be issued by clinics
• Tokens can only be issued for the same user once every 3 months.

Blood Demand Level

• Green 1 token is issued to each doner
• Yellow 2 tokens issued to each doner
• Red 3 tokens issued to each doner

Max yearly supply of tokens per clinic to avoid abuse of bloood demand level.

(should be a constant somewhere in the code)

Transfer compatible tokens between users.

• clinics can only transfer to doners

• doners can only transfer to sponsors

• sponsors retain tokens as savings , savings may be useful in a future version of the app.

  ACTION transfer(eosio::name from, eosio::name to, eosio::asset quantity, std::string memo);

Optional:

Set expiry options to a given token

ACTION setexpiry(eosio::symbol currency, std::uint32_t expiration_period, eosio::asset renovation_amount);

Inspired by the Cambiatus token contract: https://github.com/cambiatus/contracts/tree/master/bespiral.token