> For the complete documentation index, see [llms.txt](https://docs.playongeist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playongeist.com/info/moving-funds-to-geist/native-token-ghst.md).

# Native Token (GHST)

There are currently two main ways to get GHST onto Geist:

* For small amounts, refill services like smolrefuel and gas.zip are fast and convenient.
* For larger amounts, the canonical Base Bridge is the best choice. 

## For Small Amounts - Refuel Services

[Smolrefuel](https://smolrefuel.com/?outboundChain=63157) and [gas.zip](https://www.gas.zip/) both support topping up GHST natively on Geist. Simply visit these dapps, connect your wallet, and transfer funds in from Ethereum, Base, or Polygon. 

These services are best for bridging small amounts, as they natively swap tokens and may incur slippage for large amounts. 

## For Large Amounts - Canonical Base Bridge

Geist settles to Base, which means it's easy to transfer funds back and forth between Base and Geist without incurring slippage. 

To bridge from Base to Geist, ensure you have GHST in your wallet on Base, and then visit the official [Base Bridge](https://bridge.arbitrum.io/?destinationChain=geist-mainnet\&sourceChain=base), powered by Arbitrum. 

<figure><img src="/files/SYkEBHQ0gwyWyFGDs7Kk" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://docs.playongeist.com/info/moving-funds-to-geist/native-token-ghst.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.