- Three solutions:
- Sample social portal user profile page:
- certificates listed with credentials
- each certificate with possibility for verification request
- Certificates manager site
- requests manager (verify or reject requests)
- cerfiticates manager (add or remove certificate for certain user)
- Smart contracts
- one for requests
- one for certificates
- abi files with Ricardian Clauses filled in
- User flow for Jane and John:
- Jane has social account with her certificates listed
- John clicks on verification request button next to certificate A
- request is stored on the blockchain
- Jane receives request for certificate A verification on manager site
- Jane decides to verify certificate A for John
- Email is sent to John with certificate A verification credentials from the blockchain (a combined unique hash)
- next hash verifcation to be done on the server side
- User flow for University of London and Jane:
- University of London issues a cerificate B for Jane
- there is a record in blockchain table with ceritficate ID and unique certificate hash for future verification
- Jane has new certificate she can list on her social page, for other users to verify!
magdazelena / eoshackathon Goto Github PK
View Code? Open in Web Editor NEWThis project forked from irespo/eoshackathon
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent