Sunbird RC (Registry & Credential)
  • Learn
    • Introduction
    • Sunbird RC Overview
      • Why do we need Sunbird RC?
      • Core Capabilities
      • Core Registry Verbs
      • Workflows
      • What Sunbird RC is and what it's not? (WIP)
      • Possibilities
      • Demo Links
    • Technical Overview
      • High level architecture
      • Technical Specification Draft
      • Tech Stack and Requirements
    • Adopters
    • Roadmap
  • Use
    • Getting started
      • Pre-requisites
      • Installation Guide
        • Registry CLI
          • Setup A Registry Instance
        • Manual installation through docker-compose
        • Production setup through Helm
    • Developer's Guide
      • Configurations
        • Frontend Configurations
        • Frontend - Proxy configuration
        • Audit Configuration
        • Notifications Configuration
        • View Templates Configuration
      • Schema Setup
        • Introduction To Schemas
        • Creating Your Own Schemas
        • Schema Configuration
        • Create Schemas With Custom Password
      • Setup the Backend
      • Setup the Frontend
      • Backup and Restore
        • PostgreSQL
          • SQL Dump
          • File System Level Backup
          • Continuous Archiving and Point-in-Time Recovery (PITR)
        • Cassandra
          • Snapshot-based backup method
          • Incremental backup method
          • Data Restore
      • Generic Identity And Access Management
      • Metrics
      • Custom Keycloak Build
      • Custom QR Code design
      • VC Verification Module
    • Integrations
      • SSO with existing systems
      • Digilocker Meripehchaan SSO
      • Digilocker Integration
    • Release Notes
      • Latest Release - v1.0.0
    • Admin Portal
      • Login
      • Get Started
        • Create Schema
        • Attestation Workflows (WIP)
        • VC Template
          • Custom VC Template (WIP)
        • Ownership (WIP)
        • Publish (WIP)
      • Dashboard
  • API Reference
    • Registry
      • Using The APIs
      • Create An Entity
      • Invite An Entity
      • Generate token
      • Generate admin token
      • Get An Entity
      • Get An Entity By Id
      • Update An Entity
      • Create A Property Of An Entity
      • Update A Property Of An Entity
      • Revoke a Credential
      • Delete An Entity
    • Schema
      • Create Schema
      • Get Schema
      • Update Schema
      • Delete Schema
      • Publish A Schema
    • Attestation API
      • Raise An Attestation
      • Get Attestation Certificate
    • Claims API
      • Get All Claims
      • Get Claim by ID
      • Attest A Claim
    • Discovery API
      • Search An Entity
    • File Storage API
      • Upload A File
      • Get Uploaded File
      • Delete A File/ Multiple Files
    • Bulk Issuance API
      • Get Sample Template
      • Upload CSV
      • Get all uploaded Files
      • Download a Report File
    • Metrics APIs
      • Get Count
      • Get Aggregates
    • Other APIs
      • Sign API
      • Verify API
      • Swagger JSON API
      • Health API
  • Reference Solutions for Functional Registries
    • Education
      • Education Ecosystem
        • Installation
      • Education Registries
        • Installation
    • Health Registries
      • Organ Registries
        • Frontend Setup
        • Backend Setup
        • User Guide
      • Health Facility Registry
    • Govt to Person (G2P)
  • Reference Solution for Digital Credentials
    • Certificate Issuance
      • Installation(WIP)
      • User Guide
    • Vaccination Platform
    • Unified Learners Passport (ULP)
      • ULP Capabilities
      • Example Scenario
      • Technical Components (WIP)
      • Demo/Sandbox Links (WIP)
      • Installation Guide (WIP)
        • Frontend Setup
        • Installation through docker-compose
        • Dummy records setup for refrence
    • eLocker
      • High Level Diagram
      • Installation (WIP)
        • Frontend Setup E-locker
      • User Guide
    • Skills & Work Credentials
  • Links
    • Source Code
    • Releases & Changelogs
    • Website
    • Roadmap
    • Reference links
    • Design
  • Community
    • Discussion Forum
    • Contributors
    • Contributing
    • Contribution Guidebook
    • Code of Conduct
    • Community Events
    • Status By Track
  • HELP
    • Roadmap
    • FAQs
    • Glossary
    • Guide to Electronic Registries and Verifiable Credentials
      • Verifiable Credentials
        • What issues will Verifiable Credentials address?
        • What are the key roles in Verifiable Credentials?
        • What are the components of Verifiable Credentials?
        • What are the benefits of Verifiable Credentials?
        • Digital Credentials vs Verifiable Credentials
        • QR code vs Verifiable QR code
        • Use Cases
      • Electronic Registries
        • Evolution of Electronic Registries
        • What issues will Electronic Registries address?
        • Benefits of Electronic Registries
        • Registry vs Database
        • Design Principles
        • Use Cases
      • Leveraging Existing data stores
    • External Open Source Software Attributions
