The problem Trustified solves

The current certification industry is fragmented, insecure, and lacks durability or long-term accessibility.

• Fragmentation: Certificates and credentials are issued by numerous organizations and bodies that do not always communicate or share information with each other.

• Insecurity: Paper-based certificates and identity documents can be easily tampered with, and digital badges are susceptible to duplication.

• Lack of transparency: Verification processes can be opaque and cumbersome, making it difficult to cross-verify credentials.

• Durability: Paper certificates can be lost, stolen, or damaged, while current digital certificates issued or stored on a centralized server don't guarantee long-term accessibility.

Challenges we ran into

So that first challenging part was to figure out the generating the dynamic certificates as per the collectors data and then issuer should be able to customize the certificates. Then the second challenge was to figure out the claiming part like when someone is opening the claim url so that particular collector should have only that claim url in which there will be certificates with his or her name. So the last challenge we faced is I had to link the token with the unique claim tokens so that claimer can claim the particular token so we were not able to get tokenIds which we were just minting. So after so many try we figured out and added the code for that and then we were able to get the tokenIds but again we were not able to get the latest one means when we are getting the tokenIds at that time transaction was not completed. Then we found the one way to call particular block of code once transaction is completed by adding one FCL function call.