89 lines
2.0 KiB
Markdown
89 lines
2.0 KiB
Markdown
|
# License Issuance
|
||
|
|
|
||
|
|
## Issuance Process
|
||
|
|
|
||
|
|
When an application reaches final approval:
|
||
|
|
|
||
|
|
```
|
||
|
|
Final Approval
|
||
|
|
│
|
||
|
|
▼
|
||
|
|
┌─────────────────┐
|
||
|
|
│ System creates │
|
||
|
|
│ license record │
|
||
|
|
└────────┬────────┘
|
||
|
|
│
|
||
|
|
▼
|
||
|
|
┌─────────────────┐
|
||
|
|
│ NFT minted on │
|
||
|
|
│ blockchain │
|
||
|
|
└────────┬────────┘
|
||
|
|
│
|
||
|
|
▼
|
||
|
|
┌─────────────────┐
|
||
|
|
│ Certificate │
|
||
|
|
│ generated (PDF) │
|
||
|
|
└────────┬────────┘
|
||
|
|
│
|
||
|
|
▼
|
||
|
|
┌─────────────────┐
|
||
|
|
│ Applicant │
|
||
|
|
│ notified │
|
||
|
|
└─────────────────┘
|
||
|
|
```
|
||
|
|
|
||
|
|
## Certificate Contents
|
||
|
|
|
||
|
|
Each issued certificate includes:
|
||
|
|
|
||
|
|
| Field | Description |
|
||
|
|
|-------|-------------|
|
||
|
|
| License Number | Unique identifier (GOA/DEPT/YEAR/SERIAL) |
|
||
|
|
| Holder Name | Legal name of licensee |
|
||
|
|
| License Type | Category of license |
|
||
|
|
| Issue Date | Date of issuance |
|
||
|
|
| Valid Until | Expiration date |
|
||
|
|
| Issuing Authority | Department name and officer |
|
||
|
|
| QR Code | Verification link |
|
||
|
|
| Digital Signature | Cryptographic signature |
|
||
|
|
|
||
|
|
## Blockchain Record
|
||
|
|
|
||
|
|
The NFT token contains:
|
||
|
|
|
||
|
|
```json
|
||
|
|
{
|
||
|
|
"tokenId": "0x123...",
|
||
|
|
"licenseNumber": "GOA/TRADE/2026/00001",
|
||
|
|
"documentHash": "SHA256:abc...",
|
||
|
|
"issuedAt": 1707500000,
|
||
|
|
"issuedBy": "0xDeptAddress..."
|
||
|
|
}
|
||
|
|
```
|
||
|
|
|
||
|
|
## Verification
|
||
|
|
|
||
|
|
Anyone can verify a certificate:
|
||
|
|
|
||
|
|
1. Scan QR code on certificate
|
||
|
|
2. Or visit verification portal
|
||
|
|
3. Enter license number
|
||
|
|
4. System queries blockchain
|
||
|
|
5. Displays verification result
|
||
|
|
|
||
|
|
Verification shows:
|
||
|
|
- Valid/Invalid status
|
||
|
|
- License details
|
||
|
|
- Issuance history
|
||
|
|
- Current status (active/expired/revoked)
|
||
|
|
|
||
|
|
## Revocation
|
||
|
|
|
||
|
|
If a license must be revoked:
|
||
|
|
|
||
|
|
1. Department admin initiates revocation
|
||
|
|
2. Reason documented
|
||
|
|
3. Blockchain record updated (token burned)
|
||
|
|
4. Certificate marked as revoked
|
||
|
|
5. Holder notified
|