Please describe your proposed solution.
Solution
The Cardano blockchain is a rapidly evolving ecosystem, ideal for exploring innovative and useful solutions with impact. One of the important use cases is recording a person's educational history. In a traditional learning system, universities carry out a registration and control process until the student graduates, the Universities issue a certificate that certifies completion. In the context of a decentralized digital identity, Diplomada is the system that registers, controls and issues; the students the receiving entity. Diplomada would contain a student's credentials, authenticating their relevant qualifications and demonstrating their university membership. Diplomada would complement and support the traditional processes of issuing degrees and proof of attendance in the years of study and at the end of these, ensuring that no one falsifies educational data, qualifications, diplomas and certifications.
In the blockchain it is complex to place clear text since diplomas and transcripts are personal information, however in Diplomada an NFT will be issued as a conclusion of the smart contract that will be executed as the final phase of the academic commitments obtained and registered. For example, the NFT could include information such as the graduate's name, year of graduation, and other relevant data.
Components
WEB3 PORTAL
Management interface:
- Smart contract management: will allow administrators to configure and manage the records and data of the university community
- Credential and Log Requests: Provides an interface to review and approve/reject credential requests and log uploads submitted by user
- Credential and registration revocation management: Provides an interface to review and suspend or revoke existing credentials and registrations
- NFT issuance: will facilitate the creation of credentials directly for users
- Wallet Connection: Before performing any operation that modifies the blockchain, the user must connect their wallet through a wallet connector on the fronten
User interface:
- Request for credentials and NFTs: allows users to submit requests for credentials and NFT, which will begin with the creation of a smart contract and will conclude with NFT if applicabl
- Status View Request for Credentials and NSTs: Allows users to view the status of their credential and NFT (under request, approved, claimed)
- Wallet Connection: Before performing any operation that modifies the blockchain, the user must connect their wallet through a wallet connector on the fronten
Third Party Interface:
Credential Verification Portal: for the purpose of verifying certifications by third parties, a verification of the authenticity of a user's credentials and NFTs will be created without the need to interact directly with the blockchain. These are the features it will have:
- Verification Method Selection: the user or entity wishing to verify the identity can do so through a provided web3 portal
- Wallet Connection: it may have a wallet connector functionality that allows the user to connect their walle
- Provision of necessary data: key pieces of information are needed for verification: the public key of the wallet
- Identification of contract and specific NFTs: within the collection data, finds the address of the contract and the NFT to be validated
- Credential verification: verifies the specific contract, looking for a credential and NFT associated with the provided wallet public ke
- The search will be carried out through the Synchronized Database: uses a database that is synchronized with the blockchain networ
- Verification result: Finally returns the verification result, indicating whether the credential is valid or no
- Any entity or user can perform this verification through the portal or even by their own means by exploring the network and reading the corresponding dat
API
An API will be available to allow extensive interaction with the protocol. This will allow our web3 portal to not be the only means of access to these functions. The API will allow all types of queries and facilitate action, the project API will act as a facilitator to interact with the blockchain and will not directly create or modify data in the blockchain. This is because the creation and modification of data on the blockchain requires transactions to be signed by electronic wallet signatures by interested parties.
Below is the process of using our API:
- API Request: The interface makes a request to the API to create or update data. The API prepares the necessary transaction but does not send it to the blockchain.
- Transaction reception: The frontend receives the transaction prepared by the API
- Transaction Signing: Using the wallet connector, the user signs the transaction with their private wallet
- Sending the transaction: once signed, the transaction is sent to the blockchain through the frontend.