---
# System prepended metadata

title: Juno Delegation Program

---

# Juno Delegation Program

## Why do we have a delegation program?
The three core components of any distributed proof of stake blockchain are delegators, validators and the founding team. As the blockchain matures, additional roles are required to assist with community engagement and support to build on foundations set from genesis. Typical members/roles added include developers, marketing managers, and community managers. As Juno is a DAO-based blockchain, managing delegations to validators from the Juno Development Fund is responsibility of the Operations Department, as state in the [Juno Charter](https://hackmd.io/@G2q75faESMyRkexdnhUCpA/B1NPVxxRh).

## Objectives
- Protect the Juno Treasury from on-chain inflation
- Reward validators for their work on the chain
- Incentivize building on the Juno smart contract platform

## Overview of the delegation program
For this cycle, the Juno Operations Department, in behalf of Juno Council, has a total of `10,000,000 JUNO` to delegate. The current cycle will last for **1 year**, starting *May 1st 2024* and ending *May 1st 2025*.

The program will cover two main categories

### Standard Validator Contributions

70% of the total amount is dedicated for this category. Delegations will be distributed to all the eligible validators, following a points based system.

#### Examples
- Base delegation
- RPC, Rest & Relayer infrastructure
- Snapshots and other services
- Community Content
- Governance

### dAPP Builders contributions

30% of the total amount is dedicated for this category. Delegations will be distributed to all eligible validators, following the dAPP valuation criteria.
If you are building a dAPP but you are not a validator you may consider running one or applying to the other grant programs we have in place.

#### Examples
- Create something unique on Juno
- Deploy existing dAPPs on Juno
- Open source contributions to existing dAPPs on Juno

While the standard application form will be open only for 2 weeks, validators building dAPPs can apply anytime during the program.

### Schedule
1. **April 1st:** New guidelines for the delegation program are published, and validators can apply using the provided form.
2. **April 15th:** Standard applications for the delegation program will be closed.
3. **April 15th:** New form will be opened for dAPP builders late submissions.
4. **May 1st:** Applications are reviewed and delegations are deployed 


## Points Based Delegations

In the following table you'll find out a list of possible, but not limited, contributions. 

Points will be awarded discretionally by the operations department based on the relevance of every single contribution. For example, a validator relaying 10 different chains might get more points compared to a validator only relaying one.

| Category | Description | Max Points |
| -------- | -------- | -------- |
| RPC, gRPC, Rest endpoins | Run high rate limited public endpoint     | 100     |
| Juno branded RPC | Connect one of your RPCs under the Juno Network Domain | 100 |
| Relayers | Run relayers btween Juno and various Cosmos Chains | 200 |
| Snapshots and other services | Share your snapshots, state sync, and other services trough a dedicated, easy to access, UI | 100 |
| Community Content | Manage a localized community, create content around Juno | 200 |
| Governance | Actively vote on majority of governance proposals, share rationales about your votings trough socials or dedicated ui | 200 |
| Core contributions | Contribute to Juno Core and the CosmWasm Stack affecting Juno directly | 200 |
| Other | Anything you think its worth a delegation | 100 |