├── assets └── dTok │ ├── dtok-logo.jpg │ ├── dtok-mockup.jpg │ └── dTok_Complete_Phase_1.png ├── .github ├── workflows │ ├── send_to_discord.yml │ └── close_inactive.yml └── ISSUE_TEMPLATE │ ├── microgrant.yml │ ├── open_livepeer_network_grant.yml │ ├── video_disruptors_grant.yml │ └── sponsorship.yml └── README.md /assets/dTok/dtok-logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/livepeer/grants/HEAD/assets/dTok/dtok-logo.jpg -------------------------------------------------------------------------------- /assets/dTok/dtok-mockup.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/livepeer/grants/HEAD/assets/dTok/dtok-mockup.jpg -------------------------------------------------------------------------------- /assets/dTok/dTok_Complete_Phase_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/livepeer/grants/HEAD/assets/dTok/dTok_Complete_Phase_1.png -------------------------------------------------------------------------------- /.github/workflows/send_to_discord.yml: -------------------------------------------------------------------------------- 1 | name: Send issue to Discord 2 | on: 3 | issues: 4 | types: 5 | - opened 6 | jobs: 7 | notify_discord: 8 | runs-on: ubuntu-latest 9 | steps: 10 | - name: Send Discord notification 11 | env: 12 | DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }} 13 | uses: Ilshidur/action-discord@0.3.2 14 | -------------------------------------------------------------------------------- /.github/workflows/close_inactive.yml: -------------------------------------------------------------------------------- 1 | name: Close inactive issues 2 | on: 3 | schedule: 4 | - cron: "30 1 * * *" 5 | 6 | jobs: 7 | close-issues: 8 | runs-on: ubuntu-latest 9 | permissions: 10 | issues: write 11 | pull-requests: write 12 | steps: 13 | - uses: actions/stale@v4.1.1 14 | with: 15 | days-before-issue-stale: 35 16 | days-before-issue-close: 7 17 | stale-issue-label: "stale" 18 | stale-issue-message: "This issue has been marked as stale with no activity. It will close in 7 days." 19 | close-issue-message: "This issue has been automatically closed." 20 | days-before-pr-stale: -1 21 | days-before-pr-close: -1 22 | exempt-issue-labels: "help wanted" 23 | repo-token: ${{ secrets.GITHUB_TOKEN }} 24 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/microgrant.yml: -------------------------------------------------------------------------------- 1 | name: Microgrant 2 | description: Grant application for hackathon winners and other tightly scoped projects. Must be completed in one month. Up to $2K. 3 | title: "[Microgrant]: " 4 | labels: [] 5 | assignees: 6 | - hansy 7 | body: 8 | - type: textarea 9 | id: problemQuestion 10 | attributes: 11 | label: What is your project, and what problem does it solve? 12 | description: (max 100 words) 13 | validations: 14 | required: true 15 | - type: input 16 | id: githubLink 17 | attributes: 18 | label: Link to public GitHub repo (if applicable) 19 | validations: 20 | required: false 21 | - type: input 22 | id: demoLink 23 | attributes: 24 | label: Link to demo website (if applicable) 25 | validations: 26 | required: false 27 | - type: textarea 28 | id: livepeerUsageQuestion 29 | attributes: 30 | label: How is Livepeer used for this project? 31 | description: (max 100 words) 32 | validations: 33 | required: true 34 | - type: textarea 35 | id: improvementQuestion 36 | attributes: 37 | label: How will you improve your project with this grant? What steps will you take to meet this objective? 38 | description: (max 200 words) 39 | validations: 40 | required: true 41 | - type: textarea 42 | id: hackathonQuestion 43 | attributes: 44 | label: Was this project started at a hackathon or another web3 event? Which one? 45 | description: e.g. Encode Next Video Hackathon 2023, EthDenver 2023 46 | validations: 47 | required: true 48 | - type: textarea 49 | id: teamQuestion 50 | attributes: 51 | label: Please describe (in words) your team's relevant experience, and why you think you are the right team to build this project. You can cite your team's prior experience in similar domains, doing similar dev work, individual team members' backgrounds, etc. 52 | description: Please also list each team member. For each team member, please include - (a) Name (b) Links to portfolio, website, and/or Github repo 53 | validations: 54 | required: true 55 | - type: textarea 56 | id: deliverableQuestion 57 | attributes: 58 | label: What is the project’s expected deliverable at the conclusion of the grant time period? 59 | description: e.g. published blog post/docs/videos, working application launched to production, etc 60 | validations: 61 | required: true 62 | - type: textarea 63 | id: coreMechanicQuestion 64 | attributes: 65 | label: What is the one thing (the core mechanic) you want someone to do when using your deliverable? 66 | description: e.g. for a video NFT minting application, you may want users to be able to upload and mint a video NFT 67 | validations: 68 | required: true 69 | - type: textarea 70 | id: benefitQuestion 71 | attributes: 72 | label: How will this deliverable benefit the Livepeer ecosystem? 73 | validations: 74 | required: true 75 | - type: textarea 76 | id: usersQuestion 77 | attributes: 78 | label: Who is your target user group? How do you plan on obtaining them? 79 | validations: 80 | required: true 81 | - type: textarea 82 | id: attributionQuestion 83 | attributes: 84 | label: How did you learn about the Livepeer Grants Program? 85 | validations: 86 | required: true 87 | - type: input 88 | id: walletAddress 89 | attributes: 90 | label: What's your wallet address? 91 | description: Optional, but supplying a wallet address may give access to relevant onchain credentials and ecosystem benefits 92 | validations: 93 | required: false 94 | - type: checkboxes 95 | id: livepeerWatermarkConsent 96 | attributes: 97 | label: Do you consent to using "Powered by Livepeer" watermark on your application? 98 | options: 99 | - label: "Yes" 100 | - label: "No" 101 | validations: 102 | required: true 103 | 104 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/open_livepeer_network_grant.yml: -------------------------------------------------------------------------------- 1 | name: Open Livepeer Network Grant 2 | description: Application for teams looking to build tooling/applications for node operators running on the Livepeer Network. 1-3 month timeline with milestones. Up to $15K. 3 | title: "[Open LN Grant]: " 4 | labels: [] 5 | assignees: 6 | - hansy 7 | body: 8 | - type: textarea 9 | id: problemQuestion 10 | attributes: 11 | label: Please describe your project. Start with the need or problem you are trying to solve with this project. Describe why your solution is going to adequately solve this problem. 12 | validations: 13 | required: true 14 | - type: input 15 | id: githubLink 16 | attributes: 17 | label: Link to public GitHub repo (if applicable) 18 | validations: 19 | required: false 20 | - type: input 21 | id: demoLink 22 | attributes: 23 | label: Link to demo website (if applicable) 24 | validations: 25 | required: false 26 | - type: textarea 27 | id: benfitQuestion 28 | attributes: 29 | label: Please describe in more detail why this proposal is valuable for the Livepeer ecosystem 30 | description: What are the benefits to getting this right? What are the risks if you do not get it right? What are the risks that will make executing on this project difficult? 31 | validations: 32 | required: true 33 | - type: textarea 34 | id: deliverableQuestion 35 | attributes: 36 | label: Please describe in details what your final deliverable for this project will be. 37 | description: Include a specification of the project and what functionality the software will deliver when it is finished 38 | validations: 39 | required: true 40 | - type: textarea 41 | id: milestoneQuestion 42 | attributes: 43 | label: Please break up your development work into a clear set of milestones 44 | description: For each milestone, please describe - (a) The software functionality that we can expect after the completion of each milestone. This should be detailed enough that it can be used to ensure that the software meets the specification you outlined in the Deliverables, (b) How many people will be working on each milestone and their roles, (c) The amount of funding required for each milestone, (d) How much time this milestone will take to achieve (using real dates) 45 | validations: 46 | required: true 47 | - type: textarea 48 | id: budgetQuestion 49 | attributes: 50 | label: Sum up the total requested budget across all milestones, and include that figure here. Also, please include a budget breakdown to specify how you are planning to spend these funds. 51 | validations: 52 | required: true 53 | - type: textarea 54 | id: maintenanceQuestion 55 | attributes: 56 | label: Specify your team's long-term plans to maintain this software and upgrade it over time 57 | validations: 58 | required: true 59 | - type: textarea 60 | id: teamQuestion 61 | attributes: 62 | label: Please describe (in words) your team's relevant experience, and why you think you are the right team to build this project. You can cite your team's prior experience in similar domains, doing similar dev work, individual team members' backgrounds, etc. 63 | description: Please also list each team member. For each team member, please include - (a) Name (b) Links to portfolio, website, and/or Github repo (c) Location (d) *Optionally* wallet address for access to relevant onchain credentials and ecosystem benefits 64 | validations: 65 | required: true 66 | - type: textarea 67 | id: attributionQuestion 68 | attributes: 69 | label: How did you learn about the Livepeer Grants Program? 70 | validations: 71 | required: true 72 | - type: textarea 73 | id: hackathonQuestion 74 | attributes: 75 | label: Was this project started at a hackathon or another web3 event? Which one? 76 | description: e.g. Encode Next Video Hackathon 2023, EthDenver 2023 77 | validations: 78 | required: true 79 | - type: textarea 80 | id: moreInfoQuestion 81 | attributes: 82 | label: Please include any additional information that you think would be useful in helping us to evaluate your proposal. 83 | validations: 84 | required: false 85 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/video_disruptors_grant.yml: -------------------------------------------------------------------------------- 1 | name: Video Disruptors Grant 2 | description: Application for teams looking to conduct cutting-edge video research and/or explore novel applications using Livepeer. 1-3 month timeline with milestones. Up to $15K. 3 | title: "[Video Disruptors Grant]: " 4 | labels: [] 5 | assignees: 6 | - hansy 7 | body: 8 | - type: textarea 9 | id: problemQuestion 10 | attributes: 11 | label: Please describe your project. Start with the need or problem you are trying to solve with this project. Describe why your solution is going to adequately solve this problem. 12 | validations: 13 | required: true 14 | - type: input 15 | id: githubLink 16 | attributes: 17 | label: Link to public GitHub repo (if applicable) 18 | validations: 19 | required: false 20 | - type: input 21 | id: demoLink 22 | attributes: 23 | label: Link to demo website (if applicable) 24 | validations: 25 | required: false 26 | - type: textarea 27 | id: benfitQuestion 28 | attributes: 29 | label: Please describe in more detail why this proposal is valuable for the Livepeer ecosystem 30 | description: What are the benefits to getting this right? What are the risks if you do not get it right? What are the risks that will make executing on this project difficult? 31 | validations: 32 | required: true 33 | - type: textarea 34 | id: deliverableQuestion 35 | attributes: 36 | label: Please describe in details what your final deliverable for this project will be. 37 | description: Include a specification of the project and what functionality the software will deliver when it is finished 38 | validations: 39 | required: true 40 | - type: textarea 41 | id: milestoneQuestion 42 | attributes: 43 | label: Please break up your development work into a clear set of milestones 44 | description: For each milestone, please describe - (a) The software functionality that we can expect after the completion of each milestone. This should be detailed enough that it can be used to ensure that the software meets the specification you outlined in the Deliverables, (b) How many people will be working on each milestone and their roles, (c) The amount of funding required for each milestone, (d) How much time this milestone will take to achieve (using real dates) 45 | validations: 46 | required: true 47 | - type: textarea 48 | id: budgetQuestion 49 | attributes: 50 | label: Sum up the total requested budget across all milestones, and include that figure here. Also, please include a budget breakdown to specify how you are planning to spend these funds. 51 | validations: 52 | required: true 53 | - type: textarea 54 | id: maintenanceQuestion 55 | attributes: 56 | label: Specify your team's long-term plans to maintain this software and upgrade it over time 57 | validations: 58 | required: true 59 | - type: textarea 60 | id: teamQuestion 61 | attributes: 62 | label: Please describe (in words) your team's relevant experience, and why you think you are the right team to build this project. You can cite your team's prior experience in similar domains, doing similar dev work, individual team members' backgrounds, etc. 63 | description: Please also list each team member. For each team member, please include - (a) Name (b) Links to portfolio, website, and/or Github repo (c) Location (d) *Optionally* Wallet address for access to relevant onchain credentials and ecosystem benefits 64 | validations: 65 | required: true 66 | - type: textarea 67 | id: usersQuestion 68 | attributes: 69 | label: Who is your target user group? How do you plan on getting your users to use this? 70 | validations: 71 | required: true 72 | - type: textarea 73 | id: attributionQuestion 74 | attributes: 75 | label: How did you learn about the Livepeer Grants Program? 76 | validations: 77 | required: true 78 | - type: textarea 79 | id: hackathonQuestion 80 | attributes: 81 | label: Was this project started at a hackathon or another web3 event? Which one? 82 | description: e.g. Encode Next Video Hackathon 2023, EthDenver 2023 83 | validations: 84 | required: true 85 | - type: textarea 86 | id: moreInfoQuestion 87 | attributes: 88 | label: Please include any additional information that you think would be useful in helping us to evaluate your proposal. 89 | validations: 90 | required: false 91 | - type: checkboxes 92 | id: livepeerWatermarkConsent 93 | attributes: 94 | label: Do you consent to using "Powered by Livepeer" watermark on your application? 95 | options: 96 | - label: "Yes" 97 | - label: "No" 98 | validations: 99 | required: true 100 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/sponsorship.yml: -------------------------------------------------------------------------------- 1 | name: Sponsorship Request 2 | description: Application for groups looking for sponsorship or participation (in the form of speakers) for hackathons, conferences, and bootcamps. 3 | title: "[Sponsorship]: Event Name" 4 | labels: [] 5 | assignees: 6 | - shann7 7 | body: 8 | - type: input 9 | id: referral 10 | attributes: 11 | label: Referral 12 | description: How did you find out about Livepeer? 13 | validations: 14 | required: true 15 | - type: input 16 | id: poc 17 | attributes: 18 | label: Point of Contact 19 | validations: 20 | required: true 21 | - type: input 22 | id: email 23 | attributes: 24 | label: Email 25 | validations: 26 | required: true 27 | - type: textarea 28 | id: teamBio 29 | attributes: 30 | label: Team Bio 31 | validations: 32 | required: true 33 | - type: textarea 34 | id: prevEvents 35 | attributes: 36 | label: Previously Organized Events 37 | description: Please list event name, year, and any relevant links 38 | validations: 39 | required: true 40 | - type: dropdown 41 | id: eventType 42 | attributes: 43 | label: Event Type 44 | options: 45 | - Hackathon 46 | - Conference 47 | - One-Off Event 48 | - Bootcamp 49 | - Other 50 | validations: 51 | required: true 52 | - type: checkboxes 53 | id: sponsorshipType 54 | attributes: 55 | label: Type of Sponsorship Requested 56 | options: 57 | - label: Financial 58 | - label: Speakers 59 | - label: Mentors 60 | - label: Judges 61 | - label: Other 62 | validations: 63 | required: true 64 | - type: checkboxes 65 | id: hasWorkshop 66 | attributes: 67 | label: Are Workshops/Talks part of the event? 68 | options: 69 | - label: "Yes" 70 | validations: 71 | required: true 72 | - type: textarea 73 | id: workshopLivepeerContent 74 | attributes: 75 | label: Please share more information on planned Livepeer-related content 76 | description: If "Yes" answered for "Are Workshops/Talks part of the event?" 77 | validations: 78 | required: false 79 | - type: textarea 80 | id: workshopPlannedTalks 81 | attributes: 82 | label: Please provide more information on planned talks and workshops (both confirmed and not yet confirmed) 83 | description: If "Yes" answered for "Are Workshops/Talks part of the event?" 84 | validations: 85 | required: false 86 | - type: input 87 | id: budget 88 | attributes: 89 | label: Budget Requested 90 | validations: 91 | required: true 92 | - type: textarea 93 | id: otherSponsors 94 | attributes: 95 | label: Other Sponsors 96 | description: List of other sponsors of the event. Both confirmed sponsors, and potential sponsors you are still confirming 97 | validations: 98 | required: true 99 | - type: input 100 | id: startDate 101 | attributes: 102 | label: Start Date of the Event 103 | placeholder: mm/dd/yyyy 104 | validations: 105 | required: true 106 | - type: input 107 | id: endDate 108 | attributes: 109 | label: End Date of the Event 110 | placeholder: mm/dd/yyyy 111 | validations: 112 | required: true 113 | - type: textarea 114 | id: durationInfo 115 | attributes: 116 | label: More Information on Duration 117 | description: If simple start and end date doesn't apply for the event you are organizing, please provide more information 118 | validations: 119 | required: false 120 | - type: input 121 | id: location 122 | attributes: 123 | label: Location of the Event 124 | validations: 125 | required: true 126 | - type: textarea 127 | id: locationInfo 128 | attributes: 129 | label: More Information on Location 130 | description: Share any relevant information on the location 131 | validations: 132 | required: false 133 | - type: input 134 | id: attendeesNum 135 | attributes: 136 | label: Expected Number of Attendees 137 | validations: 138 | required: true 139 | - type: checkboxes 140 | id: targetAudience 141 | attributes: 142 | label: Who is the Target Audience of the Event? 143 | options: 144 | - label: Students 145 | - label: Developers - newcommers to space 146 | - label: Developers - expeienced builders 147 | - label: Academia 148 | - label: Livepeer Users/Community 149 | - label: Broader Crypto Community 150 | - label: Potential New Users of web3 video/Livepeer 151 | - label: Other 152 | validations: 153 | required: true 154 | - type: textarea 155 | id: tailored 156 | attributes: 157 | label: How is the event tailored for the Target Audience? 158 | validations: 159 | required: true 160 | - type: textarea 161 | id: promotion 162 | attributes: 163 | label: How do you plan to promote your event to potential attendees? 164 | validations: 165 | required: true 166 | - type: textarea 167 | id: connect 168 | attributes: 169 | label: How can Livepeer connect with audience after the event? 170 | validations: 171 | required: true 172 | - type: textarea 173 | id: links 174 | attributes: 175 | label: Links 176 | description: Share any useful links you might have 177 | validations: 178 | required: false 179 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Deprecated 2 | This repo is now deprecated. Please visit the [Livepeer Grants homepage](https://livepeer.notion.site/Livepeer-Grants-Program-f91071b5030d4c31ad4dd08e7c026526?pvs=4) to apply for a grant. 3 | 4 | # Livepeer Grants 5 | 6 | Livepeer has a long term vision to build an open source and fully decentralized video stack, and we cannot achieve this goal without a community of contributors to the project. Livepeer Grants provide funding to projects that benefit the Livepeer ecosystem. 7 | 8 | Grants are paid in Livepeer token (LPT), providing contributors with an opportunity to both fund their projects AND build a position in the Livepeer’s Proof of Stake network. To receive a grant you will need a wallet that can receive funds on Arbitrum. We encourage grant holders to become delegators in the Livepeer network by staking their token with a Livepeer node operator to receive inflationary Livepeer rewards. 9 | 10 | If you're appreciative of this initiative and all that it will do for the ecosystem, stake with our orchestrator node, and contribute a portion of your inflationary reward to go towards these grants! Node address: **0x4f4758f7167b18e1f5b3c1a7575e3eb584894dbc**. 11 | 12 | Current grants program [tracker](https://livepeer.notion.site/37f787d7b4814840a7ac6b098eccb492?v=aa0d841cc2a641be9b8859605eba351d&pvs=4). 13 | 14 | After LPT is withdrawn from the staking pool in the community node, it is administered by the community grants committee via the multisig address arb:0x64e0aA4631ae8f74627e68Cf02565Bec30d2EA4F. 15 | 16 | ## Requirements 17 | 18 | Requirements for ALL GRANTS: 19 | 20 | - Projects must be open source 21 | - Showcaseable 22 | - We are open to funding projects built by teams or individuals, although it helps to have both product/UX + backend for the apps. Find people with complimentary skill sets to join you and collaborate by joining Discord and posting in the #web3-app-ideas channel. 23 | - Grants must be achievable within a 3 month timeline 24 | - Projects must display a "Powered by Livepeer" watermark, when applicable, to their application. It must be visible while a viewer is watching the video, whether that's in the player itself or in another location that would be easily seen by a viewer. 25 | 26 | ## Grant Types 27 | 28 | There are 3 types of grants to support supply and demand for Livepeer’s open video infrastructure. Please choose the one most appropriate for you. 29 | 30 | ### Microgrants - up to $2,000 USD 31 | 32 | Microgrants are geared towards tightly scoped projects with a clear deliverable that can be completed in 1 month or less. Examples of such projects may be: 33 | 34 | - Hackathon participants who want to complete a feature using Livepeer 35 | - Existing projects looking to polish their Livepeer integrations with a well-defined sprint 36 | - Educational guides/tutorials/videos targeted at a specific audience teaching them how to build with Livepeer. 37 | - Contributions to Livepeer documentation 38 | 39 | [Apply for a Microgrant here](https://github.com/livepeer/Grant-Program/issues/new?assignees=hansy&labels=&projects=&template=microgrant.yml&title=%5BMicrogrant%5D%3A+) 40 | 41 | ### Video Disruptor grants - up to $15,000 USD 42 | 43 | The Video Disruptor grant is intended for dedicated teams looking to conduct cutting-edge video research and/or explore novel, user-centered web3 applications that leverage Livepeer’s decentralized video compute network. We are interested in teams looking to apply tools like Artificial Intelligence, Machine Learning, AR/VR, etc to video in a web3 context. We also are interested in teams utilizing other web3 protocols and concepts like FVMs, zK-proofs, etc to create entirely new video experiences and tooling. 44 | 45 | We will also consider projects that either disrupt or offer entirely new video experiences vs incumbent, web2 applications. However, teams must demonstrate the ability to engage the community (ideally the team or project already has a large existing community) in a meaningful way to foster fast adoption, growth, and feedback. 46 | 47 | Projects must be completed within 3 months or less with clearly defined monthly milestones. 48 | 49 | [Apply for a Video Disruptor Grant here](https://github.com/livepeer/Grant-Program/issues/new?assignees=hansy&labels=&template=video_disruptors_grant.yml&title=%5BVideo+Disruptors+Grant%5D%3A+) 50 | 51 | ### Open Livepeer Network grants 52 | 53 | Open grants will be awarded to individuals and teams building tooling and applications to support supply-side node operations, delegation and overall health of the Livepeer Network. Examples of past open network grants include bots for better governance, educational content on how to get started as an Orchestrator or Delegator, tools to better parse/debug logs, etc. 54 | 55 | [Apply for an Open Livepeer Network Grant here](https://github.com/livepeer/Grant-Program/issues/new?assignees=hansy&labels=&template=open_livepeer_network_grant.yml&title=%5BOpen+LN+Grant%5D%3A+) 56 | 57 | ## How to apply 58 | 59 | 1. Submit an [issue](https://github.com/livepeer/Grant-Program/issues/new/choose). Product-based proposals must include specs in the submission. Include mockups, technical milestones, and time estimates. When in doubt breakdown milestones further. 60 | 2. Application will be reviewed by Livepeer Grants, which meets bi-weekly to discuss all on-going and proposed grants. (If you are interested in joining Livepeer Grants, ping @hansy, @shann, @adam, or @ericxtang in the #community-grants [Discord](https://discord.gg/livepeer) channel.) Applications will receive a decision for funding within 2-4 weeks of applying. 61 | 3. Approved grants will receive 20% of the total grant value upfront, followed by graduated payments in the form of milestone completions. Payment is made in LPT (on Arbitrum) based on the USD value of the milestone. The price of LPT used to make the payments is determined using a rolling 30-day average from the time the transaction is queued. 62 | 4. Feedback will occur throughout the grant process 63 | 64 | ## Grants Application Guideline 65 | 66 | - **Measurable result**: There should be success metrics for the grant proposal. The success metrics measure the impact on the community. 67 | - **Achievable**: The proposal should be feasible - and sufficient research should be done ahead of time for its feasibility. If it’s a research grant, a well-formed problem statement should be included. 68 | - **Demonstration of capability**: The grant proposal party should demonstrate sufficient experience to successfully achieve the end goal outlined in the proposal. Prior experience in a similar area is highly preferred. 69 | - **Impact for Livepeer**: The grant proposal should have a direct impact on the success of Livepeer and its community. The grant should be impactful to the success of the proposal. 70 | 71 | _Note: This repo is migrated from the [previous repo](https://github.com/Livepeer-Community-Node/Grant-Program) to kick start the new grants process_ 72 | 73 | ## Sponsorship Requests 74 | 75 | Interested in partnering with the Livepeer? We’d love to hear how we can join forces to drive awareness, understanding, and adoption of crypto technologies further into mainstream and digital-native audiences. 76 | 77 | For any sponsorship requests for your conference, hackathon, event, etc, please fill out the [following application](https://github.com/livepeer/Grant-Program/issues/new?assignees=shann7&labels=&projects=&template=sponsorship.yml&title=%5BSponsorship%5D%3A+%3CEvent+Name+Here%3E). 78 | --------------------------------------------------------------------------------