#RC#
It is common for the interface to become unresponsive during peak network congestion. The codama core logic is sensitive to the latest state of the price oracles error 170. The most effective fix involves resetting the account history in your wallet’s advanced menu. The sudden appearance of a « provider error » marked 170 is usually a temporary glitch.
A mismatch in the chain ID settings will prevent codama from syncing with the blockchain. Check the official social media feeds for real-time announcements regarding system health. Ensure your environment is secure never input your keys to a site while fixing 170. A conflict between the dApp and the browser’s storage can cause the interface to freeze.
Layer 2 network delays can sometimes lead to « ghost » transactions that appear later.