Project Title
Digital Student ID Using Soulbound Tokens —
Team
- E/23/054, M.V.R. Dayananda, email
Table of Contents
Introduction
Background
In modern universities, student identity management is handled using centralized systems such as ID cards and databases. These systems are vulnerable to identity forgery, data breaches, lack of interoperability, and difficulty in verification across institutions.
Problem Statement
Traditional identity systems:
- Can be duplicated or forged
- Require manual verification
- Are controlled by a single authority (centralized risk)
- Do not provide ownership of identity to students
Proposed Solution
This project proposes a blockchain-based digital identity system using Soulbound Tokens (SBTs):
- Each student is assigned a non-transferable token (NFT)
- Token contains verified academic identity data
- Stored securely on blockchain
- Cannot be sold or transferred
Impact
- Improved security and trust
- Instant identity verification
- Useful for academic and professional use
- Scalable beyond universities (jobs, certifications)
Solution Architecture
2.1 High-Level Overview
The system consists of three main layers:
- Frontend Layer
- User interface for students and admins
- Handles registration and identity viewing
- Backend Layer
- Handles APIs and business logic
- Connects frontend with blockchain
- Blockchain Layer
- Stores Soulbound Tokens
- Executes smart contracts
2.2 Core Components
Frontend
- Student Dashboard
- Admin Panel
- Wallet Integration (e.g., MetaMask)
Backend APIs
- Token Issuance API
- Token Revocation API
- Token Verification API
- Token Information API
Blockchain Module
- Mint Token Function
- Revoke Token Function
- Verify Token Function
- Ownership Check
- Transfer Restriction (SBT property)
2.3 Data Flow
- Student registers in the system
- Admin verifies student details
- Token is minted for the student
- Token is stored on blockchain
- Identity can be verified using the token
Software Designs
3.1 System Design
The system follows a layered architecture:
- Presentation Layer (Frontend)
- Application Layer (Backend)
- Data Layer (Blockchain)
3.2 Data Structure Design
Each Soulbound Token includes:
- Name
- Registration Number
- Faculty
- Department
- Batch
- Mobile Number
3.3 Smart Contract Design
Functions
mintToken(address, studentData)revokeToken(tokenId)verifyToken(tokenId)getTokenInfo(tokenId)
Rules
- One student = One token
- Tokens are non-transferable
3.4 API Design
| API Endpoint | Description |
|---|---|
| POST /mint | Issue a new token |
| POST /revoke | Revoke an existing token |
| GET /verify | Verify token validity |
| GET /info | Retrieve token data |
3.5 UI/UX Design
- Simple and user-friendly interface
- Student dashboard displaying identity
- Admin panel for verification
- QR-based identity verification system
3.6 Security Design
- Blockchain ensures immutability
- Admin-only access for token issuance
- Encryption for sensitive data
- Non-transferable token enforcement
Testing
4.1 Testing Types
- Unit Testing (Smart contracts and APIs)
- Integration Testing (Frontend ↔ Backend ↔ Blockchain)
- User Acceptance Testing
4.2 Test Cases
| Test Case | Expected Result |
|---|---|
| Mint token | Token created successfully |
| Duplicate student | Request rejected |
| Verify token | Valid identity returned |
| Revoke token | Token marked invalid |
4.3 Results Summary
- Token issuance successful
- Verification accurate and fast
- Non-transferability enforced
- Minor UI improvements identified
Conclusion
5.1 Achievements
- Developed a decentralized identity system
- Implemented Soulbound Token concept successfully
- Enabled secure and efficient identity verification
5.2 Future Developments
- Multi-university integration
- Mobile application support
- Biometric authentication
- Cross-platform verification systems
5.3 Commercialization Plans
- Applicable in:
- Universities
- Government ID systems
- Recruitment platforms
- Potential SaaS model:
- Identity-as-a-Service (IDaaS)