HomePlatformBlockchain Trust Layer
Phase 1Deployable Now

Blockchain Trust Layer

Make every complaint and FIR tamper-evident — without replacing CCTNS.

Overview

A tamper-evident layer over records you already keep

Every complaint or FIR is fingerprinted with a cryptographic hash and anchored to a permissioned blockchain with a timestamp. The original document stays exactly where it already lives — in CCTNS or the department database. If it's altered later, the hash no longer matches.

Workflow

How the process runs, step by step

1

Officer registers complaint or FIR in existing system

2

Gradify generates a SHA-256 hash of the record

3

Hash + timestamp anchored to permissioned blockchain

4

QR code issued for citizen-facing documents

5

Any future edit breaks the hash match — tampering is instantly visible

Capabilities

What this phase delivers

Complaint & FIR Hashing

Cryptographic fingerprint generated for every record, anchored on-chain with a timestamp. The source document never leaves your existing systems.

QR-Based Verification

Character certificates, NOCs, lost article reports and verification certificates carry a scannable QR showing document ID, issue date, issuing station and live status.

Citizen Verification Portal

A public portal where any citizen or department can enter a document number or scan a QR to confirm a record is genuine and unaltered.

Officer Dashboard

Register documents, generate hashes, and search verification history — layered on top of current workflows with no retraining required.

Immutable Audit Trail

A permanent log of every creation, verification and update event, tied to the officer and timestamp responsible for it.

Benefits

Why this phase matters

Prevents unauthorized modification of complaints and FIRs

Improves transparency and public trust in issued documents

Zero disruption to CCTNS or existing record systems

Deployable at a single station and scaled district-wide

Bring a transparent trust layer to your department

See how Gradify PoliceTrust anchors onto CCTNS and ICJS without disrupting a single existing workflow.