> For the complete documentation index, see [llms.txt](https://support.bancor.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.bancor.network/bancor-dao/creating-a-bancor-improvement-proposal-bip.md).

# Creating a Bancor Improvement Proposal (BIP)

Below is a simple guide explaining how to create a Bancor Improvement Proposal:

1\. **Publish Proposal**: Anyone can publish a proposal on the Bancor governance forum at gov.bancor.network.

2\. **Discussion Period**: DAO proposal is up for discussion for a minimum of 3 days.

3\. **Voting Period**: After the discussion period has passed, the proposal can be put up on [Snapshot](https://vote.bancor.network) by any DAO member with a minimum of 25k vote power. This generally occurs around Sunday, 5pm GMT with voting period lasting 3 days.

4\. **Voting concludes**: Proposal passes as long as it meets the minimum quorum and FOR votes.

<figure><img src="https://2740266393-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyrOMQvtpp4gARdewefVZ%2Fuploads%2Flral1neiY8LA8lbyPjDK%2FProposal%20Quorum%202.png?alt=media&amp;token=87fb1527-2649-4580-8879-39b4aee6ca85" alt=""><figcaption><p>Bancor DAO Quorum and Supermajority Requirements </p></figcaption></figure>

5\. **Final steps**: Proposal is moved to the Archive Category on gov.bancor.network. If it passes, the corresponding tasks are added to the Bancor pipeline for implementation.<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.bancor.network/bancor-dao/creating-a-bancor-improvement-proposal-bip.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.