grassrootseconomics/cic-docs
5
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update 020_redeemable_certifcate.md

Browse Source
This commit is contained in:
Will Ruddick 2021-03-09 09:06:58 +00:00
parent 0794c5262b
commit 9df1229a85
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
spec/020_redeemable_certifcate.md
View File

@ -13,6 +13,7 @@ Anyone can redeem the Cert. Say a business offered the receiver a voucher for th
* Enviromental Data: ex. Certifying that the recipent is a farmer who is mulching their land or using regnerative practices. Soil quality testing etc. * Enviromental Data: ex. Certifying that the recipent is a farmer who is mulching their land or using regnerative practices. Soil quality testing etc.
* Transactional Data: ex. Certifying that the recipent is paying for school fees. The school could be a validator. If using CIC the transaction hashes themselves could add evidence. * Transactional Data: ex. Certifying that the recipent is paying for school fees. The school could be a validator. If using CIC the transaction hashes themselves could add evidence.
# Schema
1. Issuer: <wallet address> 1. Issuer: <wallet address>
1. Issued to: <wallet address> 1. Issued to: <wallet address>
1. Acceptance: <signature of receiver> 1. Acceptance: <signature of receiver>
@ -57,9 +58,12 @@ A market place application should be able to read these certificates and support
Certificates can be aggregated and sorted by type, area, gender and so on. Certificates can be aggregated and sorted by type, area, gender and so on.
Recipients can go here to choose to delete their certs, share them with others or approve a redemption Recipients can go here to choose to delete their certs, share them with others or approve a redemption
#Risks #Risks & Questions
* Someone may potentially recieve many bogus certificates * Someone may potentially recieve many bogus certificates
* these should not be 'accepted' by the receiver and can also be Destroyed. * these should not be 'accepted' by the receiver and can also be Destroyed.
* Validators should also have certifications
* Personal Identifying Information written into the Cert is avalible to anyone that can read the Cert. * Personal Identifying Information written into the Cert is avalible to anyone that can read the Cert.
* The reciever can have the option to encrypt the data or parts of the data/details * The reciever can have the option to encrypt the data or parts of the data/details
* Zero knowlege proofs... tbt * Zero knowlege proofs... tbt