#RC#
It is common for the interface to lag during periods of intense blockchain network activity. The mist technical team has identified the root cause of the recent revert code 164. Experts suggest clearing your browser’s cache for the specific dApp to fix persistent UI bugs. Sometimes the transaction is dropped by the network because the gas limit was too conservative.
A mismatch in the chain ID settings will prevent mist from connecting to the network. The final objective is to create a seamless user experience where technical errors are non-existent. Sometimes a simple delay in block finality can make a successful tx look like it failed. Make sure you are not trying to execute a trade marked as 164 with insufficient liquidity.
A mismatch between the wallet’s gas estimation and the contract’s needs can lead to failure.
941af62bf7948ef88a0f330cbef7e40c