Professional documents repository on Flow blockchain

The problem Certifi solves

NFT mass adoption in B2B & B2C usecases are lacking behind complex wallets, workflows & tech savvy UI/UX.
Institutions, Businesses, Professionals & Students can explore the power of blockchain, By storing their professional documents on chain.

Flow's walletless onboarding + Blocto Wallet FCL Auth declutters the typical public/private key hiccups.

Certifi.ly's NFT Documents

  1. Certificates : Online & Offline Educational Institutions (Customizable Templates)
  2. Documents : Multi-counter party signable agreements/contracts with public & private (protected/encrypted) info with ZK verification.
  3. Web3 Memberships: By owning a specific NFT across Flow blockchain (different flow storage) to gain access to apps.
  4. Cards: Proof of purchase document issued by brands/companies to users to claim warranty.
  5. Tickets: To access events

Demo credentials are available in our github repo. Create a new user within demo institution and mint certificates.

Challenges we ran into

Eventhough we have successfully onboarded users walletlessly, Allowing the end users to claim ownership of those child accounts was a challenge., We had to go through flow tutorials and multiple sample github projects to figure it out. Finally we were able to develop "Claim Child Account" feature & implemented hybrid custodial revokking mechanism as well successfully.

Certificates are generated as PDF files., But we think PDF is good for documents/contracts type NFTs only and for certificates., it is better to generate as an image file instead PDF. So that an image preview looks better when shared on social networking sites.

(TBD: To be developed)
For documents/contracts type NFTs, We are exploring ways to store private (protected) information. 1. Encrypt and store on IPFS and decrypt upon successful FCL auth, 2. Encrypt and store in Internet Computer (Dfinity) and reterive upon successful FCL auth. (we may need to write a bridge between FCL and ICP canister read operation). 3. Encrypt and store in a cloud (on-premise of institutions or certifily's infrastructure & reterive)