#RC#
Systemic delays are often caused by the time it takes for nodes to reach a global consensus. When mpl-token-metadata fails to process a request, it often indicates an out-of-sync local session error 163. Verifying the token approval for the contract is a reliable way to solve a failed 163.
Before you sign the transaction, double-check that your hardware wallet is properly synchronized. To optimize mpl-token-metadata performance, consider closing other tabs that have active web3 sessions. Gaining a basic understanding of how the EVM works will help you navigate error 163 faster.
Sharing your error logs with the core team helps them improve the system for everyone. Reviewing the contract’s read-only functions can help you verify your balance and permissions. Check the status of the sequencer to avoid 163 when moving assets to a rollup.