# Redelegating & Signalling Intent

### Signalling Intent Overview

**Signalling Intent** is a core feature of the Quicksilver protocol that empowers delegators to specify which validators should receive their stake. By collecting these individual “Intents” from all users, Quicksilver can accurately align staking distributions with the community’s preferences while maintaining **user sovereignty**.

***

### Initial Deposit

When a user makes a **first-time deposit** to Quicksilver:

1. **Validator Selection**
   * Users can select **up to 8 validators** on the target chain to delegate their stake.
   * They can choose **equal stake** distribution (automatically dividing the stake equally across the chosen validators) or **custom allocations** (assigning specific percentages to each validator).
2. **LSM Integration**
   * If depositing from an **existing delegation** using **Liquid Staking Module (LSM)**, Quicksilver adopts the composition of that pre-existing delegation as the user’s **initial Intent**.

This initial configuration forms the baseline preferences for where a user’s stake should be allocated—referred to as the **Intent**.

***

### Further Deposits

When a user makes **subsequent deposits**, they can again specify validator preferences. However, these preferences only apply to the **newly deposited amount**. Quicksilver then blends the existing Intent with the newly stated one:

$$
Overall Intent=(Existing Intent×Existing Delegation Weight)+(New Intent×New Delegation Weight)
$$

This ensures every deposit updates a delegator’s total Intent in proportion to the amount deposited.

***

### Changing Signal

Delegators can adjust their validator preferences at any time by submitting a **`MsgSignalIntent`** transaction on the Quicksilver chain. Key points to remember:

* The updated Intent applies to the **entire weight** of the user’s delegated stake (not just the new deposit).
* By issuing this message, the user effectively signals that they wish to reallocate existing delegations to new validators or adjust allocations among current validators.

***

### Epochly Rebalancing

Quicksilver performs **rebalancing** at regular intervals (known as **epochs**, typically every 3 days). During this process:

1. **Aggregate Intent Calculation**
   * The protocol aggregates all users’ Intents for a specific chain, creating a collective picture of the **preferred validator set** and allocation.
2. **Redelegations**
   * Quicksilver initiates redelegation transactions to align actual staking distribution with the aggregate Intent.
   * **Concurrent Redelegation Constraints**: Cosmos PoS imposes limits on how many redelegations can happen at once.
3. **Eventual Consistency**
   * Rebalancing may take up to **one unbonding period** (14–28 days) to fully converge on the desired distribution.
   * Quicksilver gradually moves delegations over time to comply with user preferences without violating chain-level redelegation constraints.

***

### Limitations

1. **Concurrent Redelegation Limits**
   * Cosmos consensus limits the number of simultaneous redelegations per validator, so rebalancing must proceed **incrementally**.
2. **Extended Completion Window**
   * Achieving complete alignment with the aggregate Intent can take **up to an unbonding period** (14–28 days) due to these redelegation constraints.
3. **Moving Target**
   * Because new deposits and changing signals can occur at any time, the aggregate Intent itself is **dynamic**, meaning the “perfect” distribution is continuously evolving.

***

### Key Takeaways

* **User Autonomy**: Delegators keep full control of how their stake is allocated, reflecting both initial deposits and any subsequent changes.
* **Responsive Protocol**: Quicksilver collects Intents, aggregates them each epoch, and steadily redelegates funds to align with evolving user preferences.
* **Decentralized Staking**: By encouraging users to select various validators, Quicksilver supports broader validator participation and robust network security.

Through Signalling Intent, Quicksilver strikes a balance between **flexible user choice** and **orderly, protocol-driven rebalancing**, ensuring staking decisions reflect the collective will of the Cosmos community without sacrificing sovereignty or security.


---

# 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.quicksilver.zone/protocol/redelegating-and-signalling-intent.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.