You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some wallets will reissue the same calls over and over again for extended periods when they receive errors.
In many cases the responses are static (e.g. INVALID_CONTRACT_ID and INVALID_ACCOUNT_ID) and will not change over time or with successive or other transactions
Solution
This can be optimized by capturing calls and their error response in a cache (LRU) that returns the static response if called again.
Care should be taken to only do this for static responses whosE success is not impacted by future calls
Alternatives
No response
The text was updated successfully, but these errors were encountered:
Problem
Some wallets will reissue the same calls over and over again for extended periods when they receive errors.
In many cases the responses are static (e.g. INVALID_CONTRACT_ID and INVALID_ACCOUNT_ID) and will not change over time or with successive or other transactions
Solution
This can be optimized by capturing calls and their error response in a cache (LRU) that returns the static response if called again.
Care should be taken to only do this for static responses whosE success is not impacted by future calls
Alternatives
No response
The text was updated successfully, but these errors were encountered: