> For the complete documentation index, see [llms.txt](https://node1.gitbook.io/node1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node1.gitbook.io/node1-docs/solana/fast-landing/optimization.md). # Transaction optimization ## Transaction Optimization Strategy ### 1. Choose the nearest endpoint All available nodes are centrally maintained in the [Endpoints and tip addresses](/node1-docs/solana/fast-landing/endpoints.md) document. To minimize synchronization overhead, please directly reference this page in your deployment scripts or configuration files, or maintain only a single link to it in your internal wiki. For optimal performance, always select the node closest to your end-users or cluster and regularly perform health checks to validate latency. ### 2. Optimize tip amount Tip size directly affects transaction priority: * Minimum tip: 0.001 SOL * Node1 applies a tip-amount-based prioritization policy. Requests are ranked by the tip amount provided. Higher tip amount leads to higher priority and faster landing speed. ### 3. Connection optimization * Use persistent HTTP connections * Enable connection reuse * Configure reasonable timeouts * Send a ping every 30 seconds --- # 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://node1.gitbook.io/node1-docs/solana/fast-landing/optimization.md?ask=&goal= ``` `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.