BUG: Flaky Network Switching Validation
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- blockchain, payments
Research direction
Start by reading TransactionReview.jsx, especially handleBuySc and its network switch flow. Reproduce the mismatch by switching MetaMask to a different network and submitting a transaction; trace how the provider chain ID and freshWalletClient.chain.id are checked. Done when a successful network switch lets the transaction proceed immediately without a false mismatch error.
Written by the indexing model from the issue text.
Description
[y] I have checked for duplicate issues
Description
In TransactionReview.jsx, the handleBuySc function performs a manual verification of the network after switching. It compares window.ethereum chain ID with the freshWalletClient.chain.id. This logic is brittle because freshWalletClient might maintain an old reference or the provider might not have emitted the event yet, leading to false positives for "Network mismatch" errors.
How to Reproduce
- Set MetaMask to a network different from the one selected in the widget.
- Click "Send Transaction".
- Approve the network switch in MetaMask.
Expected Behavior
The transaction proceeds immediately after the switch.
Actual Behavior
Occasionally, the code throws Wallet client chain mismatch, forcing the user to click the button again.
[y] I want to work on this issue
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from StabilityNexus/StablePay
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
StabilityNexus/StablePay#64 · 1 comment ·
-
[BUG]: Missing SDK API documentation and incomplete developer-facing usage guide in StablePay READMEOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
StabilityNexus/StablePay#104 · 1 comment ·
-
[BUG]: `stablepay-sdk` README documents an unrelated thirdweb app instead of the actual SDK APIOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
StabilityNexus/StablePay#102 ·
-
[FEATURE]: Centralize transaction initialization and quote fetching to avoid duplicate RPC calls in the widgetMay be free again @CaptainLevi2k04 claimed this 81 days ago, and no pull request is open. Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 38/100
StabilityNexus/StablePay#101 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
StabilityNexus/StablePay#96 · 1 comment ·
All issues in StabilityNexus/StablePay
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Leonxlnx/taste-skill#216 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
all-contributors/cli#690 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day