From 9df1229a85d102f7bd2a546333e8014348d996cc Mon Sep 17 00:00:00 2001 From: Will Ruddick Date: Tue, 9 Mar 2021 09:06:58 +0000 Subject: [PATCH] Update 020_redeemable_certifcate.md --- spec/020_redeemable_certifcate.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/spec/020_redeemable_certifcate.md b/spec/020_redeemable_certifcate.md index 13469aa..d4e7764 100644 --- a/spec/020_redeemable_certifcate.md +++ b/spec/020_redeemable_certifcate.md @@ -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. * 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: 1. Issued to: 1. Acceptance: @@ -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. 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 * 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. * The reciever can have the option to encrypt the data or parts of the data/details * Zero knowlege proofs... tbt + +