> For the complete documentation index, see [llms.txt](https://docs.libertyswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.libertyswap.finance/how-to/use-railway-wallet/rpc-configuration.md).

# RPC Configuration

When using the Shield feature in Liberty Swap, RPC configuration plays a critical role in execution reliability.

Shield operations require frequent state queries and additional processing compared to standard transactions. As a result, default public RPC endpoints may not provide sufficient performance.

### Recommended Setup

For a stable experience, it is recommended to use a dedicated RPC endpoint instead of the default wallet configuration.

You can configure a custom RPC from providers such as:

* Alchemy
* Infura
* Chainstack

These services provide API-based endpoints with higher throughput and more reliable request handling.

### Common Issues with Default RPC

Using shared or public RPC endpoints may result in:

* transactions remaining pending
* delayed confirmations
* failed Shield operations

These issues are typically caused by RPC limitations rather than the protocol itself.

### Resolution

Switching to a dedicated RPC endpoint can significantly improve performance and resolve most execution issues.

Once configured, no additional changes are required within the Liberty Swap interface.

### Notes

* RPC settings are managed within Railway Wallet
* A custom RPC can be added or updated at any time
* No additional configuration is required after setup


---

# 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.libertyswap.finance/how-to/use-railway-wallet/rpc-configuration.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.