> For the complete documentation index, see [llms.txt](https://docs.vultisig.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vultisig.com/vult-token/airdrop.md).

# Vultisig $VULT airdrop (concluded)

The $VULT airdrop is concluded. $VULT launched 27 October 2025. Current utility is in-app swap fee discounts.

{% hint style="warning" %}
**Concluded.** The $VULT airdrop is finished. There is no registration, no VULTIES accrual, and no seasonal distribution.

`airdrop.vultisig.com` is not a product surface. Hold $VULT in a vault for [in-app fee discounts](/vult-token/vult/in-app-utility.md).
{% endhint %}

***

## Current $VULT

* **Live** on Uniswap (Ethereum) and Kraken
* Contract: [`0xb788144DF611029C60b859DF47e79B7726C4DEBa`](https://etherscan.io/token/0xb788144df611029c60b859df47e79b7726c4deba)
* Current product utility: [in-app swap fee discounts](/vult-token/vult/in-app-utility.md)
* Token overview: [The $VULT Token](/vult-token/vult.md)
* Launch record: [Launch of $VULT](/vult-token/launch.md)

***

## Season 0 (concluded)

Season 0 measured vault value over time. Points were called VULTIES. The published formula was:

$$
vault\_asset\_value \* time\_in\_vault
$$

The published initial allocation was 5,000,000 $VULT, to be distributed after the first year. [Airdrop V2](/vult-token/airdrop/airdrop-v2.md) described the seasonal design that followed Season 0. That program is concluded.

Users registered by sending vault public keys (via Vault QR) to an airdrop registry, which scanned balances daily. That path is closed.

***

## Related

* [$VULT in-app fee discounts](/vult-token/vult/in-app-utility.md)
* [The $VULT Token](/vult-token/vult.md)
* [Launch of $VULT](/vult-token/launch.md)


---

# 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.vultisig.com/vult-token/airdrop.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.