πŸͺŸUsecases

Multiple Web3-enabled Use Cases:

🏞 Database NFT

The NFT space is growing at a rapid pace today, and Glacier will be one of the most professional and friendly database protocols used to store NFT metadata as the metadata of NFT is also in the NoSQL data structure. NFT will be the most important user scenario and Glacier will expand the adoption in the NFT space first.

πŸ™Œ SocialFi

SocialFi dApps mainly deal with the social connections of Web3 natives and have great needs in storing the Web3 natives’ social connection data in a structural way. Therefore, Glacier will help the SocialFi developers achieve that in a friendly and low-cost way. At the same time, SocialFi developers could also use the Glacier database engine to easily build a social graph for its users since they could store the user data in a graph database which is supported by Glacier.

πŸ‘Ύ Metaverse

GameFi projects can have thousands of NFT items in their blockchain games, meaning that they have a huge burden to store the related asset data and user data. Glacier’s NoSQL database engine could help GameFi developers store them in a structural way in Glacier’s nodes and the Arweave chain. At the same time, they could use Glacier to easily update and query the related asset data and user data by leveraging Glacier’s SDK.

πŸ’  Data Monetization

In Web2.0 applications, all the user data is stored in the storage space provided by a single technical giant, like Apple, Facebook or Twitter. They don’t have any desire to share their own user data with other companies to build a universal social graph that could be of tremendous value to society.

Last updated