Powered by GitBook
On this page
  • Let's first understand What is a QR code?
  • Normal QR code vs Verifiable QR code

Was this helpful?

Edit on GitHub
  1. HELP
  2. Guide to Electronic Registries and Verifiable Credentials
  3. Verifiable Credentials

QR code vs Verifiable QR code

Let's first understand What is a QR code?

A QR code, short for Quick Response code, is a two-dimensional barcode that can be scanned by a QR code reader or smartphone camera to retrieve information.

QR codes can contain various types of data, such as website URLs, text, email addresses, phone numbers, and more.

QR codes are widely used in marketing, advertising, and other industries as a way to quickly provide information to customers or users. They are also used for contactless payment systems, where customers can scan a QR code to make a payment without physically swiping or inserting a credit or debit card.

QR codes are easy to create and can be printed on a paper, plastic, and metal. They can also be displayed on electronic screens, such as smartphones, tablets, and computer monitors.

Normal QR code vs Verifiable QR code

Normal QR Code
Verifiable QR code

A normal QR Code is a two-dimensional barcode that contains information that can be read using a QR code scanner or a smartphone camera. This information is usually a website URL.

A signed QR code encodes the verifiable data set or information within the QR itself, rather than on any website.

QR codes are susceptible to tampering and alteration, making the verification process untrustworthy and vulnerable to hacking.

Verifiable QR codes use digital signatures to ensure the authenticity and integrity of the data/information contained within them. When a verifiable QR code is scanned, the digital signature is verified to ensure that the data/information has not been altered or tampered with. This makes them more secure and trustworthy than normal QR code.

QR codes are a quick and convenient way to share information such as website details, contact details etc.

Verifiable QR codes are used when the security and integrity of the data are of utmost importance. They are typically used for sensitive data, such as personal identification details, financial information, and medical records.

Normal QR codes can be read by most QR code scanners or smartphone cameras, ensuring broad compatibility across different devices and platforms

Verifiable QR codes can still be read by most QR code scanners or smartphone cameras, maintaining compatibility across different devices and platforms. However, the verification process may require specific software or systems capable of validating the digital signatures.

Normal QR codes may contain digital credentials, which are digital representations of qualifications, achievements, or evidence of learning or experience. These credentials can be embedded within the QR code to provide information about the individual's skills, knowledge, or accomplishments. However, it's important to note that digital credentials in normal QR codes lack the built-in mechanisms for verification and cryptographic proof found in verifiable QR codes. As a result, the authenticity and integrity of the digital credentials within normal QR codes may be more difficult to ascertain compared to verifiable QR codes.

Verifiable QR codes contain verifiable credentials, which are digital representations of qualifications, achievements, or evidence of learning or experience. These credentials are securely embedded within the QR code and include cryptographic proof of their authenticity. Verifiable credentials are issued by trusted entities and can be easily shared and verified across different platforms and systems. The presence of verifiable credentials in verifiable QR codes enhances their trustworthiness and ensures that the information contained within them can be reliably

PreviousDigital Credentials vs Verifiable CredentialsNextUse Cases

Last updated 1 year ago

Was this helpful?