Right now there are “n” number of ways to create a duplicate certificate online, available at the click of your mouse on the internet. Not only does it reduce the significance of a certificate but it also becomes impossible to verify authenticity of the certificate if one is presented. The aim is to build a decentralized application which by using Smart contracts can create an immutable version of a document which can be verified by concerned parties.
Project Description*
A hash can be created from a document but a document cannot be created from a hash
We hash the certificate that is to be issued by a certain party
This company then creates an index (Merkle DAG(very secure)) of all the
hashes of the certificates that have been issued
This indexed document is then uploaded on the blockchain
The indexed document is available on the blockchain, thus confirming that the certificate was indeed issued by a legitimate party. Now, we produce a hash of the certificate to be authenticated
We search for this hash within the authenticated indexed document
If the hash is found, then the certificate is authentic.
Project Limitations
The issuer and receiver must trust the system and there should be an accepted standard of the system. The system should have an incentive then who should be incentivised and what is the incentive?
Tech Stack*
Hybrid Blockchain (XDC)
Solidity(smart contracts)
React(Front End)
Django(Back End)
IPFS( Distributed File system to store the certificates)
Hackathon Name*
SPIT Hackathon
Problem Statement*
Right now there are “n” number of ways to create a duplicate certificate online, available at the click of your mouse on the internet. Not only does it reduce the significance of a certificate but it also becomes impossible to verify authenticity of the certificate if one is presented. The aim is to build a decentralized application which by using Smart contracts can create an immutable version of a document which can be verified by concerned parties.
Project Description*
A hash can be created from a document but a document cannot be created from a hash We hash the certificate that is to be issued by a certain party This company then creates an index (Merkle DAG(very secure)) of all the hashes of the certificates that have been issued This indexed document is then uploaded on the blockchain The indexed document is available on the blockchain, thus confirming that the certificate was indeed issued by a legitimate party. Now, we produce a hash of the certificate to be authenticated We search for this hash within the authenticated indexed document If the hash is found, then the certificate is authentic.
Project Limitations
The issuer and receiver must trust the system and there should be an accepted standard of the system. The system should have an incentive then who should be incentivised and what is the incentive?
Tech Stack*
Hybrid Blockchain (XDC) Solidity(smart contracts) React(Front End) Django(Back End) IPFS( Distributed File system to store the certificates)
Team Members and Contact info*
Shreeyaa Agrawal shreeyaa98@gmail.com Github: https://github.com/shreeyaa98 Harsh Jain harshjain131098@gmail.com Github: https://github.com/harsh9500 Farhan Kasmani farhankasmani956@gmail.com Harshita Khandelwal harshitaskh@gmail.com Team code-shreeyaa98258