Certifact

Certifact

An API for businesses to issue Blockchain based certificates to users on multiple chains in form of Single Owner Non Transferable Asset, without writing a single line of web3 code

Created on 29th May 2022

Certifact

Certifact

An API for businesses to issue Blockchain based certificates to users on multiple chains in form of Single Owner Non Transferable Asset, without writing a single line of web3 code

The problem Certifact solves

Facebook beginning the Metaverse has catapulted everyone to get into the world of web3. With this shift every industry from Finance to Ed-tech, is seeing a rapid change in the traditional systems.
So now a lot of companies want to issue certificates in form of NFTs to their users, but this leads to few major problems which we are solving with Certifact.

The problems :-

  • To issue certificates in form of NFTs every company needs to hire a web3 team to write their contract, integrate web3 with their system, which can be really expensive sometimes.
  • Certificates in form of traditional NFTs is not a smart-choice as it can be sold or transferred after issuing. If custom NFT contracts are written, people won't be able to showcase their certificates in any other platform other than ours, which is absolutely not favourable.
  • The companies also need to get their financial team ready to manage their cryptocurrencies and their blockchain wallets.
  • Companies have different requirements depending upon their particular use-case which might require them to shift between different blockchains, which is a very tedious task and need to make different Dapps for each chain.

The Solutions Certifact offers :-

Link to the detailed solutions

Challenges we ran into

  • The first issue we faced was to make the API fast, as blockchain based transactions take time and are slow. The solution for this is that we look for the CID(content identifier), once the root CID is ready we complete the request.
  • Another major issue we faced, is that we created the API with a lot of different features but during the short time of 24hrs we could not illustrate the demo of the features in our frontend. But we kept a demo of the API so that people can try it out.
  • And the last major issue we faced was making the hosted API https, in Google Cloud. It's doable by setting up load-balancers, but we need a domain for the complete process which we were unable of getting at this moment.

Discussion

Builders also viewed

See more projects on Devfolio