> For the complete documentation index, see [llms.txt](https://jpg-protocol.gitbook.io/jpg-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jpg-protocol.gitbook.io/jpg-docs/canons/governance.md).

# Governance

In the early stages of our rollout, JPG will release canons we believe to be particularly valuable to the ecosystem or that uniquely demonstrate the Canons’ potential. The contents of the Canons will be generated and controlled by the community and archived on Arweave.

Following the Beta stage, any JPG NFT holder will be able to propose their own Canon for community vote, allowing for emergent categories and conceptual systems to develop.

Below is a technical overview of the Canon governance system.

### Access

Access to the governance system is provided by the Canonicon NFT, which tracks your curation history, reputation, and voting power. As a user makes proposals and votes, their voting power within the system increases, meaning they have more sway within the system.

### System Architecture

Coming soon.

### Governance Lifecycle

The governance lifecycle of Canons relies on a weekly system. Over the course of one cycle, all new proposals are stored in Pending, at the conclusion of that cycle, they are moved into Active, where they are then eligible for voting.\
\
Similarly, submissions in the Active category are eligible for voting throughout the cycle, at the conclusion of which they are either Canonized or Rejected.

### Reputation System

JPG's reputation system is designed to create a positive sum environment that encourages active participation and "correct" consensus.

The primary factors impacting JXPG rewards for voting on Canons are: Majority/Minority, Difference between Majority/Minority, and Vote Ordering Batch.<br>

Put as simply as possible, Majority earns more JXPG than Minority, and the difference in rewards is correlated with the difference in Majority/Minority votes (a 51/49 split leads to very similar rewards for Maj/Min, while a 99/1 leads to a large reward difference.) Finally, the earlier you vote relative to other voters, the more JXPG you will be awarded.\
\
Reward calculations can be performed with the following:

**Proposal Accepted (Quorum Reached):**

Proposer Reward:

$$ProposerReward = b$$

Majority Vote Reward:

$$JXPG=c^{x}\left(sb\right)\left{1\le x\le10\right}\ \left{y\ge l\right}$$

Minority Vote Reward:

$$JXPG=c^{x}\cdot\left(p+0.5\right)\cdot\left(sb\right)\ \left{1\le x\le10\right}\left{y\ge l\right}$$

Spam Vote:

$$JXPG = - 0.25 \*b$$

**Proposal Rejected (Quorum Reached):**

Proposer Reward:

$$JXPG =\left(p+0.6\right)\cdot sb$$

Majority Vote Reward:

$$JXPG\ =\ c^{x}\cdot sb\ \left{1\le x\le10\right}\left{y\ge20\right}$$

Minority Vote Reward

$$JXPG\ =\ c^{x}\cdot\left(p+0.5\right)\cdot\left(sb\right)\left{1\le x\le10\right}\ \left{y\ge20\right}$$

Spam Vote:

$$JXPG = - 0.25 \*b$$

**Proposal Voted as Spam:**

Proposer:

$$JXPG = -b$$

Approve Voters:

$$JXPG = -0.5 \* b$$

Reject Voters:

$$JXPG = -0.25\*b$$

Spam Voters:

$$JXPG = 30$$

**Variables:**

$$b = 100$$ - Base JXPG Value

$$x = Batch$$ - Integer between 1 and 10

$$s  = 0.8$$ - JXPG scaled difference between proposing and voting (1.0 = Least Difference)

$$c = 0.93$$ - Impact of early versus late voting (1.0 = Least Impact)

$$p = Minority/Total$$

NOTE: In the case where a calculation falls finds a JXPG reward to be less than 20, it is set to equal 20. In other words, 20 is the minimum JXPG reward unless noted otherwise as in the case of spam situations.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jpg-protocol.gitbook.io/jpg-docs/canons/governance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
