---
# System prepended metadata

title: Sponsor Program
tags: [Templates, Documentation]

---

---
title: 'Sponsor Program'
disqus: hackmd
---

Sponsor Program
===
The Sponsor Program allows Dev Protocol users to lock up their DEV for three months by staking for OSS projects not yet onboarded. Sponsors' rewards begin to accumulate as soon as they stake, but are locked until the OSS project tokenizes. If the OSS project doesn't onboard then rewards are burned and users receive their DEV back. The Sponsor Program has boosted rewards to increase the incentive for users.

## Table of Contents

[TOC]

Motivation
---
The Sponsor Program allows Dev Protocol users to stake for projects that are not yet onboarded. This should increase the community's enthusiasm, organic growth, marketing, and awareness. 

Boosted Rewards
---
Users will have a lower APY because of the Sponsor Programs formula: (Current Market APY)-(SP Inflation Capture)-(Incubator Inflation Capture) = Sponsor Program APY. The lower APY and mandatory lock will limit the incentive to participate in the Sponsor Program. Dev Protocol should boost rewards if OSS projects onboard.

**Feedback**
1) Some OSS projects have a higher chance to onboard then others therefore the boost should reflect that.
    a)  Use Github metrics to determine project's boost
    b) Team chooses beforehand which projects are part of the Sponsor program

Liquidity Mining
---
An alternative to boosted rewards is liquidity mining. Users that participate in a successful Sponsor Program will receive part of the OSS token allocation that the Dev Protocol Treasury receives. 

**Concerns**
1) Users will begin trading the OSS token on Uniswap
2) Foundations will have external stakeholders

User story
---

```gherkin=
Feature: Sponsor Program

  # The first example has five steps
  Scenario: User submits OSS project to Sponsor Program
    When Dev Protocol approves application
    Then Dev Protocol creates pool for OSS project
    Then the User locks DEV tokens for OSS project for 90 days
    When the OSS project joins both parties receive rewards

  

```

> Read more about Gherkin here: https://docs.cucumber.io/gherkin/reference/

User flows
---
```sequence
User->Dev Protocol: *Submits OSS Project*
Dev Protocol->Sponsor Pool: *Accepts Application*
User->Sponsor Pool: User locks DEV tokens
Note left of Sponsor Pool: *APY is changed*
Note right of Sponsor Pool: **DEV locked for 90 days**
Sponsor Pool->Authentication: *Rewards distributed*
Note right of Authentication: *Boosted rewards sent*
Authentication->Users:
```

> Read more about sequence-diagrams here: http://bramp.github.io/js-sequence-diagrams/

Technical Requirements
---
1) APY needs to be calculated as the following:
    (Current Market APY)-(SP Inflation Capture)-(Incubator Inflation Capture) = Sponsor Program APY
2) Escrow for Locked DEV 
3) Boosted Rewards

Project Timeline
---
```mermaid
gantt
    title A Gantt Diagram

    section Creation
    UI/UX           :a1, 2021-02-01, 15d
    DEVELOPMENT     :al, 2021-02-01, 40d
    section Testing
    Bugs      :2021-03-14  ,3d
    Content       : 5d
```

> Read more about mermaid here: http://mermaid-js.github.io/mermaid/

Project Roles
---
1) Smart Contract Lead- Taniguchi
2) UI/UX Design- Stas
3) Product Management- Aggre, Scott
4) Frontend Development- Daan
6) Content- Stas, Scott


## Appendix and FAQ
1) Does new asset inflation occur?
    a) Not until the OSS project authenticates.
    
2) What happens after 90 days to rewards?
    a) Staking and creator rewards are burned after 90 day threshold.
:::info
**Find this document incomplete?** Leave a comment!
:::

###### tags: `Templates` `Documentation`
