The problem Super Stream solves

Streamers depend on these services' centralised transcoding and distribution and pay YouTube about 40% of the cost of superchats. However, the quality of their streams is out of their hands because streamers have no influence over the transcoding quality or bitrate.

The fundamental issue with centralised platforms like Youtube, Twitch, and others is that the firm owns the content rather than the producers, and they also take a sizable portion of the earnings as commission. Additionally, they have the power to ban or suspend your channel or content at will or in response to government pressure.

The aforementioned issues drove the development of "SuperStream" a completely decentralised live streaming (Livepeer) and creator platform on ETH where users may watch/create live streams, send/receive tips, subscribe to their favourite creators, etc.

The Superstream platform can assist in achieving this goal utilising livepeer because, unlike centralised platforms, P2P networks allow media material to be delivered directly from content creators to the audience without the use of middlemen.

Features: -All users get a profile nft associated with their Superstream Account. -Can mint and publish recorded live streams as nft. -All data is stored in ipfs or blockchain. -Send or receive tips directly into your wallet in MATIC. -Innovative Subscription plan, only pay for every second that you are subscribed ( using superfluid protocol ). -Live Chat and Comments. -Leverages Livepeer transcoding and cdn services for streaming and recording stream.

Challenges I ran into

Faced numerous obstacles while the project was developed, including:
-Considering architecture and schema for storing different types of data, such as users, streams, etc.
-Because I am new to blockchain, I had a difficult time connecting with the front end and encountered numerous problems and glitches during the construction of smart contracts.
-I spent the most of my time making mistakes and conducting extensive trial and error.
-Due to time limits, I was unable to find solutions to issues on the front end side, such as listening to events, filters, and changing the UI.