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