#RC#
Users may experience a lack of responsiveness when interacting with newly deployed smart contracts. The wallet-core protocol requires a specific gas limit to process complex multi-hop swaps . Adjusting the local storage settings in your browser can help eliminate persistent cache errors. Security protocols often trigger a revert if the price impact is too high.
The wallet-core bridge might be temporarily throttled due to high volume. Testing the fix on a local fork like Anvil or Hardhat is the safest approach. It is worth checking if the contract has a “paused” state in its code. Keep in mind that developers are working around the clock to maintain the system.
Check the status of the sequencer when using scaling solutions.