# 🧲 Validator directed stake (/validators/validator-directed-stake)







The Vault lets you choose which validator your [vSOL](/about/vsol) supports through [direct staking](/stake/direct-staking).

<img alt="Banner: A validator operator welcomes a staker whose orange path leads from a cream wallet directly to their server tower." src="__img0" />

* With Automatic delegation selected, your vSOL contributes to [undirected stake](/stake/direct-vs-undirected-stake), which is allocated among gauges and the two approved-validator buckets.
* Alternatively, choose a specific validator and set your wallet to direct stake to it, so all vSOL in that wallet counts toward it. See [How to direct stake](/stake/how-to-direct-stake).

## Engaging communities [#engaging-communities]

Validator communities are encouraged to share their validator-directed stake page with their members to maximize stake support.

## Tracking your directed stake [#tracking-your-directed-stake]

Your vSOL counts while held in the wallet you set to the validator or in a supported integration. Connect that wallet on the [Direct Stake page](https://thevault.finance/direct-stake) and check Your vSOL holdings for the positions currently tracked. See [What counts as direct stake](/delegation/direct-stake-leaders-bucket#what-counts-as-direct-stake).

<Callout type="info">
  Moving vSOL to an unsupported location stops that position from counting toward the wallet's direct stake. It contributes to undirected stake until it is tracked in a supported location again.
</Callout>

## Redelegation on return [#redelegation-on-return]

Returning vSOL to the configured wallet or a supported position lets it count again after the holdings refresh, which can take about 24 hours. The stakebot then moves stake over subsequent epochs; completion in the very next epoch is not guaranteed (Figure 16.8).

<img alt="Tracked wallet and integration holdings count toward directed stake. Unsupported holdings stop counting. Returning to a supported location restores tracking after the data refresh; stake movement follows over subsequent epochs." src="__img1" />

Figure 16.8: How directed stake stays tracked