The problem MetaVid solves

With the growing trend of over-the-top (OTT) streaming services like Netflix, password sharing and misuse have become major issues. This not only results in revenue losses for the companies but also hampers the overall user experience. That's where MetaVid comes in - a blockchain-based video platform that aims to provide a secure and efficient subscription-based streaming experience. Our platform uses a subscription model that gets renewed upon the user's subscription, thereby ensuring that only authorised users can access it. To further enhance security, we require a linked MetaMask account to stream content, which prevents password sharing and misuse. We also noticed a significant lack of subscription-based platforms that accept payments through multiple blockchain chains. MetaVid solves this issue by allowing users to pay for their subscriptions using their preferred blockchain chain, making the payment process more accessible and efficient. At MetaVid, we believe that secure and decentralised video streaming is the future. By providing a user-friendly platform that prioritises security and efficiency, we aim to provide an unmatched streaming experience to our users. Join us today and experience the future of video streaming!

Challenges we ran into

Poor/ outdated documentation or lack thereof, was a big issue that stalled our progress for quite a while.
Implementing new protocols like Livepeer and Push protocols was challenging as we had never worked with them before. But once we were comfortable with them, we were able to implement them well.
Faced difficulty in implementing Connext xchain app due to errors in the documentation. Had to shift from off-chain to on-chain and finally back to off-chain implementation, which worked only after the documentation got updated on 17 Feb.
The thumbnail loading property does not seem to exist in Livepeer, which created issues. The video kept playing directly without being prompted and so we had to shift to other methods to meet our project’s needs.
There were limitations in the on-chain implementation of Superfluid due to the requirement of prior approvals for contract deployment. The docs for upgradation of Supertokens from MATIC to MATICx were also insufficient. Also, the integration of Connext and Superfluid was quite tough but we implemented it all finally.