> For the complete documentation index, see [llms.txt](https://docs.wasabi.xyz/_/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wasabi.xyz/_/overview/technical-documentation/depositor-snapshots.md).

# Depositor Snapshots

Below is a practical workflow to snapshot vault depositors and convert vault-share balances into the underlying token amounts.

#### 1) Export the vault holder list (CSV)

1. Open the vault you want to snapshot on [Wasabi](https://app.wasabi.xyz/earn).
2. Click the Explorer icon to open the vault token contract on the chain explorer.

<figure><img src="/files/wSRQrZdaRhmXOgEJMCEK" alt="" width="375"><figcaption></figcaption></figure>

3. In the explorer:

* Go to Holders

<figure><img src="/files/507A21PfEvQitHjK6nRm" alt="" width="375"><figcaption></figcaption></figure>

* Click CSV Export

<figure><img src="/files/0SsBiwd42FtHkC11ibhW" alt="" width="375"><figcaption></figcaption></figure>

You’ll now have a CSV containing at least:

* HolderAddress (wallet address)
* Balance (the vault token balance, e.g., sTOKEN)

**Important**: this Balance is not the final token amount. It represents vault shares (the vault receipt token), not the underlying token amount.

***

#### 2) Find the current redemption rate (shares → underlying)

To convert vault shares to underlying token amounts, you need the redemption rate (sometimes called share price). The simplest way to derive it is from the most recent deposit or withdraw transaction:

1. Find the most recent deposit/withdraw transaction for the vault (via the explorer / transfers).
2. Identify both values from that transaction:
   * Non-spicy amount = underlying token amount (e.g., BOT)
   * Spicy amount = vault share amount (e.g., sBOT)

<figure><img src="/files/waOIGL3A2WWMCwPJZUJe" alt="" width="375"><figcaption></figcaption></figure>

3. Calculate the remption rate by dividing the non-spicy amount by the spicy amount:

Redemption Rate = Non-spicy amount ÷ Spicy amount

This value should always be > 1 (and will increase over time as rewards accrue).

*In the example above, we calculate 851.496 (BOT) / 833.429 (sBOT) = \~1.0217*

***

#### 3) Convert balances in a sheet (i.e. Google Sheets)

1. Import the CSV into Google Sheets or a program of your choice.
2. Add a new column like TrueBalance.
3. Multiply each wallet’s Balance by the redemption rate.

<figure><img src="/files/SQUSoOyiZE7gY439VNYO" alt="" width="563"><figcaption></figcaption></figure>

Example formula (if Balance is in column B and your redemption rate is 1.0217):

\=B2 \* 1.0217

Drag down to apply it to all rows.

<figure><img src="/files/M1cHLN4gufvQhszrhnQb" alt="" width="375"><figcaption></figcaption></figure>

***

#### Result

You now have:

* HolderAddress (the depositor wallet)
* TrueBalance (estimated underlying token amount at the moment you exported the CSV)

**That’s your depositor snapshot** - a clean, reproducible dataset you can use for rewards, allowlists, or community campaigns.

#### Notes & best practices

* Snapshot is time-based. If deposits/withdrawals happen after export, they won’t be reflected.
* Record the metadata alongside your sheet: vault name, export timestamp, redemption rate used, and the tx hash you sourced it from.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.wasabi.xyz/_/overview/technical-documentation/depositor-snapshots.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.