[MPL-TOKEN-METADATA] Borsh Serialization Error
#RC#
The complexity of modern smart contracts means that even a minor data mismatch can cause a halt. When mpl-token-metadata fails to process a request, it is usually due to a stale connection error 129. The most effective fix involves resetting your wallet’s account data to clear the local history.
Sometimes the transaction is dropped by the network because the gas limit was too conservative. The mpl-token-metadata protocol expects the gas limit to be at least 20% higher than the estimation error 129. Learning how to read a block explorer can help you identify exactly where a tx reverted.
It is worth checking for any active governance proposals related to 129 that change logic. Using a transaction simulation tool can prevent many costly mistakes and errors like 129. Check the status of the sequencer to avoid 129 when moving assets to a rollup.