CredChain
Issuer-Controlled Stackable Workforce Credentials
Executive Summary
CredChain is an issuer-controlled, stackable workforce credential platform designed for large employers and training networks. Employees earn non-transferable, blockchain-backed micro-credentials (sa Large, high-growth market with strong regulatory tailwinds.
Token Data Schema
What this token holds — every field is specific to CredChain:
{
"immutable": {
"token_id": "unique identifier",
"entity_id": "primary actor",
"created_date": "ISO 8601",
"category": "concept-specific",
"version": "schema version"
},
"mutable": {
"status": "state in lifecycle",
"metadata": "custom fields",
"participant_roles": ["role1", "role2"],
"event_log": ["event1", "event2"]
},
"compliance": {
"audit_trail": "immutable transaction log",
"regulatory_status": "Compliant|Pending|Flagged",
"verification_hash": "SHA-256 proof"
}
}User Journey
Issues micro-credential upon course completion with skill tags, assessment score, and expiry date
Token: credential_token created, skill_tags[] set, expiry_date defined
Accepts credential into professional profile; stacks with existing certifications for role qualification
Token: state → Verified, employee_did bound, stack_count incremented
Queries employee credential stack against role requirements; validates all certs are current and relevant
Token: qualification_check = Met, all_credentials_current = true, role_match_score computed
Verifies issuer accreditation, assessment integrity, and continuing education compliance
Token: audit_status = Valid, issuer_accredited = true, ce_hours verified
Detects approaching expiry; notifies employee and employer; triggers recertification workflow
Token: state → Renewal_Required, notification_sent, recert_deadline set
Token Lifecycle
State machine transitions:
Why Not Just a Database?
| Approach | Portability | Mutable State | Cross-Org | Compliance |
|---|---|---|---|---|
| Traditional Database | Locked in vendor platform | Fully mutable; no immutable audit trail | Single-org only | Manual reconciliation |
| Blockchain (Public) | Fully transparent and portable | Immutable; cannot fix errors | Open access; privacy concerns | On-chain but lacks regulatory integration |
| SaaS Platform | Vendor lock-in; limited export | Mutable state; weak audit | Multi-tenant but hub-controlled | Proprietary format; limited interop |
| DUAL Token | Owner-controlled; portable across ecosystems | Mutable terms + immutable settlement trail | Multi-party settlement with zero-trust | Standards-based; regulatory-ready integration |
Market Opportunity
Issuer-controlled stackable workforce credentials for one employer. Employees earn micro-credentials as non-transferable tokens. Employer controls terms, revocation, and stackability. Logic Layer enforces prerequisite trees.
Business Model & Unit Economics
- SaaS Subscription: Monthly platform fee based on usage tier
- Transaction Fee: Per-transaction commission on platform flow
- Premium Support: White-glove integration and support services
$0.50-$2.00 per transaction | Gross margin: 65-75% | CAC payback: 8-12 months
5-Year Projections
| Year | ARR | Customers | Notes |
|---|---|---|---|
| Y1 | $150K | 2-3 | MVP launch, pilot customers |
| Y2 | $2M | 8-10 | 40% growth, expand to 2-3 regions |
| Y3 | $10M | 25+ | Series A scaling, feature expansion |
| Y4 | $25M | 60+ | Market expansion, strategic partnerships |
| Y5 | $50M | 120+ | Market leader, IPO readiness |
Competitive Positioning
| Competitor | Weakness | DUAL Advantage |
|---|---|---|
| Traditional Database | Single-vendor lock-in; no portability | Owner-controlled tokens; portable across ecosystems |
| Blockchain (Public) | No privacy controls; too transparent for business logic | Permissioned transparency + mutable business state |
| SaaS Platform | Vendor dependency; limited interoperability | Standards-based; integrates with any system |
Go-to-Market
Build core platform; secure 1-2 pilot customers; validate product-market fit.
Expand customer base; build strategic partnerships; establish industry credibility.
Dominate target market; pursue acquisition opportunities; expand to adjacent markets.
90-Day MVP
- Core token creation and state management interface
- Multi-party access control and role-based permissions
- Immutable event logging and audit trail
- Settlement calculation and distribution engine
- External API for third-party integrations
- Dashboard for monitoring and analytics
Risk Factors
Regulations continue to evolve; new compliance requirements may emerge requiring platform updates.
Mitigation: Build modular compliance framework; engage industry advisors; maintain active legal relationships
Customers may be slow to adopt new tools or prefer legacy workflows.
Mitigation: Land-and-expand strategy; offer training and onboarding; demonstrate ROI through time savings
Reliance on third-party services for payment processing or data exchange; service disruptions impact flow.
Mitigation: Dual provider integration; fallback manual settlement procedures; redundant infrastructure
Larger fintech/industry platforms could enter market with superior brand recognition and resources.
Mitigation: Build stickiness through compliance integrations; establish strategic partnerships; network effects
VC Pack Documents
Complete pre-seed investment package:
Get Started with AI
Prerequisites: Complete the DUAL Quick Start Guide to set up your environment and API keys before building this concept.
# CredChain Token Deep-Dive You are building the token system for CredChain on DUAL Network. ## Context - **Concept**: CredChain - **Alias**: Issuer-Controlled Stackable Workforce Credentials - **Category**: Refined Concept - **Viability**: 9.7/10 ## Your Task 1. Review the investment memo and financial model 2. Design the immutable→mutable→compliance token schema 3. Map the user journey (6 steps with NAMED actors) 4. For each step, list which token fields mutate 5. Identify the 4 database comparison trade-offs 6. Define state machine with business event triggers ## Output Return complete JSON with all sections filled from memo data: - token_schema (15+ fields, domain-specific) - journey_steps (with real actor names) - db_comparison (4 rows comparing approaches) - competitors (3-4 with weaknesses) - projections (Y1-Y5 ARR and customer count) - risks (3-4 with category, detail, mitigation) ## Key Principles - Token = mutable business logic + immutable compliance trail - Every field must serve a purpose (no generic metadata) - Multi-party transparency without breaking privacy - Standards-based, portable across platforms Start here.