fix(examples): skip simulateContract for bid to avoid stale RPC allowance error#73
Draft
EByrdS wants to merge 2 commits into
Draft
fix(examples): skip simulateContract for bid to avoid stale RPC allowance error#73EByrdS wants to merge 2 commits into
EByrdS wants to merge 2 commits into
Conversation
…roval After the ERC20 approval is confirmed, calling simulateContract for the bid (an eth_call) on a load-balanced RPC can hit a node that hasn't yet synced the approval block, causing a false "transfer amount exceeds allowance" revert. Calling writeContractAsync directly bypasses the simulation; the actual on-chain execution always sees confirmed state. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira ticket: ECHO-152
Summary
approvetx is confirmed, callingsimulateContractfor the subsequentreplaceBidWithApprovalbid was failing intermittently withERC20: transfer amount exceeds allowance.simulateContractissues aneth_callagainstblock="latest", but on load-balanced public RPCs (e.g.sepolia.base.org) the node handling the call may lag behind and not yet have the block containing the approval — so it sees allowance = 0 and reverts.writeContractAsyncdirectly for the bid, bypassing the pre-flight simulation. The actual on-chain execution always reads confirmed state, so the approval is guaranteed to be visible by the time the transaction is mined.🤖 Generated with Claude Code