The problem MyStiq solves

1. Most centralized creator platforms today take away a huge cut of the pay received by the creators thereby reducing their profits. We have tried to solve this problem by creating a decentralized subscription-based streaming service where audiences can access their favorite creator’s content by buying an exclusive NFT and paying a subscription fee.

2. Payments management has been a headache many times. Thanks to SuperFluid’s Money Streaming utility we can stream and transfer money seamlessly with a click of a button.Also managing your team members and giving them timely payouts can be a nightmare as well as affect your productivity . We solve this problem by using SuperFluid’s Instant Distribution method to distribute the revenue received by the creator to its team members.

3. In an era where 80% of all Internet Bandwidth is consumed by video streaming, Implementing video streaming with proper transcoding has become a lot expensive. But thanks to Livepeer’s decentralized protocol which not only helps in reducing the cost upto 50 times but also provides streaming with proper transcoding.

4. Traditional authentication processes involve a lot of hectic procedures like numerous logins, 2FAs etc. At Mystiq your crypto wallet is your identity and is an one click process. Also thanks to Alchemy’s NFT API which helps us in authenticating whether a user has a Certain NFT to access a Creator’s content.

Challenges we ran into

1 . We were not familiar with most of the things that we have used in the project. Hence we had to learn and build everything while starting from scratch which was challenging.

2. Initially, we thought to make our website by putting mock data but later we had to learn how to use cloud storage platforms like firebase in order to store the data and make our platform more dynamic. Learning and implementing firebase from scratch caused a lot of errors which took a long time to resolve.

3. We ran into deployment issues as the look of our website in the deployment state was different from the one that we had on the local. We had to spend a lot of time figuring out and fixing the bugs.

4. Livepeer’s API did not work properly when called from the client-side and gave CORS error at the last moment. So we had to call it using an express server. We had never worked with express before so we had to learn and implement it from scratch at the last moment.