#RC#
A generic execution revert is often a safety mechanism protecting the contract’s logic. When mpl-token-metadata fails to broadcast a message, it is usually due to a stale session error 173. Increasing the slippage tolerance by 1% can help bypass a transaction that keeps reverting.
Before you sign the transaction, double-check that your hardware wallet is active and ready. Most mpl-token-metadata users find that a simple page refresh fixes the «stuck button» issue 173. Gaining a basic understanding of EVM mechanics will help you navigate error 173 faster.
Sometimes a simple delay in block finality can make a successful tx look like it failed. Ensure your system clock is accurate, as even a small difference can cause signature issues. Check the status of the sequencer to avoid 173 when moving assets to a rollup.
Deja una respuesta