> For the complete documentation index, see [llms.txt](https://docs.cheqd.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheqd.io/product/learning-docs/governance/advanced/cheq-erc20/gravity-bridge.md).

# What is the Gravity Bridge?

![Gravity Image](/files/abl3Ufr0aMY67HV76MCA)

The Gravity Bridge is a trustless, neutral bridge between the Ethereum and Cosmos ecosystems built by the [Althea](https://www.althea.net/) team. Built using the Cosmos SDK, it uses the validator set to sign transactions instead of a multi-sig or permissioned set of actors.

The neutrality here implies that the entire focus of the Gravity community is on providing the most effective and secure bridge possible instead of on a DeFi application on the local chain. This neutrality aggregates volume from a number of blockchains and sources, increasing efficiency and lowering costs. All control over the bridge is handled entirely by the Gravity Bridge validator set.

The Gravity Bridge has two defined components:

1. A [Solidity contract on Ethereum](https://github.com/Gravity-Bridge/Gravity-Bridge/blob/main/solidity/contracts/contract-explanation.md)
2. A [Cosmos SDK module](https://github.com/Gravity-Bridge/Gravity-Bridge/tree/main/module/x/gravity/spec) on the Gravity Bridge blockchain

The way Gravity Bridge works is similar to how all cross-chain bridges work, i.e. locking up a native token on one side of the bridge and minting a representation of that token on the other. The user then uses this representation before it is returned to the bridge and redeemed for the native asset on the other chain.

The most critical component for bridges to and from Ethereum is the Solidity contract. It holds the native assets being sent across the bridge.

[Gravity.sol](https://github.com/Gravity-Bridge/Gravity-Bridge/blob/main/solidity/contracts/Gravity.sol), the Solidity contract developed by the [Althea](https://www.althea.net/) team, holds funds for Gravity Bridge on Ethereum. In contrast to the prevailing trend in other bridge designs, at a mere 580 lines of code, Gravity.sol is compact and easy to review.

It has been audited by three independent teams ([Informal](https://informal.systems/), [Least Authority](https://leastauthority.com/), and [Code4rena](https://code4rena.com/)), and it is not upgradable, meaning that auditors found it cannot be tampered with by any malicious actor and does not contain any trusted parties of any kind.

To interact with Gravity Bridge, head to[SpaceStation.zone](https://spacestation.zone/) (supported by [Cosmostation](https://www.cosmostation.io/)), where you can connect your [MetaMask](https://metamask.io/) and[Keplr wallet](https://www.keplr.app/).

If you want to learn more, hear from the[Gravity team themselves here](https://blog.cosmos.network/gravity-is-an-essential-force-of-the-cosmos-aligning-all-planets-in-orbits-in-the-composable-b1ca17de18cc) or head over to the [Gravity Docs](https://github.com/Gravity-Bridge/Gravity-Bridge).


---

# 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.cheqd.io/product/learning-docs/governance/advanced/cheq-erc20/gravity-bridge.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.