> For the complete documentation index, see [llms.txt](https://docs.gravityblocks.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gravityblocks.xyz/introduction.md). # Introduction > **Gravity is an open and competitive marketplace for Solana blockspace** Validators supply blockspace; users, applications, and traders create demand for inclusion and ordering; and builders compete to allocate that capacity optimally by selecting and ordering transactions. Competition rewards the builders that allocate blockspace most effectively, creating continuous pressure to increase validator rewards and make sequencing more predictable for users. Gravity is the aggregation layer that connects validators to a competitive builder market and coordinates competition among block builders. ## Why Gravity * **Higher validator rewards** through competitive auctions between independent block builders * **Efficient, low-latency block production** by moving simulation and sequencing off the validator’s critical path * **More predictable execution for traders** through fast, consistent, value-based priority * **Neutrality:** Gravity does not trade or otherwise search onchain, thus reducing conflicts of interest * **Faster innovation** without protocol changes or validator-client release cycles * **Validator control and flexibility** through configurable policies, detailed observability, and native scheduler fallback --- # 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.gravityblocks.xyz/introduction.md?ask=&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.