CertVerify 💯

Blockchain-Inspired Certificate Verification Platform

"Detect Certificate, Medical Records, Research Papers Tampering Using SHA-256 Cryptographic Hashing & Immutable Blockchain Verification Records"

---

🤔 The Problem

i. In today's digital world, certificates are frequently shared as PDF documents.

ii. Unfortunately, digital documents can be:

• Modified after issuance

• Duplicated without authorization

• Forged and distributed as genuine certificates

• Difficult to verify manually

iii. As a result, employers, universities, and organizations often struggle to determine whether a certificate is authentic or has been tampered with.

iv. Even changing a single character, image, or date inside a PDF creates a completely different digital fingerprint, making traditional verification methods unreliable.

v. Without a secure verification mechanism, trust in digital certificates becomes a serious challenge.

---

💡 The Solution

I. CertVerify addresses this problem by combining cryptographic hashing with a blockchain-inspired verification ledger.

II. Instead of trusting the document itself, the system verifies the document's unique cryptographic fingerprint.

III. How It Works

1. Every uploaded certificate generates a unique SHA-256 hash.

2. The generated hash acts as the certificate's digital fingerprint.

3. A blockchain-inspired record is created and linked to previous records.

4. Certificate metadata and verification information are securely stored.

5. During verification, a new SHA-256 hash is generated from the uploaded file.

6. The newly generated hash is compared with the original stored hash.

IV. Verification Result

✔ Authentic Certificate

"The generated hash matches the stored hash."

This confirms that:

• The certificate is original.

• No modifications have been made.

• The document integrity remains intact.

❌ Tampered Certificate

"The generated hash does not match the stored hash."

This indicates that:

• The certificate has been modified.

• The document is no longer identical to the original version.

• The integrity of the certificate has been compromised.

---

Key Objectives 🎯

• Detect certificate tampering instantly.

• Eliminate manual verification processes.

• Ensure document integrity using SHA-256 hashing.

• Maintain immutable verification records.

• Provide fast and secure certificate validation.

• Demonstrate practical blockchain-inspired verification concepts.

• Deliver a cloud-hosted verification platform accessible from anywhere.

---

1. Data Registration Workflow.

flowchart TD

A[User Uploads Certificate]
--> B[React Frontend]

B --> C[Spring Boot Upload API]

C --> D[Read File Contents]

D --> E[Generate SHA-256 Fingerprint]

E --> F[Create Blockchain Record]

F --> G[Store Certificate Metadata]

G --> H[(PostgreSQL Database)]

H --> I[Certificate Successfully Registered]

Loading

---

2. Data Verification Workflow.

flowchart TD

A[User Uploads Certificate For Verification]
--> B[React Frontend]

B --> C[Spring Boot Verification API]

C --> D[Generate SHA-256 Fingerprint]

D --> E[Retrieve Stored Fingerprint]

E --> F{Hashes Match?}

F -->|Yes| G[Certificate Is Authentic]

F -->|No| H[Certificate Has Been Modified]

Loading

---

3. Production Architecture.

flowchart LR

User[User Browser]

subgraph Frontend
Vercel[React + Vite<br/>Hosted on Vercel]
end

subgraph AWS_Experience
EC2[AWS EC2<br/>Spring Boot]
RDS[(AWS RDS PostgreSQL)]
EC2 --> RDS
end

subgraph Public_Demo
RenderAPI[Spring Boot API<br/>Render]
RenderDB[(PostgreSQL<br/>Render)]
RenderAPI --> RenderDB
end

User --> Vercel

Vercel -. AWS Deployment Journey .-> EC2

Vercel --> RenderAPI

Loading

---

Application Walkthrough

1. Home Interface

The landing page introduces the platform and provides access to certificate registration, verification, and blockchain records.

---

2. Admin Authentication

To prevent unauthorized certificate registration, the upload portal is protected by an admin authentication layer.

---

3. Data Registration

Administrators can upload certificates by providing:

• Certificate File
• Owner Name
• Email Address

During registration:

• SHA-256 fingerprint is generated
• Blockchain record is created
• Certificate metadata is stored
• Verification data is persisted

---

4. Data Verification

Users can upload an existing certificate to verify its authenticity.

The system:

1. Generates a new SHA-256 fingerprint
2. Retrieves the original stored fingerprint
3. Compares both values
4. Returns the verification result

---

Blockchain Ledger

Every uploaded certificate generates a blockchain-inspired record.

Each block contains:

• Block Index
• Certificate Hash
• Previous Hash
• Timestamp
• Current Hash

This creates a tamper-evident verification chain.

---

Conclusion

In a world where digital documents can be easily copied, edited, and forged, trust becomes a challenge.

CertVerify addresses this challenge by providing a secure verification mechanism based on cryptographic hashing and blockchain-inspired integrity checks. A single modification to a document is enough to trigger detection, ensuring that authenticity can be verified with confidence.

This project reflects the complete software development journey—from problem identification and system design to cloud deployment and production readiness—demonstrating how technology can be used to build trust in digital information.