The value of your NFT is derived from its unique story. That story includes how the token was minted, press about the artist (you) or team, trading and on-chain info, certifications, related items, and a lot more. But right now, there isn’t a way to provably tie that varying data from on and off-chain sources to the token or to view it easily in one place. That’s what FungyProof solves. FungyProof is a grading and enrichments platform for the metaverse. It enables NFT collectors and creators to aggregate and show off everything about their token that makes it stand out from the rest. Use FungyProof to Grade and discover the Mint Conditions of your NFT to easily know where data lives and how well it’s crafted. Digitally encase your token to add it the FungyProof registry ensuring it’s data become future-proof. Once encased, enrich your NFT with upgrades, achievements, rare cases and items all owned by the NFT. Attribute more value and continue customizing long after your token has been minted. When you sell your token all of its data stays with it so future owners inherit the accrued story and are able to write the next chapter.

FungyProof showcase

How it's made

The project is built on top of a serverless API backend and React. The Sponsor technology we used included: Ceramic, Covalent, Polygon, Textile's ThreadDB, IPFS and The sponsor tech stack was extremely beneficial in a number of ways, Textile made it simple to forgo a full database solution for a quick 2 week project. Polygon made it quick and easy to get our NFT and our Enrichment contracts onto a testnet. Web3.Storage made it simple to be able to make use of Filecoin for economic incentives for IPFS storage for all of the applications assets, the frontend hosting, and the NFT backup system we created. Finally Ceramic is the backbone for the application concept, allowing us to store NFT data and external enrichment information on an append-only registry with commit history, that will be editable by the owner of the NFT. There were definitely some corners cut, specifically, the UI contains several mixes of UI frameworks for the sake of brevity on component buildout, the API does not use any background jobs or event processing (so the requests can be very slow), and the Smart contract could likely use a security audit. I'm impressed by the amount we accomplished, including a very user-friendly UI, a complex backend with several integrations, and a new Contract standard. I was also impressed by our ability to coordinate across three of the farthest apart timezones.

Technologies used