> 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/gravity-networks.md).

# Gravity Networks

- [Gravity Mainnet (L1)](https://docs.gravity.xyz/gravity-networks/l1-mainnet.md): Gravity Mainnet (L1) network reference — chain ID, RPC, explorer, bridge.
- [Gravity Mainnet Hardforks](https://docs.gravity.xyz/gravity-networks/mainnet-hardforks.md): Gravity Mainnet (L1) hardfork schedule, required node version, and what happens if a node misses an activation.
- [Run a Gravity Mainnet Public Full Node](https://docs.gravity.xyz/gravity-networks/run-a-mainnet-pfn.md): Run a Gravity Mainnet (L1) Public Full Node. Covers binaries, genesis artifacts, public/VFN seeds, deployment, database warm start, and sync verification for a PFN/RPC endpoint.
- [Run a Gravity Mainnet Public Full Node With Docker](https://docs.gravity.xyz/gravity-networks/run-a-mainnet-pfn-with-docker.md): Run a Gravity Mainnet (L1) Public Full Node with Docker. Covers image preparation, mainnet artifacts, PFN identity generation, pruning, startup, sync checks, and operational cleanup.
- [Run a Gravity Mainnet VFN](https://docs.gravity.xyz/gravity-networks/run-a-mainnet-vfn.md): Run a Gravity Mainnet (L1) Validator Full Node. Covers validator VFN-network seeds, deployment, optional public listener, database warm start, and sync verification.
- [Run a Gravity Mainnet Validator (Invite Only)](https://docs.gravity.xyz/gravity-networks/run-a-mainnet-validator.md): Run an invite-only Gravity Mainnet (L1) validator. Validator onboarding is currently invite-only. Covers validator node deployment, StakePool creation, governance whitelisting, validator join, status
- [Node Operation Anti-Patterns](https://docs.gravity.xyz/gravity-networks/node-operation-anti-patterns.md): Node operation mistakes that cause sync problems on Gravity L1, with the symptoms to look for, why they happen, how to confirm them, and how to fix them.
- [Gravity Longevity Testnet (L1)](https://docs.gravity.xyz/gravity-networks/l1-longevity-testnet.md)
- [Gravity Longevity Testnet Hardforks](https://docs.gravity.xyz/gravity-networks/testnet-hardforks.md): Gravity Longevity Testnet (L1) hardfork schedule, how activations are stored, and the node version needed to follow the live chain.
- [Run a Gravity Testnet Public Full Node](https://docs.gravity.xyz/gravity-networks/run-a-testnet-pfn.md): Run a Gravity Longevity Testnet (L1) Public Full Node. Covers binaries, testnet genesis artifacts, the public-network seed, deployment, database warm start, and sync verification for a PFN/RPC endpoin
- [Run a Gravity Testnet Public Full Node With Docker](https://docs.gravity.xyz/gravity-networks/run-a-testnet-pfn-with-docker.md): Run a Gravity Longevity Testnet (L1) Public Full Node with Docker. Covers image preparation, testnet artifacts, PFN identity generation, pruning, startup, sync checks, and operational cleanup.


---

# 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/gravity-networks.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.