livepeer / grants

⚠️ DEPRECATED ⚠️ Please visit the new homepage at https://livepeer.notion.site/Livepeer-Grants-Program-f91071b5030d4c31ad4dd08e7c026526
44 stars 7 forks source link

DoinGud Protocol #98

Closed Jameel139 closed 1 year ago

Jameel139 commented 1 year ago

Give a 3 sentence description about this proposal.

The proposal entails implementing the “go-live” feature on DoinGud website or app. The feature targets two core user types: Creators and Impact Reporters. Creators can live stream their creative process or other announcements (e.g. live NFT drops) for their community. Impact Reporters can live stream how social causes are using their funds and the impact it's creating on-ground. Live streams can optionally be recorded and accessible later.

Describe the problem you are solving.

  1. Creators: If a creator/artist wants to have a 1-1 time with his NFT community, there are very few options available out there. Discord is not the best of those, and youtube/twitch cannot be token-gated just to their community. As such, we are integrating the community engagement tool with an NFT marketplace so that artists can sell his/her NFT as well as talk to them within bounds and have true feedback.
  2. Impact Reporters: Currently there is not enough transparency on the impact generated by social causes, and current forms of reporting and segmented when it comes to on-ground impact. By integrating live streaming of impact reports into the DoinGud Protocol and linking it to specific social causes, the community will get more visibility on who are the most impactful social causes and allocate funds accordingly.

How will this benefit the Livepeer Ecosystem?

With the integration of Livepeer into DoinGud, a significant number of users will be exposed to and onboarded into using Livepeer on a regular basis (already 7k users in our beta closed platform, with significant growth and expected long term). This use case can also further inspire other adjacent use cases for DoinGud or other protocols to experiment with as well and contribute to the further proliferation of Livepeer adoption.

Describe the solution you are proposing.

  1. Creators:

Creators will be able to do a live stream which can be only watched/ accessed only by some specific NFT holders / NFT collection holders of that specific artist within the DoinGud platform.

Within the profile tab of the artist/creator, we will add a Tab (let's call it Stream) this will act as the main dashboard for the artist where they will handle all the live streaming backend just like Youtube Studio when a user does live streams.

We will embed the Livepeer dashboard within this tab and also include input from the artist for the NFT’s they wanna stream to, they can choose either a collection or some specific 1/1 NFT’s ( From the tech side we would just need the Contract Address of those NFT’s)

A user who holds the specific NFT of the artist who is doing the live stream will be able to access the Live stream from a TAB created on the home page.

This Tab will be visible to all the users of DoinGud and within this tab, we will show all the current live streams that are happening right now and will show a Thumbnail with a description of the NFT to watch the stream they will have to click on it and they will be redirected to a new page. This is the place where 2 things can happen:

  1. Impact Reporters:

Impact Reporters will be able to do a live stream connected to a specific social cause (or impact organization) which can be accessed by the Guild members connected to that cause on the DoinGud Protocol.

Within the profile tab of the Impact Reporter, in the “Submit Report” section, we will add an option to “live-stream” reports. This feature opens a dashboard that allows Impact Reporters to handle all the live streaming backend just like Youtube Studio when a user does live streams.

The live-streams will be visible to all the Guild members on the “Reporting Page” during the “reporting cycle”. This will enable the Guild members (signalers specifically) to watch the impact and vote on the quality of reporting as it happens.

Describe the scope of the project including a rough timeline and milestones

The product will be built in 4 phases with each phase having its milestones to be delivered.

Phase 1 (TBD) P1 will be a POC based product development where we will develop the product outside the bounds of DoinGud with our own website and servers and login systems.

The goal is to prove the development of all the features without worrying about designs and all the complexity it comes with integrating it with DG

Product Features to be Developed

  1. Creator studio
    • Livestreaming page with live analytics
    • Content Dashboard
    • Pre live stream page
    • Post live stream page
    • Creator dashboard for meta-level analytics of past live streams
  2. Token gated live streaming
    • Only available for certain NFT holders regardless the NFT is on DG or not
  3. Live chat
    • Different UI for NFT holders, non-NFT holders, and paid comment
  4. After stream content page for creators
    • Similar to the YouTube page
  5. Like & comment on a video on replay

Timeline 3-4 sprints + 1 sprint as a buffer (400 hours) With each sprint being 2 weeks.

People Involved (4) Sanchit (PM / Web3 FE / Livepeer Integration) FT Disha (Video Engineer / Web3 Backend) FT Aman (Web2 Backend / DevOps) FT David (Web2 FE) FT

Phase 2 (TBD) This phase will be focused on designing the product within the DG standards and in parallel, we will integrate all the connections and endpoints of user profile payments and stuff to DG standards.

In parallel when we will have MVP of the Frontend within the product we will start doing closed beta user testing with our creator pool of 531 who are already active on the platform.

Product Features to be developed

  1. UI/UX Design (Web+Mobile)
    • Creator Dashboard
    • Livestreaming Page for users and for the creator
    • Analytics page
    • Chat
    • Like and comment
  2. Dev
    • Forking the DG to deploy the POC within DG with new designs but still remaining a separate part of DG
    • [Maybe] Looking into lens protocol or polygon ID for ZK

Timeline 2 sprints + 1 sprint as a buffer (400 hours)

People Involved (7) Sanchit (PM / Web3 FE / Livepeer Integration) PT Disha (Video Engineer / Web3 Backend) FT Aman (Web2 Backend / DevOps) FT David + 1 (Web2 FE) FT Enialo + 1 (UI/UX Design) FT

Phase 3 (TBD) Phase 3 will focus on the final integration of the UI/UX developed during Phase 2 with all the dev resources which were built during POC in phase 1 according to the existing DG profile standards and the later part will be QA testing before making it live on staging and then on main.

Timeline 3 + 1(QA) sprint + 1 sprint as buffer (400 hours)

People Involved (6) Sanchit (PM / Web3 FE / Livepeer Integration) FT Disha (Video Engineer / Web3 Backend) PT Aman (Web2 Backend / DevOps) FT Nestor + 2 (Web2 FE / QA/ Integration) FT

Phase 4 (TBD) Phase 4 will focus on the implementation of Impact Reporting Live Stream feature. Similar steps as Phases 1-3 will be followed with small tweaks on the UI/UX and back end side.

Timeline 3 + 1(QA) sprint + 1 sprint as buffer (100 hours)

People Involved (6) Sanchit (PM / Web3 FE / Livepeer Integration) FT Disha (Video Engineer / Web3 Backend) PT Aman (Web2 Backend / DevOps) FT Nestor + 2 (Web2 FE / QA/ Integration) FT

Please estimate hours spent on the project based on the above

1300 hours spread across 10 folks across different sprints

github-actions[bot] commented 1 year ago

This issue has been marked as stale with no activity. It will close in 7 days.

github-actions[bot] commented 1 year ago

This issue has been automatically closed.