Description: Field of the Invention
The present invention is relating to a system and method for create and validate the educational certification in a secure manner using blockchain technology.
Objective of the Invention
The invention's major goal is to help the Government and private companies to verify the educational certification using a decentralized networking principle. In the recent years, some of them facing the issues like lose or damage of their important educational certifications. In order to solve this, we are introducing a blockchain based certificate creation and verification mechanisms.
Background of the Invention
In recent years, every Government/private firm facing the issue of verifying the educational/certification course certificate. First, type of technique has been introduced in (WO2020/186788A1), the present invention is for a blockchain-based certificate validation and gadget, as well as a memory device and also an electrical gadget, in which the methodology comprises acquiring a confirmation solicitation of an end credential, the validation demand trying to carry personal details with one or more destination node certs. Another method, (KR2019/102218188B1), when any one of a plurality of node devices, each of which stores block generates a hard copy along with a certificates in storage, receives a certificate distribution demand, the nodes module generates a certificates and subsequently the process is completed. In (CN2018/108540447B), this innovation is in the field of IT computer security, and it specifically refers to a block chain-based certificate validation and method. Based on a block chain trust structure, the approach can establish that a block is valid only if a particular proportion of individuals (nodes) on the block chain authorize it, ensuring that perhaps the trusted channel of a certification authentication scheme is completed and it has more public confidence. In (KR2018/102209987B1), An equipment and methodology for administering a certification status using a blockchain and a smart contract are described. According to one aspect of the present invention, a certificate registration request including a user certificate produced in an access point is received, a user certificate addresses is created utilising user cert, and a user cert is produced utilising user cert.
The (Priya et al [2019], International Journal of Advanced Networking and Applications, pp-1-4), emphasizes on E-certificates generated on the app and let the users verify them anywhere. The limitation to this approach is that old physical documents cannot be secured, as the data inputs are only used to automatically generate an e-certificate. This method was implemented with the help of an Ethereum private simulated blockchain, and Solidity smart contracts.
The (Lamkoti et al [2021], International Journal of Engineering Research & Technology (IJERT), Vol.10, Issue.3, pp-639-544), also focuses on students and organizations to register on the portal to verify and access certificates on the blockchain. This has been achieved by using the technologies, IPFS, Ganache to simulate a private blockchain network. Pitfall here is the usage of a private blockchain which can be manipulated.

