> For the complete documentation index, see [llms.txt](https://docs.novarpc.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novarpc.xyz/nova-rpc/key-features.md). # Key Features Best Inclusion: Nova optimizes for latency, fee precision, and MEV protection to reduce inclusion uncertainty and deliver the strongest possible outcome for every transaction * **Industry Leading Refunds:** Real-time gas optimization means you won't overpay, whilst always meeting your inclusion goals. This means we can refund more on average than industry peers. * **MEV Protection and Capture:** Industry leading searchers are vetted to facilitate protection from front-running and sandwiching, and value capture from back-running opportunities (optional). * **Reduced Latency:** Private mempool operators typically act as middlemen, introducing an extra step in the transaction lifecycle between originators and block builders. Nova co-locates with a leading block builder to minimize inclusion latency. * **Enhanced Privacy:** Active monitoring of builder behaviour means transactions are only shared with Nova's trusted builder network. * **Avoid Failed Transactions:** Transactions are only included in a block if they do not revert, protecting users from costs associated with failed transactions (optional). * **Real-Time Analytics:** Easy to analyse statistics on revenue generated and inclusion. \ **Transaction API:** offers detailed status reports on transactions sent to Nova. For more information please see **Real-Time Analytics Dashboard:** --- # 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.novarpc.xyz/nova-rpc/key-features.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.