How Praman Works
Three-Layer Source-Record Architecture
The paper certificate a student holds is a COPY. The source of truth is the university's own examination registers — the physical ledgers, result sheets, and convocation records in the Controller of Examinations' office.
Praman digitizes the source, not the copy.
Bulk Record Migration
University examination registers are digitized from the source — not from student-submitted paper certificates.
Deploy Team
Trained data-entry team on campus
Capture Data
Roll no, marks, result from registers
CoE Signs
Controller of Examinations reviews & signs
Registrar Signs
Counter-signature as second authority
On-Chain
Committed as W3C Verifiable Credentials
Why Multi-Signature Matters
Two university officers must sign every batch of records. The Controller of Examinations and the Registrar act as independent authorities. One person cannot unilaterally fake records — collusion between two designated officers is required, creating a structural barrier to fraud.
Student Claim & Identity Binding
Students don't submit certificates. They claim credentials that already exist on-chain from the university's own records.
Identity Verification
Student provides their roll number, examination year, and completes Aadhaar eKYC to prove identity.
Record Matching
System matches the student’s claim against the digitized source records already committed on-chain by the university.
Credential Binding
The Verifiable Credential is bound to the student’s Decentralized Identifier (DID) and issued to their digital wallet.
Claim Fee
Student pays Rs. 150 — a one-time fee for a portable, reusable, cryptographically verifiable credential.
“The student never submits a paper certificate.
There is nothing TO fake.”
Assurance Levels
Not all source records are equally complete. Praman encodes this reality as machine-readable assurance levels that enable automated acceptance policies.
Condition
Source register exists, record found, dual-signed by CoE + Registrar
Action
Accept for direct appointment
Condition
Source register exists but has gaps (missing pages, illegible entries)
Action
Conditional appointment, pending physical verification
Condition
Source register MISSING from university archives
Action
Treated as unverified; cannot be confirmed or denied
Assurance levels are embedded in the Verifiable Credential metadata, enabling employers like BPSC to automate acceptance and escalation policies.
Trust Chain
Bihar's institutional hierarchy mapped to the European Blockchain Services Infrastructure trust model.
Root Trust Anchor — authorizes universities to issue
Trust Anchor — approves and counter-signs credential batches
Issues credentials from source examination registers
Queries the trust registry and verifies credentials via API
Claims and holds verifiable credentials in a digital wallet
Technical Foundation
Every design decision traces to a published specification.
Hyperledger Fabric 2.x
Permissioned blockchain with institutional governance
Go Chaincode
Smart contracts for credential lifecycle management
W3C VC v2.0 + JSON-LD
Interoperable, standards-compliant credential format
Five On-Chain Registries
Identity, trusted issuers, schemas, verifiers, and credential status — each maintained independently for auditability
Ready to See Praman in Action?
Whether you represent a university, a state education department, or an employer — we'd welcome the conversation.