#RC#
It is common for the interface to lag during periods of intense blockchain network activity. If the MultiCurrencyWallet interface feels sluggish, try changing your RPC node to a faster alternative. To resolve the , many recommend manually bumping the gas fee in the settings. Sometimes the transaction is dropped by the network because the gas limit was too conservative.
Most MultiCurrencyWallet users find that a simple hard refresh of the page fixes the . The official project documentation is the best place to find step-by-step troubleshooting guides. An outdated web3 provider is often the hidden reason behind many interaction failures. The error could also be the result of an incompatibility with the latest RPC protocol version.
- These practices minimize downtime and reduce the need for risky manual repairs when common Tezos node errors occur.
- Protocols such as Hop, Connext (NXTP), and Orbiter provide liquidity-anchored bridges that let an aggregator route a token swap on one rollup, move assets through a shared liquidity layer, and settle on another rollup in what feels like a single logical operation to the user.
- For baker and endorser errors check that secret keys are available, properly encrypted passwords are supplied to the baker service, and that tezos-client can reach the local RPC; restarting baker services after node recovery often resolves transient key lookup failures.
- The permission model changed over time, so checking wallet version and supported methods helps avoid runtime errors.
- Oracle errors and bridging failures can break peg and liquidity.
- Experimental code is more likely to contain logic errors, and the composition of multiple components multiplies risk.
- Read stack traces and error codes.
Always check the official documentation for the latest maintenance schedule and announcements.