# Redenomination of ACA

Effective on April 6 2021, the total fixed supply of (new) ACA will increase 10 times to 1,000,000,000. ACA token distribution and token economics remain the same.

Acala chain is not live, so ACA redenomination does NOT have any impact on anyone, therefore this is for your information only.

Key Points for the redenomination:

* The total fixed supply of (old) ACA in the [whitepaper](https://github.com/AcalaNetwork/Acala-white-paper/blob/master/Acala_Whitepaper.pdf) is 100,000,000.&#x20;
* After 10x redenomination, the total fixed supply of (new) ACA will increase 10 times to 1,000,000,000.&#x20;
* ACA balances will increase by a factor of 10.&#x20;
* The distribution of ACA does NOT change, and holders of ACA still own an equal share of the network as before the change. ACA token economics also does NOT change.
  * As an example, if an account has 1,000,000 (old) ACA that is 1% of the total supply, then after redenomination, the account would still have 1% of the total supply which is 10,000,000 (new) ACA.
* The main benefit of this change similar to the [redenomination of DOT](https://wiki.polkadot.network/docs/en/redenomination) is to avoid using small decimals when dealing with ACA and make calculations easier.
* The main benefit of doing this before mainnet is that redenomination is way simpler before the Acala chain is live, with less confusion and NO impact to users and service providers like exchanges and wallets, etc.&#x20;


---

# 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://wiki.acala.network/learn/acala-introduction/redenomination-of-aca.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.
