RPC, refresh and pending transactions
Resolve read-node failures and rate limits without deleting RPC settings or resending a transaction that may already be on-chain.
Content reviewed: · Documented version: v1.1.12 · Source code
What happens when a read node fails?
Configured RPC endpoints serve list reads, displays and preparation estimates. The app validates HTTPS and the chain ID for saved endpoints and uses healthy nodes. Wallet authorization and sending remain with the injected wallet.
An RPC failure can be caused by the provider or by local connectivity, DNS, a firewall or a proxy/VPN. Check connectivity and retry the health check, or change the RPC settings manually. The app does not delete the configured list when nodes become unavailable. Do not put credentials in an RPC URL.
What does the rate-limit warning mean?
A provider may return HTTP 429 or a JSON-RPC rate-limit error. When a usable Retry-After value is available, the message can show a bounded wait. Without it, including when browser CORS rules hide the header, the app uses a general rate-limit message rather than inventing a server countdown.
Wait before retrying and avoid repeatedly refreshing. A successful node health probe does not guarantee that later contract reads will succeed or that a public endpoint has unlimited capacity.
Why is my old list still visible?
After a failed full refresh, the last successful list can remain visible with an outdated-data warning. It is read-only: operations are blocked until a full refresh succeeds. Background refreshes may invalidate a preparation that has not opened a wallet request.
A refresh clears list selection. Recheck the refreshed data before selecting VMUs again. A refresh does not cancel an already opened wallet request or reverse an already broadcast transaction.
A transaction is pending or confirmation timed out
Do not resend solely because confirmation stopped or timed out. Check the pending panel, wallet activity and the correct chain's explorer. The application retains unresolved records and relevant locks to reduce duplicate submissions.
Closing a dialog or cancelling local preparation does not undo a transaction already broadcast. Wallet replacement or cancellation is a separate on-chain action and can itself cost gas.