> For the complete documentation index, see [llms.txt](https://eosforce-1.gitbook.io/eosc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eosforce-1.gitbook.io/eosc/proposal/eosforce-mainnet-improvement-proposal/fip-5-community-secretary-compensation-proposal.md).

# FIP#5 Community Secretary Compensation Proposal

To improve community governance efficiency and to attract more network BPs to community governance, it is proposed:

1. Each member of the Community Secretary receives 10,000 EOSC as salary compensation each month
2. Implementation starts at the election of the 3rd Community Secretary
3. The token compensation comes from the Developer Fund account

> Notes:
>
> According to “EOSForce Mainnet Super Node Meeting Rules”, Community Secretary consists of 1 Chief Secretary, 2 Deputy Secretaries, and 1 Host in rotation. Compensations are calculated based off the token. Low price encourages the staff effectiveness and high price attracts more people to apply for the position

2019.2.25


---

# 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://eosforce-1.gitbook.io/eosc/proposal/eosforce-mainnet-improvement-proposal/fip-5-community-secretary-compensation-proposal.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.