---
# System prepended metadata

title: Near Contributor Program

---

# Near Contributor Program

### What's already possible

![](https://i.imgur.com/LjaF8f3.png)

* Here's a view of all the entities that hold organization tokens (STR) within this organization called Open Startup.
* Note that Contributor Charlie currently has 15.6 STR.
* Users are connected via an Ethereum Identity Provider.

![](https://i.imgur.com/ph31PeT.png)

* New issues can be created, given a title and a description.
* We are currently integrated with GitHub to be able to sync already existing GitHub repositories and their issues. When you create a new issue on the platform, it gets created on GitHub as well.

![](https://i.imgur.com/OOW1rR3.png)

* Here's our newly created issue, which we are now going to fund with some organization tokens.

![](https://i.imgur.com/X0fsM4d.png)

* We can determine whether we'd like contributors to apply to the bounty first before they upload a work submission.
* We're going to fund this issue with 3 STR and mention that it's for Beginners.
* Experience Levels can be configured in the settings panel. They are specially useful when the organization funds issues according to an hourly model vs. a fixed model (the latter is what we're currently demoing).
* Hourly model sets the bounty price = base rate per hour x experience level multiplier.

![](https://i.imgur.com/VnhhfrU.png)

* In this organization, a bounty is enacted once it is approved by its members. 
* This is a really simple configuration to change based on the organization's preferences. For example, you can restrict the ability to fund issues to a single entity.

![](https://i.imgur.com/oiFxnNU.png)

* The issue bounty was approved and now anyone can submit an application.
* At this point, 3 STR tokens are escrowed to a contract that's associated to the completion of this issue.

![](https://i.imgur.com/z61kwtn.png)

* Participants can specify their work plan, estimated number of hours, and an estimated date of completion.

![](https://i.imgur.com/kzSfsyv.png)

* Applications can be approved by users with the right permission privileges.

![](https://i.imgur.com/FBffLtS.png)

* We've assigned the bounty to contributor Charlie.
* In the activity panel it appears as if it's always the same person interacting with the bounty. That's because what's being displayed is my GitHub profile, not my Ethereum identity. We've worked a fix on our staged environment.

![](https://i.imgur.com/nKk56z4.png)

* Contributor Charlie is ready to submit the work.

![](https://i.imgur.com/ASUI90x.png)

* We're reviewing Contributor Charlie's work submission. Looks good!

![](https://i.imgur.com/gBGX06a.png)

* Here's the updated issue status now that the bounty has been completed.

![](https://i.imgur.com/5JZ5ybd.png)

* Here's the reviewed work that now has an updated submission status.

![](https://i.imgur.com/RlxZHMb.png)

* And here we can see that Contributor Charlie has an extra 3 STR tokens, which he earned by fulfilling the bounty.

Some other things that are currently possible:

* Instead of assigning NEAR tokens directly to bounties, you could set up a "contributor token" that only has utility within the platform, and set up a reward pool of actual NEAR tokens that are disbursed at a specific or recurring dates according to who holds a % of the total amount of contributor tokens. This encourages community engagement over time.

### What's already possible (in our staging environment)

* No requirement to connect to GitHub in order to create and interact with bounties.
* Integration with 3Box profiles.
* Adding comments on issues.

## Potential exploration for Near

* Integration with Near Wallet instead of Ethereum based.
* KYC process by integrating an additional token that can be minted by the Near Foundation as the admin to users that pass a KYC process off chain. This would allow Near to ensure that only verified users can interact with the platform. We could already provide support for this straight away.
* Support for better categorization of bounties and application processes.
* Tailoring the user experience and design further to Near's needs and its users.