> For the complete documentation index, see [llms.txt](https://docs.ecroxscan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecroxscan.com/general-1/network-details/network-upgrades/fips.md).

# FIP's

### What is a FIP?

FIP stands for Ecrox Improvement Proposal. A FIP is a design document providing information to the Ecrox community, or describing a new feature for Ecrox. The FIP should provide motivation and technical specification for the feature.

| FIP   | Description                                                  | Status                                                 |
| ----- | ------------------------------------------------------------ | ------------------------------------------------------ |
| FIP-1 | Introduction and explanation about FIP's                     | Done                                                   |
| FIP-2 | Enabling delegation of fuse tokens to validators             | Done                                                   |
| FIP-3 | Lowering the stake to run a validator node to 100K Ecrox     | Done                                                   |
| FIP-4 | Multi validators, validators can run multiple nodes          | Undone                                                 |
| FIP-5 | Validators key splitting, validator will have separated keys | Undone                                                 |
| FIP-6 | Bridge implementation should be changeable by voting         | Undone                                                 |
| FIP-7 | Tiny Ethereum Network transactions on end of cycle           | Undone                                                 |
| FIP-8 | Adjusting Block Rewards by the Validator's Stake             | [Done](https://github.com/fuseio/fuse-network/pull/61) |


---

# 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://docs.ecroxscan.com/general-1/network-details/network-upgrades/fips.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.