> For the complete documentation index, see [llms.txt](https://kerneldao.gitbook.io/kernel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerneldao.gitbook.io/kernel/getting-started/gain/airdrop-gain/faqs.md).

# FAQs

## FAQs

1. What is Gain? \
   Gain is our latest product offering designed to help restakers and users maximize their rewards. It will feature multiple vaults based on smart contracts.
2. How does Gain work? \
   Gain is a collection of vaults. The vaults are smart contracts that automate reward farming opportunities and strategies. Kelp’s vaults are non-custodial, allowing users to withdraw at any time while providing complete transparency regarding the deployment of their tokens.
3. How does Airdrop Gain work?

   It is a simple process: - You deposit ETH/ETH LSTs/rsETH to the vault - Liquid token (agETH) is issued against the deposited assets - Deposited assets are deployed into different strategies like liquidity provisioning, leverage looping etc. and earns rewards that are fed back into the vault to increase the exchange rate of agETH
4. What does the redemption/withdrawal process look like? How long does it take and what asset can I get in return?

   Withdrawal and claim take 5-7 days. Users can withdraw their agETH as rsETH from the Gain dApp


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kerneldao.gitbook.io/kernel/getting-started/gain/airdrop-gain/faqs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.