██████╗██████╗ ███████╗██████╗ ██╗███████╗██╗ ██╗ ██╔════╝██╔══██╗██╔════╝██╔══██╗██║██╔════╝╚██╗ ██╔╝ ██║ ██████╔╝█████╗ ██║ ██║██║█████╗ ╚████╔╝ ██║ ██╔══██╗██╔══╝ ██║ ██║██║██╔══╝ ╚██╔╝ ╚██████╗██║ ██║███████╗██████╔╝██║██║ ██║ ╚═════╝╚═╝ ╚═╝╚══════╝╚═════╝ ╚═╝╚═╝ ╚═╝
Controlled Trust · Deterministic Verification · Institutional Auditability
A permissioned blockchain infrastructure for secure academic credential issuance, verification, and tamper-evident record validation.
Overview • Architecture • Workflow • Security • Quick Start • Roadmap
Note
Credify v2 is a permissioned blockchain platform designed to solve credential forgery, verification delays, and uncontrolled academic record exposure in traditional verification systems.
Traditional verification systems still rely heavily on:
- manual verification workflows
- institution-dependent approvals
- paper-based trust
- delayed verification cycles
- centralized record handling
Credify replaces that flow with:
- deterministic blockchain anchoring
- validator-controlled trust
- finalized tamper-evident blocks
- cryptographic proof validation
- selective credential disclosure
|
|
|
|
|
|
Important
Credify prioritizes deterministic distributed behavior, institutional trust, explainability, and auditability over public-chain decentralization complexity.
flowchart LR
A[Issuer] --> B[Credential Generation]
B --> C[Digital Signature]
C --> D[IPFS Storage]
D --> E[Blockchain Anchor]
E --> F[Finalized Block]
F --> G[Student Holder]
G --> H[Verifier]
H --> I[Signature Validation]
H --> J[Anchor Integrity Validation]
H --> K[Revocation Validation]
graph TD
V1[Validator Node 1]
V2[Validator Node 2]
V3[Validator Node 3]
V1 --> V2
V2 --> V3
V3 --> V1
B[Finalized Block]
V1 --> B
V2 --> B
V3 --> B
flowchart TD
Admin -->|Creates| Student
Admin -->|Issues| Credential
Student -->|Shares| Proof
Verifier -->|Checks| Blockchain
Verifier -->|Validates| Signature
Verifier -->|Checks| Revocation
| Principle | Why It Exists |
|---|---|
| Deterministic Consensus | Removes probabilistic confirmation delays and creates predictable validator sequencing. |
| Permissioned Validators | Maintains institutional trust boundaries and prevents uncontrolled participation. |
| Finalized Blocks | Strengthens tamper evidence and reduces ambiguity in verification flows. |
| Independent Verification | Reduces operational coupling between issuance and verification systems. |
| Selective Disclosure | Allows proof validation without exposing unnecessary academic information. |
Note
Initial prototype created to validate feasibility and core verification flows quickly.
- IPFS-based credential storage
- SHA-256 / Keccak hashing
- React dashboard workflows
- Dockerized deployment
- Initial credential anchoring
Warning
The prototype exposed architectural limitations in:
- deterministic state progression
- validator trust control
- institutional audit guarantees
- finalized verification guarantees
- synchronization consistency
These limitations directly shaped the redesign into Credify v2.
- Permissioned validator architecture
- Deterministic consensus sequencing
- Finalized tamper-evident blocks
- Validator orchestration model
- Multi-node synchronization support
- Stronger verification guarantees
Tip
Verification was intentionally separated into an independent trust boundary.
- Independent verification frontend
- QR-based proof validation
- No backend dependency during verification
- Reduced operational coupling
- Public verification accessibility
Note
Credify follows institution-controlled onboarding rather than public self-registration.
|
|
|
sequenceDiagram
participant Admin
participant Storage
participant Blockchain
participant Student
participant Verifier
Admin->>Storage: Store credential payload
Admin->>Blockchain: Anchor metadata hash
Blockchain-->>Student: Credential finalized
Student->>Verifier: Share proof / QR
Verifier->>Blockchain: Validate anchor
Verifier->>Storage: Validate payload
Verifier-->>Student: Verification result
Tip
Recommended setup for validator synchronization demos and distributed-system evaluation.
docker pull udaycodespace/credify:latest
docker run -d -p 5000:5000 udaycodespace/credify:latesthttp://localhost:5000git clone https://github.com/udaycodespace/credify.git
cd credify
python -m venv venv
# Windows
venv\Scripts\activate
# Linux/macOS
source venv/bin/activate
pip install -r requirements.txt
cp .env.example .env
python main.pydocker-compose up -d| Technology | Purpose |
|---|---|
| Python 3.10+ | Runtime |
| Flask | REST backend |
| SQLAlchemy | ORM & persistence |
| RSA Cryptography | Digital signatures |
| SHA-256 | Integrity hashing |
| Technology | Purpose |
|---|---|
| Permissioned Ledger | Controlled validator trust |
| Deterministic Consensus | Predictable sequencing |
| Finalized Blocks | Tamper evidence |
| Validator Orchestration | Distributed synchronization |
| Technology | Purpose |
|---|---|
| IPFS | Decentralized storage |
| SQLite/PostgreSQL | Persistence layer |
| Local Fallback | Reliability support |
| Technology | Purpose |
|---|---|
| Docker | Containerization |
| Docker Compose | Validator orchestration |
| GitHub Actions | CI/CD automation |
credify/
│
├── app/ # Flask routes and services
├── core/ # Blockchain and cryptographic logic
├── data/ # Runtime storage artifacts
├── docs/ # Engineering documentation
├── static/ # Frontend assets
├── templates/ # HTML templates
├── tests/ # Automated tests
│
├── Dockerfile
├── docker-compose.yml
├── pyproject.toml
└── README.md
pytest -vpytest --cov=app --cov=core --cov-report=html- authentication flows
- blockchain integrity
- validator synchronization
- consensus sequencing
- propagation consistency
- signature validation
- revocation verification
Tip
Suitable for:
- academic demonstrations
- institutional pilot environments
- distributed systems showcases
- blockchain engineering portfolios
- verification workflow evaluation
SECRET_KEY=
OTP_SECRET=
DATABASE_URL=
IPFS_GATEWAY=
VALIDATOR_NODE_ID=
PEER_NODES=| Control | Purpose |
|---|---|
| OTP-based Privileged Access | Restricts administrative onboarding and issuance. |
| RSA Digital Signatures | Validates credential authenticity and integrity. |
| SHA-256 Hashing | Provides tamper-evident hashing guarantees. |
| Role-based Boundaries | Prevents unauthorized credential operations. |
| Finalized Block Model | Strengthens verification defensibility. |
Warning
Production deployments should:
- enforce HTTPS/TLS
- rotate secrets regularly
- isolate validator infrastructure
- monitor verification failures
- avoid default development secrets
- separate staging and production validators
- PBFT-style consensus evolution
- Validator governance controls
- Validator slashing mechanisms
- IPFS cluster integration
- DID interoperability
- Advanced zero-knowledge proof systems
- Distributed audit dashboards
💻 ⚡ 🔐 |
🧪 💻 📖 |
🐛 🧪 📚 |
Note
This project was developed with academic mentorship and institutional guidance from faculty members at G. Pulla Reddy Engineering College (Autonomous), Kurnool.
| Faculty | Contribution |
|---|---|
| Dr. B. Thimma Reddy Sir | Distributed systems and engineering guidance |
| Dr. G. Rajeswarappa Sir | Academic evaluation and technical mentorship |
| Shri K. Bala Chowdappa Sir | Institutional support and project guidance |
- Python ecosystem
- Flask community
- IPFS contributors
- Open-source maintainers
- Cryptography libraries ecosystem
Note
Project classification: B.Tech Final Year Engineering Project.
Maintained for:
- academic evaluation
- blockchain engineering demonstration
- distributed systems showcase
- portfolio presentation
Built as a flagship blockchain engineering project
If this project helped you, consider giving it a ⭐