Skip to content

docs(examples): note RPC fix for intermittent allowance error on bid#88

Merged
WillSewell merged 1 commit into
mainfrom
fix/sonar-5-rpc-allowance-comment
May 6, 2026
Merged

docs(examples): note RPC fix for intermittent allowance error on bid#88
WillSewell merged 1 commit into
mainfrom
fix/sonar-5-rpc-allowance-comment

Conversation

@WillSewell

@WillSewell WillSewell commented May 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The post-approval simulateContract for the bid in the EVM example apps can intermittently revert with ERC20: transfer amount exceeds allowance. Root cause: load-balanced public RPCs (e.g. the default sepolia.base.org) may route the eth_call to a node that hasn't yet synced the approval block. The on-chain execution is unaffected — clicking Commit a second time succeeds.
  • The pre-flight simulation is valuable (clean UI errors for any other revert reason), and the right production fix is to point the dapp at a dedicated, non-load-balanced RPC. That's already supported via NEXT_PUBLIC_BASE_RPC_URL / VITE_BASE_RPC_URL (see .env.example).
  • This PR adds a code comment at the bid simulation site explaining the symptom and the fix, so a developer who hits it in the example knows exactly what to do.

Supersedes #87.

Test Plan

  • Comment-only change — no behavior modified
  • No code paths affected; type/lint unchanged

The post-approval simulateContract for the bid can revert with
"ERC20: transfer amount exceeds allowance" when the configured RPC
is load-balanced (e.g. the default sepolia.base.org), because the
eth_call may be served by a node that hasn't yet synced the approval
block. Add a comment pointing developers to the existing
NEXT_PUBLIC_BASE_RPC_URL / VITE_BASE_RPC_URL env var as the fix.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@WillSewell
WillSewell merged commit 81084f6 into main May 6, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants