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

# CONTRIBUTING

## Thanks you in advance for contributing!

To add new content:

* Make sure it doesn't already exist.
* Most of the consensus are created and developed by projects themselves, and require to copy or explain some part of their White-paper. But there is no copyright infringement intended from my side. Just a try to list all consensus algorithms.
* Link to PDF is required. Open knowledge is mandatory. Papers where the PDF is not publicly and openly available for free will not be accepted.
* Don't add deck of slides, or document lacking an abstract, not a blog post, not a bitcoin forum post.
* Conference or journal and year must be stated if available.

Please stay on topic!

You can open PR on Github <https://github.com/cedricwalter/blockchain-consensus>&#x20;

### Contact

You can contact me using Twitter [@CedricWalter](https://twitter.com/CedricWalter?lang=en) or [@TokensEconomy](https://twitter.com/tokenseconomy)&#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://tokens-economy.gitbook.io/consensus/contributing.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.