> 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.md).

# Airdrop Gain

The Airdrop Gain vault is designed to maximize your airdrops through a dual strategy: Earning Layer 2 (L2) airdrops and accessing mainnet DeFi opportunities. Here’s how it works:

1. Deposit Assets:

* You deposit one or more of the following assets into the Airdrop Gain vault:
  * ETH
  * stETH (Lido’s LST)
  * ETHx (Stader’s LST)
  * rsETH (Kelp’s LRT)
* The vault receives these assets and processes them for further steps.

2. Issuance of Liquid Tokens:

* Upon depositing, the vault issues a liquid token agETH that represents a claim on the deposited assets. This is an ERC-20 token which is a tradable and usable representation of your staked assets within the vault.

3. Airdrop Optimization:

* The deposited assets are then bridged to partner L2 networks. This bridging allows the assets to be used in L2 ecosystems, which are eligible for various airdrop opportunities.

4. DeFi Deployment:

* Using agETH, the issued liquid token, you deploy them into Pendle, a protocol for DeFi yields on the mainnet.
* Pendle allows you to earn additional yields on your liquid tokens by participating in its DeFi protocols. This adds another layer of potential profit beyond the airdrop benefits.

## **Withdrawals**

Users can withdraw assets using the Gain dApp. Follow these steps:

1. Go to 'Withdraw' section and enter the amount of agETH you want to withdraw
2. Click on the 'Withdraw' button to initiate a wallet approval
3. Once approved, your withdrawal request will be placed. The same can be checked under the 'Claim' section.
4. In 5-7 days, your assets with be transferred to your wallet address.

Note:

* Assets can be withdrawn only as rsETH
* All the withdrawal requests that you place within a day will be clubbed together and will be available as a single claim transaction

## **Vault Partners:**

1. Strategy Partner: K3 Capital
2. Infra Partner: August
3. DeFi: Pendle, Balancer, Uniswap

## **Technical Details:**

### Smart contracts:

1. [ERC-4626 vault](https://etherscan.io/address/0xe1B4d34E8754600962Cd944B535180Bd758E6c2e/)
2. [LRT Adaptor contract](https://etherscan.io/address/0xdabc97cb4eef6fe685ca1c82429d127998c95cca#code)

### Audits:

Comprehensive audit reports can be accessed [here](https://docs.augustdigital.io/smart-contracts/risks-and-audits).\
Airdrop Gain has been thoroughly reviewed by leading firms, including **Zellic, Sigma, and ChainSecurity.**

### Disclaimer:

Read the detailed disclaimer [here](https://docs.google.com/document/d/1KnAvqWDWXr-GpU3c1g_CtQU6y1fpxX9oaGRcrx4lcWQ/edit)


---

# 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://kerneldao.gitbook.io/kernel/getting-started/gain/airdrop-gain.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.