Summary of the Invention
The proposed invention will be helpful for the all the Government as well as private company peoples to validate the employee certificate using the blockchain technology. First, the University has to generate the students certificate using blockchain technology. With the hash code only, we can able to validate the certificates from anywhere.
Brief description of Drawing
In the figure which are illustrate exemplary embodiments of the invention.
Figure 1, Process of Creation of an NFT Certificate
Figure 2, Process of Verification of an NFT Certificate
Detailed Description of the Invention
The proposed invention consists of two step processes like creation of an NFT certificate and verification of NFT certificate.
This module involves the logic and programming code that fulfils the task of creating an NFT certificate, on the blockchain, as a form of a transaction to the receiver’s blockchain address (also referred to as the receiver’s wallet). The workflow requires the Certifying Authority to be in possession of the digital form of the certificate being made into an NFT. These forms generally include files with extensions, like, .jpg, .jpeg, or .pdf, .png, etc. When a digital file of the certificate is being used to create an NFT, since, there is no physical or hard-paper file, there can only be one legitimate file. But, when a hard-paper (hard-copy) file or document is being used to create an NFT, then only a single digital instance(scan) of the original hard copied file will be considered as original on the blockchain network. Any other scans, or photographs of the hard copied document, xerox or photocopies would not account as an original or legitimate file.
There are some elements in this architecture, that play a vital role in the creation of NFT certificates with our application. The elements listed in the order of their appearance are as follows: Certifying Authority, Digital Certificate (File being made into NFT), Location of the file on the public domain, BlockCertify Application, Smart Contract, Ethereum Node (in the Ethereum Blockchain Network), End User (Student or person being certified). It is to be fundamentally understood that for anyone to make a transaction on the Ethereum Blockchain network, they must be in possession of sufficient Ether (ETH) currency to pay as a gas fee on the Ethereum network. Since BlockCertify is also based on the Ethereum Blockchain, the certifying authority needs to have sufficient Ether in their Blockchain Account (also called as wallet). We have tested our application with the MetaMask wallet, and for best results, it is highly recommended that the Certifying Authority and the End User have their accounts (wallets) set-up on MetaMask. Also, for the Certifying Authority to be able to validate requests of certificate verification, it is mandatory for the Certifying Authority to use only a limited Ethereum accounts (wallets) whose public addresses are publicly disclosed and advertised for on their domains and publications, solely for the purpose of verification. These addresses will act as an identifier to distinguish the real and legitimate Certifying Authority from an illegitimate or a fake one.
The workflow mainly involves the following steps, starting from the Certifying Authority creating a digital certificate in the form of a file with .jpeg, .jpg, ,pdf, or a .png file extension. This file will be referred to as NFT Certificate File. This particular file is hosted on public domain with a permanent URL, that does not change with time, as the certificate can be verified only by this means. For NFTs, generally IPFS file system is used to generate permanent file links, to files stored on a distributed network, but, any other stable and public file location on the internet can be used. (Ex: University file hosting on its own servers with a static IP or domain name). This location will be the location of the file on the public domain. When the certifying authority enters the Create certificate module on the BlockCertify application, they are supposed to be accessing it from a browser where their MetaMask wallet has been linked to, or from a MetaMask mobile applications’ inbuilt browser for linking the MetaMask wallet. The BlockCertify Application takes the user’s inputs namely the NFT file and the recepient’s (student’s) wallet address and invokes the smart contract which has already been deployed to create BlockCertify NFTs. This smart contract interacts with the Ethereum Blockchain, which inturn makes a transaction with the Ethereum Virtual Machine (which is the brain of the Ethereum Blockchain Network). When the transaction response arrives back to the BlockCertify application, if the transaction completes successfully, BlockCertify application displays the transaction data, like the Transaction Hash (also called Transaction ID) to the Certifying Authority which can be forwarded to the student /recipient for verification.
The verification module encompasses the frame works and functions that fulfil the task of verifying an already created NFT Certificate (created only using BlockCertify App) on the blockchain. This module enables any third party, or a verifier, or an employer to verify certificates on the blockchain, by providing the transaction hash (also sometimes referred as Transaction ID) primarily, and the file to be verified, or its file hash value. The elements in the order of their appearance in this architecture are as follows: End User (Verifier or 3rd party or Employer), Transaction Hash, NFT File, NFT File Hash value, Ethereum Node (in the Ethereum Blockchain Network), Certificate File at the publicly hosted location, BlockCertify Application, Certifying Authority and its public wallet address.
This module’s workflow mainly involves verifying data from the user’s inputs and comparing it with that from the blockchain data, to report any changes or to report any fraud. Since, transactions and data on the blockchain is permanent and immutable, this feature is very much in safeguarding the data from hacking or modification. For the BlockCertify application to be able to get the data from the Ethereum Blockchain, it needs to be connected to a node on the Ethereum Blockchain. This has been achieved by the virtue of a connection to a node on the Ethereum blockchain via an API key obtained with Infura. Infura is a blockchain node infrastructure service that allows apps and developers to get data from, and broadcast transactions to, the Ethereum blockchain. Infura's network is utilized as a backend for Ethereum services and applications, including MetaMask and many others. This API key can be used to make JsonRpcConnection to the node, and get results and read the data of blocks that node holds. This data can be used to verify transactions ID, obtain NFT metadata, and verify certificate generator address.
Upon entering this module, the user is presented with three choices to verify the certificate, with one being using the transaction ID (transaction hash), another being transaction hash along with the NFT File’s SHA 256 Hash, and the last method being transaction hash along with the NFT file upload. The module has algorithms and logic in place that can detect any minor change to the files, like editing even a single bit of data. This can be ensured by the means of comparison of the SHA-256 hash of the file stored at the metadata location, and the user-supplied file. If the SHA-256 hash values of both files match, then the file is said to be original. If the hashes do not match, it means that the user holds a hash/file that has been obtained as a result of modification/tampering of the original NFT file. The user can also find out that the transaction has been initiated from which particular Ethereum address (wallet address) and verify it with the Certifying Authority’s wallet address and the application gives user the response whether it was generated by that particular Certifying Authority or not. Hence, this also removes the risk of any third party or person fraudulently impersonating or pretending to be the Certifying Authority and generate NFT certificates.
5 Claims & 2 Figures , Claims: The scope of the invention is defined by the following claims:

Claim:
1. A system/method to create and validate the Educational Certificates using blockchain technology, said system/method comprising the steps of:
a) The system starts certifying authorities (1), from that all the digital certificates (2) are hosted on the public domain (3).
b) Then proposed invention is incorporated with smart contract (4) algorithms, to create a blockchain nodes (5), the entire node information is stored on our invention, then finally the certified is received by the student/end user (7).
c) In the verification end, individual certificates transaction and hash will generate (8), and given to the nodes in the blockchain network (9), after that the transaction and hashed values are sent back to our invention (10). Then, that’s assigned to public domain (11) and its public address (12).
d) Finally, the university/certificate authorities (13) verify the public address of certificates with our invention/BlockCertify (14).
2. As mentioned in claim 1, the invented system starts with university/certificate authorities to store/manage all the student’s certifications that will hosted on the public domain.
3. According to claim 1, the certificates are given to smart contracts from the public domain to generate the unique hash values and store it on the blockchain network.
4. According to claim 1, the end user can able to view the created certificates. Now the verification is reverse manner, the generated hash values are verified/validated with the transaction and NFT certificate hash values.
5. According to claim 1, the certified authorities/ any private organization able to verify it with the generated public wallet address.