Bridging Event Organizers & Attendees
We serve as the seamless connection between event organizers and attendees, creating efficient and engaging event experiences.
├── /agenda # Solution documentation & planning
├── /architecture # System architecture & design decisions
├── /basic-app # Prototype (Verification & Issuer functionality)agenda/- Detailed project documentation, requirements, and roadmapsarchitecture/- Technical diagrams, system flows, and infrastructurebasic-app/- Minimal viable prototype for core functionality validation
| Stakeholder | Problem | Pain Points | "What If" Solution | Benefits |
|---|---|---|---|---|
| Business Owner | Need to arrange event quickly | - Long card production time - Shipping delays - Manual distribution |
Digital cards issued instantly | - No physical production - No shipping wait - Real-time issuance |
| Business Owner | Card ordering process | - Bulk ordering required - Minimum order quantities - Upfront costs |
On-demand digital issuance | - Pay per card - No minimums - No inventory |
| Business Owner | Time constraints | - Lead time for physical cards - Last-minute attendees |
Instant digital delivery | - Same-day event setup - Add attendees anytime |
| User | Physical card dependency | - Forgetting cards - Loss/theft - Damage |
Mobile wallet integration | - Always available on phone - Backup in cloud |
| User | Multiple cards | - Wallet clutter - Organization difficulty |
Unified digital card app | - All cards in one place - Easy switching |
| User | Replacement delays | - Waiting for new cards - Verification hassles |
Instant digital reissuance | - Self-service replacement - Immediate access |
| User | Pre-event checklist | - Manual card verification - Anxiety about forgetting |
Push notification reminders | - Automated check - Last-minute alerts |
Traditional physical card systems create logistical bottlenecks for event organizers and friction for users who struggle with card management, leading to:
- Slow onboarding for last-minute participants
- High costs and waste from unused physical cards
- Poor user experience from lost/forgotten cards
- Operational inefficiencies in card distribution
Business Owner: "What if my employee data gets leaked? I'm concerned about privacy."
Cardora: "We completely understand your concern. With Cardora, we offer two security modes to match your privacy requirements – and in both cases, we never store raw personal information."
Business Owner: "What are these two modes?"
Cardora: "We have:
Mode 1: Hash-Based Cards (Standard)
- Your employee data stays in your HR system
- We generate a cryptographic hash (digital fingerprint) of employee ID/email
- Original data is discarded immediately
- Verification happens by comparing hashes – no personal data stored
Mode 2: Self-Sovereign Cards (Premium)
- Each employee gets their own cryptographic key pair
- Cards are digitally signed by the employee's private key
- We only store the public signature – no personal data at all
- Employee controls their own card completely"
Business Owner: "Which mode should I choose?"
Cardora: "Most organizations start with Hash-Based Cards because:
- Simple setup for bulk employee onboarding
- You control the card issuance process
- Lower cost per card
Self-Sovereign Cards are better if you have:
- Employees who handle highly sensitive data
- Remote workers who need maximum privacy control
- Compliance requirements for zero data storage
You can even mix both modes within your organization – executives might use Self-Sovereign while general employees use Hash-Based."
Business Owner: "How does verification work with two different systems?"
Cardora: "That's the beauty – verifiers don't need to know which mode was used. Our scanner automatically detects the card type and applies the correct verification method. It's completely seamless."
Business Owner: "But what if someone reverse-engineers the hashes?"
Cardora: "With our advanced cryptographic approach, we go beyond basic hashing:
-
Asymmetric Key Protection
- Each card is signed using ECDSA (Elliptic Curve Digital Signature Algorithm)
- Your organization holds the private key - we never store it
-
Dual-Layer Security
# Card signing process signature = ecdsa_sign( message=card_details, private_key=org_private_key ) # Generates unique cryptographic signature
- The signed card contains:
• Public metadata (visible)
• Digital signature (verifiable)
• No stored personal data
- The signed card contains:
-
Zero-Data Verification
- Verifiers only need your organization's public key
- No central database of personal information exists to compromise"
Watch the complete demonstration of Cardora in action.
- Privacy-First: Two security modes with zero personal data storage
- Instant Issuance: Digital cards created and delivered immediately
- Mobile Integration: Native wallet support across platforms
- Seamless Verification: Automatic detection of card types
- Pay-Per-Use: No minimum orders or upfront inventory costs
- Cross-Platform: Works across different mobile wallets and devices
- Cryptography: ECDSA (Elliptic Curve Digital Signature Algorithm)
- Hashing: Advanced cryptographic hashing with salt protection
- Mobile Integration: Cardora App support
- Verification: QR code
-
Registration & Login
- As a user, I can register with my email, password, and public key (as my address).
- I can log in securely to access my digital cards.
-
Card Management
- Event Cards: Automatically appear on my screen when issued.
- Employee Cards: Must request from registered organizations.
- I can view cards in Hash or Cryptographic mode.
-
Security & Settings
- I can export my private key.
- I can log out to keep my cards secure.
- (Future) Suspend cards if my phone is stolen.
-
Dual Mode Access
- I can switch between Normal User and Verifier roles.
-
Registration & Dashboard
- I can register as a Customer or Organization.
- After login, I see a dashboard with:
- Organizations I manage
- Billing history
- Settings
-
Card Issuance & Management
- Under each organization, I see Events/Entities and issued cards.
- I can import data to generate digital cards.
- I can customize card fields (tags) before creation.
-
Preview & Approval
- After setting fields, I see a card sample.
- I can edit (adjust UI/attributes) or approve.
- On approval, I see cost estimation and pay via USDC (Crypto) or Fiat (Asian Payment/Dinger).
-
Post-Payment
- After payment, backend processes cards.
- I receive an email notification with invoice upon completion.
- Mobile User: Registration, login, card viewing, basic security.
- Admin: Organization management, card creation, payment.
- Later: Card suspension (lost phone), advanced verifier features.
This is the simple customer of our application would love to see his dashboard and issue cards
