Tunify

Problem Statement

This project is a music streaming platform unlike Spotify it uses Pay as you Listen model users will be charged from minutes listened Sample scenario Consider a song of Ariana Grande - 7 Rings it has Spotify- 2.5 billions YT music - 2.6 billions apple music - some billions Youtube - 1.5 billionDespite being her one 15+ songs her annual earnings is less than 16 million* for her singing career if we don't consider the Shows she act on So for a famous song she earns around 2 million so we get the value of 0.0002 dollars per listening after including the making cost, patents,directors salaryIn conclusion you need to listen to 20000 songs to pay 2$ incorporating platform fees it will be always cheaper than current alternativesMusic listeners are not nerd so the wallet integration payment gateways are make abstract and seamless for easy onboarding

Solution

Tunify is a music streaming platform so it hold a lot of music files, thumbnails, and metadata. All of which are stored in IPFS storage offered by Opsec, I am using more than 2 Gigs of storage on IPFS thanks to OpsecFor easy user onboarding we are using privy's embedded wallets so people without prior web3 knowledge can also use the platform with ease, also the way privy handles non wallets client by integrating Gpay and other Onramping protocolFor all the chain interactions i are using Base network of its L2 robust handling of transactions I have contributed to Covalent Ai agent sdk to add support for hugging face and Gradio inferences. I have had a very good experience with Covalent in the past. I have raised PR for all the contributions that i have made in the ai-agent-sdk, kindly review it and merge it No one have tried using audio or other models on Covalent . The gradio and HF integration has made it easy to use high performance hosted models in any projectI have tried to use EigenLayer for rest of the interaction of backend and the contract