# Quartech Trust Services - SaaS - Multi-tenant VC issuer, holder and verifier

## Summary
Enables entities via a web or mobile application [SaaS] to:
- `Issuers` create schema and credential def to a ledger network
- `Issuers` issue credentials with the required attributes to `Holders`
- `Holders` store the credentials in their wallet
- `Verifiers` can request proof from `Holders` and verify it
- `Issuers` can revoke issued credentials

Rely on connections or connectionless OOB???

## Problem
Facilitate easy adoption of verifiable credentials by entities in their workflow across various sectors and use cases.

## Scope

| Roadmap | In | Out |
|---|----|-----|
| Traction Backend | <ul><li>Ledger??</li><li>Tails Server??</li></ul> | |
| OrganicBC POC | | |
| Multitenant SaaS Expansion | <ul><li>Present Proof Request Templates</li><li>Present Proof Request Editor</li><li>~~API interface for 3rd party integeration~~</li></ul> | |

## Requirements

### Roadmap 0 - Traction Backend

- All Aries [ACA-Py] related capablities like `issue-credential`, `present-proof`, `revoke-credential`, `schema`, `creddef`, `connections` and `out-of-band` will be leveraged from Traction
- Each tenant will leverage the Askar wallet from Traction for storing credentials
### Roadmap 1 - OrganicBC POC
Multiple use cases applicable under this roadmap:
- **OrganicBC `Issuer` - Farm Entity `Holder` - Inspector, Distributor or Consumer `Verifier`**
`OrganicBC` will issue credential to `Farm` depicting organic farm status. `OrganicBC` can revoke already issued credentials. `Inspector, Distributor or Consumer` will request proof from `Farm` and can verify it.

All 3 actors in the above example will be 3 individual tenants in the Traction backend.


`Attributes` for organic farm:
- <u>Farm Identification</u>:
Farm Name
Unique Identifier (e.g., a farm registration number)
- <u>Location Information</u>:
Address of the farm
Geographic Coordinates (if applicable)
- <u>Certification Details</u>:
Certification Body (e.g., name of the organization that certified the farm)
Certification Number
Date of Certification
Expiry Date of Certification (if applicable)
- <u>Organic Standards Compliance</u>:
Confirmation that the farm complies with relevant standards such as CAN/CGSB 32.310, CAN/CGSB 32.311, etc.
Compliance with specific provincial requirements (e.g., BC Certified Organic Program)
- <u>Audit and Inspection Records</u>:
Dates of last inspections
Summary of inspection findings
- <u>Organic Plan</u>:
Details of the organic plan that the farm follows
Soil management practices
Pest and weed control methods used
- <u>Permitted Substances Used</u>:
List of any permitted substances used, as per CAN/CGSB 32.311
- <u>Contact Information</u>:
Contact details of the farm owner or manager
Emergency contact information
- <u>Digital Signature</u>:
An electronic signature from the certifying body for authentication
- <u>QR Code or Digital Link</u>:
For easy verification and access to the farm's certification details
- <u>Regulatory Compliance Information</u>:
Information confirming compliance with the Safe Food for Canadians Regulations
- <u>Additional Certifications</u>:
Any other relevant certifications (e.g., fair trade, local organic association memberships)
- **Farm Entity `Issuer` - Farm Produce Store `Holder` - Inspector, Distributor or Consumer `Verifier`**
`Farm` entity will issue credential to a `Farm store` entity depicting organic attributes of each product type like apple, banana, etc. `Farm` entity can revoke already issued credentials. `Inspector, Distributor or Consumer` will request proof from `Farm store` [mainly via scanning QR] and can verify it.

All 3 actors in the above example will be 3 individual tenants in the Traction backend.


`Attributes` for organic food product:
- <u>Certification Body Information</u>
Name of the certifying body or organization
Certification logo or mark
- <u>Certification Standard</u>
Specification of the organic certification standard followed (e.g., USDA Organic, EU Organic)
- <u>Product Information</u>
Name of the organic product
Product type and category
- <u>Producer/Farm Information</u>
Name and address of the certified organic producer or farm
Certification number for the producer/farm
- <u>Date of Certification</u>
The date on which the organic certification was issued
- <u>Ingredients and Raw Materials</u>
List of organic ingredients or raw materials used in the product
- <u>Organic Percentage</u>
The percentage of organic ingredients in the product
- <u>Traceability Information</u>
Batch or lot numbers to trace the product back to its origin
- <u>Compliance Statements</u>
Statements confirming compliance with specific organic standards and regulations
- <u>Expiration Date</u>
The date on which the organic certification expires
- <u>Third-Party Verification</u>
Information about any third-party inspections or audits conducted to verify compliance
- <u>QR Code or Barcode</u>
A scannable code that provides access to detailed information about the product's certification when scanned
- <u>Regulatory Compliance Information</u>
Confirmation that the product complies with local and international regulations regarding organic labeling
- <u>Storage and Handling Information</u>
Instructions for proper storage and handling to maintain the organic integrity of the product
### Roadmap 2 - Expansion to Multitenant SaaS architecture

## Solution

### Roadmap 0

### Roadmap 1

### Roadmap 2

## Acceptance Criteria

### Roadmap 0
- Setup/Selection of ledger network
- Setup/Selection of tails server
- Deployment of Traction backend

### Roadmap 1
- OrganicBC to issue organic status VC to farm
- The farm is able to store the VC
- Verfier is able to request proof from the farm and verify it successfully
- OrganicBC is able to revoke the VC issued to the farm
- Verifier is unable to receive a verified proof from the farm
### Roadmap 2