> 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/legacy-alpha-mainnet-l2/alpha-g-fast-bridge.md).

# Alpha G Fast Bridge Contracts

Verified contract addresses for the G-only fast bridge from Gravity Alpha Mainnet to Ethereum.

This bridge moves **native G from Gravity Alpha Mainnet (L2, chain ID 1625) to Ethereum mainnet (chain ID 1)**. Gravity Mainnet L1 (chain ID 127001) is a separate network.

The Alpha escrow holds the deposited G and sends a LayerZero message. The Ethereum minter mints the same amount to the recipient after message verification. Operators later withdraw the escrowed G through the canonical bridge to the fixed BurnSink and burn it. The canonical withdrawal and claim process remains separate from fast message delivery.

## Bridge contracts

All three contracts below have verified source code on their respective explorers. Deployment and verification records are available in the [bridge repository](https://github.com/Galxe/alpha-g-bridge/tree/main/docs/deployments/2026-09-20/execution-archive).

| Contract        | Network (chain ID)   | Verified address                                                                                                                           | Role                                                             |
| --------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
| AlphaGEscrow    | Gravity Alpha (1625) | [0x8412Fe9ae34Ca66c140E950927591ee8dc09a235](https://explorer.gravity.xyz/address/0x8412Fe9ae34Ca66c140E950927591ee8dc09a235?tab=contract) | Holds deposited native G and sends the mint message to Ethereum. |
| EthereumGMinter | Ethereum (1)         | [0x7b7fDA78d7C262b5Eff124dB57D3434F1f3bFFD8](https://etherscan.io/address/0x7b7fDA78d7C262b5Eff124dB57D3434F1f3bFFD8#code)                 | Mints Ethereum G after verifying the Alpha message.              |
| GBurnSink       | Ethereum (1)         | [0x6Ba324f1B84c9973249D0cf7B87Aca396164a04e](https://etherscan.io/address/0x6Ba324f1B84c9973249D0cf7B87Aca396164a04e#code)                 | Receives canonical withdrawals for subsequent burning.           |

## Ownership

| Safe          | Network              | Address                                                                                                                       | Owns                                                                        |
| ------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Alpha Safe    | Gravity Alpha (1625) | [0x4B08D07c2C7CE01f3666D10AF7d7c6080ECcb1FE](https://explorer.gravity.xyz/address/0x4B08D07c2C7CE01f3666D10AF7d7c6080ECcb1FE) | AlphaGEscrow; also its LayerZero delegate                                   |
| Ethereum Safe | Ethereum (1)         | [0xbD6e434dB90FD8AD4E28d85C133AD34cA6fbfB6D](https://etherscan.io/address/0xbD6e434dB90FD8AD4E28d85C133AD34cA6fbfB6D)         | EthereumGMinter, GBurnSink and GToken; also the minter's LayerZero delegate |

## Token and messaging contracts

| Contract             | Network                         | Address                                                                                                                                    |
| -------------------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| GToken (G ERC-20)    | Ethereum (1)                    | [0x9C7BEBa8F6eF6643aBd725e45a4E8387eF260649](https://etherscan.io/address/0x9C7BEBa8F6eF6643aBd725e45a4E8387eF260649#code)                 |
| LayerZero EndpointV2 | Gravity Alpha (1625), EID 30294 | [0x1a44076050125825900e736c501f859c50fE728c](https://explorer.gravity.xyz/address/0x1a44076050125825900e736c501f859c50fE728c?tab=contract) |
| LayerZero EndpointV2 | Ethereum (1), EID 30101         | [0x1a44076050125825900e736c501f859c50fE728c](https://etherscan.io/address/0x1a44076050125825900e736c501f859c50fE728c#code)                 |
| Send library         | Gravity Alpha (1625)            | [0xe1844c5D63a9543023008D332Bd3d2e6f1FE1043](https://explorer.gravity.xyz/address/0xe1844c5D63a9543023008D332Bd3d2e6f1FE1043?tab=contract) |
| Receive library      | Ethereum (1)                    | [0xc02Ab410f0734EFa3F14628780e6e695156024C2](https://etherscan.io/address/0xc02Ab410f0734EFa3F14628780e6e695156024C2#code)                 |
| Executor             | Gravity Alpha (1625)            | [0xcCE466a522984415bC91338c232d98869193D46e](https://explorer.gravity.xyz/address/0xcCE466a522984415bC91338c232d98869193D46e?tab=contract) |

G is the native asset on Alpha; there is no ERC-20 approval step for depositing native G. The full per-chain DVN addresses and messaging parameters are maintained in the [mainnet configuration](https://github.com/Galxe/alpha-g-bridge/blob/main/config/mainnet-config.json).

## Required DVNs

The configured pathway requires all four DVNs on each side. These are chain-specific verifier addresses.

| Network              | DVN address                                                                                                                   |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Gravity Alpha (1625) | [0x4b92BC2A7d681bf5230472C80d92aCFE9A6b9435](https://explorer.gravity.xyz/address/0x4b92BC2A7d681bf5230472C80d92aCFE9A6b9435) |
| Gravity Alpha (1625) | [0x9C061c9A4782294eeF65ef28Cb88233A987F4bdD](https://explorer.gravity.xyz/address/0x9C061c9A4782294eeF65ef28Cb88233A987F4bdD) |
| Gravity Alpha (1625) | [0xe95B63C4dA1D94fa5022e7C23c984F278B416ca7](https://explorer.gravity.xyz/address/0xe95B63C4dA1D94fa5022e7C23c984F278B416ca7) |
| Gravity Alpha (1625) | [0xe9C24dD582e37FAACa7d44c799530688DE92Da73](https://explorer.gravity.xyz/address/0xe9C24dD582e37FAACa7d44c799530688DE92Da73) |
| Ethereum (1)         | [0x380275805876Ff19055EA900CDb2B46a94ecF20D](https://etherscan.io/address/0x380275805876Ff19055EA900CDb2B46a94ecF20D)         |
| Ethereum (1)         | [0x589dEDbD617e0CBcB916A9223F4d1300c294236b](https://etherscan.io/address/0x589dEDbD617e0CBcB916A9223F4d1300c294236b)         |
| Ethereum (1)         | [0xa4fE5A5B9A846458a70Cd0748228aED3bF65c2cd](https://etherscan.io/address/0xa4fE5A5B9A846458a70Cd0748228aED3bF65c2cd)         |
| Ethereum (1)         | [0xa59BA433ac34D2927232918Ef5B2eaAfcF130BA5](https://etherscan.io/address/0xa59BA433ac34D2927232918Ef5B2eaAfcF130BA5)         |

## Canonical settlement contracts

| Contract         | Network              | Address                                                                                                                       |
| ---------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| ArbSys           | Gravity Alpha (1625) | [0x0000000000000000000000000000000000000064](https://explorer.gravity.xyz/address/0x0000000000000000000000000000000000000064) |
| Canonical bridge | Ethereum (1)         | [0x7983403dDA368AA7d67145a9b81c5c517F364c42](https://etherscan.io/address/0x7983403dDA368AA7d67145a9b81c5c517F364c42#code)    |
| Outbox           | Ethereum (1)         | [0x1153a1e4B1523DFf36f77d696bd6eBF2B0e7DAbF](https://etherscan.io/address/0x1153a1e4B1523DFf36f77d696bd6eBF2B0e7DAbF#code)    |
| Rollup           | Ethereum (1)         | [0x2807B1d5d94ca823ca7d8642A5F5DDac120ce48f](https://etherscan.io/address/0x2807B1d5d94ca823ca7d8642A5F5DDac120ce48f#code)    |

Addresses and ownership were checked on September 20, 2026. The rollup address was read from the canonical bridge's `rollup()` getter. Permissions, limits and messaging configuration can change; query current state before operating.

## Using these addresses

* Deposit through the bridge's `bridge(recipient, amount)` call with its quoted message fee. Do not send tokens or native G directly to the listed addresses.
* BurnSink has no transfer or recovery function. It is a settlement destination, not a user deposit address.
* A source-chain deposit does not prove Ethereum delivery. Check the original GUID's mint result; retry the original verified message if execution failed, without depositing again.
* The fast bridge supports G only. For other assets and the canonical user withdrawal route, see [Bridge Assets back to Ethereum](/legacy-alpha-mainnet-l2/bridge-back-to-ethereum.md).


---

# 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://docs.gravity.xyz/legacy-alpha-mainnet-l2/alpha-g-fast-bridge.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.