Caze

Caze

A Web3 based Subscription platform for Creators to get support from their audience and enjoy exclusive contents and perks for the users according to the subscription plan selected.

8
Caze

Caze

A Web3 based Subscription platform for Creators to get support from their audience and enjoy exclusive contents and perks for the users according to the subscription plan selected.

The problem Caze solves

Caze is decentralize platform to support your favorite creators on a subscription basis, creators from different domains can create a account.

Caze is a totally free, decentralized & Open source for creators with no fees attached , so no worries of paying hefty fees to the big platforms and enjoy it to your fullest.

Creators can fill the form on the /Register page and the then their data is added onto IPFS and then in the contract, later they get NFT dropped straight to the registered wallet. A sharable profile link is provided for the creator profile to share with their audience with subscription plans.

Creator can post from the /Account section specially designed for them. Posts are also stored on IPFS and in the contract . Also shows the balance and subscribers of the creator

All creator profiles registered on the platform are displayed under the /Explore section , extracted right from the contract and IPFS . Users can explore the page to look out for their favourite creators.

A separate creator /profile page contains all the info for data of the creator from contract and IPFS . Title , Bio , pfp and the posts from the creator itself .

Folks can visit any creators profile and subscribe them on a monthly basis and can choose among three different plans. A subscriber will then have access to member only posts uploaded by a creator. A NFT according to the plan is already minted in the backend.

Challenges I ran into

These are some challenegs and issues we faced while building the project , but we even enjoyed overcoming them too.

  • We had faced some issue in fetching data from IPFS and rendering the data in the frontend with mapping .
  • We struggled with the docs for fetching the data in proper format , but later figured it out with bit of tries.
  • Implementing dynamic mapping for creator profiles with our frontend React.js and render the profile for each creator.
  • We faced issues with the contract , Majorly the subscription contract because it was a bit complex to manage the data for the creators and users but in the end , after improving it day by day , we pulled it off.

Discussion