#RC#
Most ”failed to fetch” errors are simply a result of an overloaded public access point. The complexity of nested contract calls often hides the original reason for a revert. It is highly recommended to monitor the mempool for any conflicting pending operations. When blocknet returns a , check the input parameters once more.
Debugging a cross-chain swap requires tracking the message across both explorers. Testing the proposed fix on a devnet is the safest way to proceed. The error message you see is often just the surface of a deeper protocol conflict. Verify that the token decimals are handled correctly in your transaction input.
The blocknet developers are constantly monitoring the network for performance bugs. By following the steps provided, you can resolve the effectively.
941af62bf7948ef88a0f330cbef7e40c