Merge branch 'willruddick-master-patch-84791' into 'master'
Update 020_redeemable_certifcate.md See merge request grassrootseconomics/cic-docs!48
This commit is contained in:
commit
69a7091419
@ -44,7 +44,7 @@ Anyone can redeem the Cert. Say a business offered the receiver a voucher for th
|
||||
1. Currency
|
||||
1. Value
|
||||
|
||||
#Contract Functions:
|
||||
# Contract Functions:
|
||||
* Issue: Anyone can issue a Cert (this specifies all the informaion and the recipient) - note there is no transfer function. Once issued to the reciever they can no longer send it to anyone else.
|
||||
* AcceptCert: The receiver can choose to accept the Certificate
|
||||
* Destroy: The receiver can delete – remove data and send to 0x000
|
||||
@ -52,13 +52,13 @@ Anyone can redeem the Cert. Say a business offered the receiver a voucher for th
|
||||
* Redeem: Anyone can redeem the cert
|
||||
* AcceptRedemption: The receiver can accept a redemption.
|
||||
|
||||
#Marketplace:
|
||||
# Marketplace:
|
||||
|
||||
A market place application should be able to read these certificates and support redemption.
|
||||
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 & Questions
|
||||
# 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
|
||||
|
Loading…
Reference in New Issue
Block a user