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

# Airdrop

## Airdrop Closed

The initial Arkeo airdrop period has officially ended. All previously allocated but unclaimed tokens have been returned to the Arkeo network reserve. We thank everyone for their participation and support.

## Original Airdrop Distribution (for reference)

The initial airdrop of ARKEO tokens was distributed among a broad variety of communities to encourage diverse participation in the Arkeo network.

## Original Claiming Process (now closed)

Users were required to take multiple actions to receive their full airdrop allocation:

* 1/3 was sent upon initial claim.
* 1/3 was sent after delegating Arkeo tokens to a validator.
* 1/3 was sent after participating in governance.

Ethereum users claimed their tokens by transferring from their designated Ethereum address to their Arkeo address via a signed message.

Eligible Arkeo native addresses were provided a small amount of ARKEO at genesis to cover the gas fees necessary to claim their tokens.

To incentivize timely claims, the claimable airdrop amount reduced over time:

* Full amount claimable for the first month (`DurationUntilDecay`).
* Linear decay in the claimable amount from the 1st to the 2nd month (`DurationOfDecay`).
* After two months, unclaimed tokens reverted to the reserve.

## THORChain Users

THORChain's unique BIP-44 coin type (931) required an additional step to transfer allocated tokens from a THORChain-derived address to an Arkeo address. This transfer could only be performed once per claim.

## Continuing Participation

Even though the airdrop has concluded, you can continue to engage with the Arkeo network by:

* Delegating ARKEO tokens to validators.
* Participating in governance proposals.
* Becoming a data provider or subscriber.

We appreciate your continued interest and involvement in the Arkeo community!


---

# 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.arkeo.network/architecture/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.