> For the complete documentation index, see [llms.txt](https://docs.gravity.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gravity.xyz/the-g-token/how-to-get-g.md). # How to Get G You need native G on Gravity L1 to pay gas, stake, or participate in governance. This page covers the three realistic routes: the **canonical bridge from Ethereum**, **direct withdrawals from centralized exchanges**, and **migration from Alpha Mainnet (L2)**. {% hint style="info" %} This page is the L1 view. The Alpha Mainnet (L2) bridging guide is preserved at [How to Get G (Gravity Alpha, L2)](/legacy-alpha-mainnet-l2/bridge-to-gravity.md) and remains valid for anyone still using L2. {% endhint %} ## Option 1: Canonical bridge from Ethereum The canonical bridge locks ERC-20 G on Ethereum and issues native G on Gravity L1 at a 1:1 ratio. End-to-end takes a few minutes once the Ethereum transaction is confirmed. The bridge consists of two contracts on Ethereum — `GravityPortal` (the generic message outbox) and `GBridgeSender` (which locks the user's G ERC-20 and forwards the bridge message to the Portal) — paired with the `GBridgeReceiver` contract on Gravity L1 (deployed at genesis) that mints native G once the consensus engine relays the verified message through the native oracle. Contract addresses are listed in [Gravity Mainnet (L1) Contracts](/developer-resources/mainnet.md#cross-chain-bridge). At launch, the bridge is one-way — Ethereum → Gravity L1; bridging native G back to Ethereum is on the roadmap. {% hint style="info" %} **Bridge UI:** The unified [Get G portal](https://bridge.gravity.xyz/) at `bridge.gravity.xyz` is the single entry point for bridging G to Gravity. See the [Get G One Portal](https://gravity.xyz/blog/get-g-one-portal-every-option-to-acquire-g-tokens) announcement for all options. {% endhint %} ### Step-by-step 1. Hold G as ERC-20 on Ethereum at [`0x9C7BEBa8F6eF6643aBd725e45a4E8387eF260649`](https://etherscan.io/token/0x9C7BEBa8F6eF6643aBd725e45a4E8387eF260649) (buy on a CEX, on Uniswap, etc.). 2. Open the canonical bridge UI (see the box above) and connect your wallet. 3. Approve the bridge contract to spend your G. 4. Send the bridge transaction, paying the ETH bridge fee on Ethereum. 5. Wait for the bridge to relay your message to L1; native G arrives at your recipient address shortly after Ethereum finality. ## Option 2: Centralized exchanges G is currently listed on Binance, OKX, Bitget, KuCoin, MEXC, and BitMart, with deposits and withdrawals available on Ethereum (and on Mantle L2 on some). Once an exchange adds direct Gravity L1 support, you can withdraw native G to your L1 address in a single step. Until then, withdraw G as ERC-20 to Ethereum and follow **Option 1** to bridge in. Confirm the network the exchange uses — L1 vs Ethereum vs Alpha Mainnet (L2) — before withdrawing. For the up-to-date exchange list, see [CoinMarketCap](https://coinmarketcap.com/currencies/gravity-token/), [CoinGecko](https://www.coingecko.com/en/coins/gravity), or the [Get G portal announcement (April 2025)](https://gravity.xyz/blog/get-g-one-portal-every-option-to-acquire-g-tokens). ## Option 3: Migrate from Alpha Mainnet (L2) to L1 If you hold native G on Alpha Mainnet (L2, Chain ID `1625`): 1. Use the [L2 canonical bridge](https://bridge.gravity.xyz/) to withdraw your G back to Ethereum. The L2 rollup's optimistic-challenge period means this leg takes \~7 days. 2. Once the G ERC-20 is back on Ethereum, follow **Option 1** above to bridge into L1. Direct L2-to-L1 routing may be added through third-party aggregators; check current options at [Jumper](https://jumper.exchange/) or [Symbiosis](https://app.symbiosis.finance/) when L1 is listed. ## Other ways to acquire G * **Fiat onramps** — Buy G with credit card, bank transfer, or local payment methods through [Onramp.money](https://onramp.money/) or [Alchemy Pay](https://ramp.alchemypay.org/). These currently deliver G ERC-20; bridge to L1 using **Option 1**. * **Cross-chain aggregators** — [LI.FI](https://li.fi/) supports moving G across 37+ networks; once L1 is a routing destination, you can bridge from any supported source chain in a single transaction. ## After you have G on L1 * Add the network to your wallet — see [Gravity Mainnet (L1)](/gravity-networks/l1-mainnet.md). * Stake or delegate — see [G Token](/the-g-token/g-token.md#g-utilities). * Explore the ecosystem — see [Wallets & Exchanges](/ecosystem-infrastructures/supported-wallets.md) and [Cross-chain Interoperability](/ecosystem-infrastructures/cross-chain-interoperability.md). ## See also * [G Token](/the-g-token/g-token.md) — token overview and utilities. * [Token Contracts on Gravity](/the-g-token/token-contracts.md) — L1 ERC-20 list (wG, USDT, USDC, …). * [How to Get Test Tokens](/the-g-token/how-to-get-test-tokens.md) — for the Longevity Testnet (L1). --- # 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.gravity.xyz/the-g-token/how-to-get-g.md?ask=&goal= ``` `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.