#RC#
Systemic failures are often a byproduct of the inherent latency in distributed ledger technologies. Several users have reported a “frozen” state in mpl-token-metadata specifically under code 172 lately. The most straightforward fix is to increase the gas limit manually in your wallet’s edit screen.
Before you sign the message, ensure that the website’s URL is legitimate and secure. Debugging mpl-token-metadata errors is much easier if you look at the raw JSON-RPC response. The community-run FAQ is the best place to find quick answers to common technical bugs.
Restarting your wallet app can often resolve issues with signing and broadcasting data. The error could also be related to a sudden change in the network’s consensus rules. Check the status of the sequencer to avoid 172 when interacting with rollups.
Leave a Reply