# Validator Rotation and Key Management

In the TON network, validators are rotated every 18 hours as part of the regular consensus mechanism. Since the TON Teleport BTC system relies on validators to generate and manage the distributed key used for signing Bitcoin transactions, the keys must also be updated every 18 hours to ensure consistency and security. This means that the deposit addresses, which are derived from these keys, will also change with each new set of validators.

*Important: In the test network (testnet), validators are rotated every 4 hours. Consequently, deposit addresses are also updated at the same interval.*

Whenever the set of validators changes, a new DKG process is initiated to create a fresh public key. The new key is then used for all subsequent peg-in and peg-out operations. After the DKG process is completed and the new key is established, validators need to consolidate all available UTXOs associated with the previous key and move them to a new address controlled by the new key. This process ensures that all Bitcoin funds are securely managed by the updated set of TON validators and that the old key is no longer in use.

One of the primary concerns during key rotation is the handling of Bitcoin transaction fees. When validators move funds from the old bank address to the new one, there are two approaches for managing transaction fees:

<figure><img src="/files/VVKKliHoTTxyEY93Rnm9" alt=""><figcaption></figcaption></figure>

The decision on whether to implement a zero-fee approach or a dedicated fee mechanism is left to the TON validators, who can decide through consensus. TON validators can adjust the base fee rate, determine the allocation of collected fees, and establish guidelines for handling Bitcoin transaction costs during key rotation. This flexibility ensures that the system can adapt to changes in the Bitcoin network, such as fluctuating fees or changes in miner behavior.

The automatic transition process, including the reallocation of UTXOs and the regeneration of keys, occurs seamlessly, minimizing disruptions to users. Throughout this process, the system’s state remains synchronized, and all ongoing operations continue as expected, maintaining the trustless nature of the system.


---

# 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://tgbtc.gitbook.io/docs/whitepaper/key-concepts/additional-components-and-security-mechanisms/validator-rotation-and-key-management.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.