# Chiliz Chain Changelog

Chiliz Chain is not set in stone! There are several ways for it to evolve, improve, and keep up with the times.

## Governance Proposals & Decisions

The Chiliz Chain governance relies on a system of validators, with the Proof-of-Staked Authority (PoSA) consensus mechanism.

Since the inception of Chiliz Chain’s, several decisions have been applied to it through the governance body.

You can see the full list of decisions on the [Chiliz Chain Governance page](https://governance.chilizchain.com/governance), including the addition of validators and previous white-listings.

You can access the full list of proposals and decisions on the page below:

{% content-ref url="/pages/jEEQKFV3Lmxznc7tFuo8" %}
[Governance Proposals & Decisions](/chiliz-chain-changelog/governance-proposals-and-decisions.md)
{% endcontent-ref %}

## Blockchain code changes

The code of Chiliz Chain itself is always evolving, with bug fixes , new features, etc.

You can see the list of evolutions on the page below:

{% content-ref url="/pages/Hk49aR6qVOuSpfuHb4h2" %}
[Blockchain code changes](/chiliz-chain-changelog/blockchain-code-changes.md)
{% endcontent-ref %}

## Outage reports

Chiliz Chain maintains a high level of availability for our ecosystem.\
That being said, software inevitably comes with scheduled maintenance... and unexpected outages.

For transparency, we have a dedicated Outage Reports page listing the major outages that happened:

{% content-ref url="/pages/OwGKgCITESgMsONbw7oq" %}
[Outage reports](/chiliz-chain-changelog/outage-reports.md)
{% endcontent-ref %}

The status page for all Chiliz services is here:

{% embed url="<https://status.chiliz.com/>" %}


---

# Agent Instructions: 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:

```
GET https://docs.chiliz.com/chiliz-chain-changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.