docs: add troubleshooting guide for failed swap (Nonce fix) #23
Conversation
WalkthroughAdds a Troubleshooting section to the README titled "Troubleshooting Swap / Transaction Failures on KIIDEX," describing nonce-related failures and a three-step resolution: check the suggested nonce from the error or wallet, manually set the nonce to that value, and resend the transaction. Notes that this ensures proper transaction sequencing. Also applies a minor formatting tweak to the Testnet Faucet link. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Pre-merge checks (2 passed, 1 warning)❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
README.MD (2)
59-66: Tighten nonce guidance: add authoritative check and replacement flow.
Prevents users from guessing and covers stuck-pending cases. Also keeps terminology consistent.Apply this diff:
-### How to Fix Nonce Issues -1. When a transaction fails, check the **suggested Nonce** from the error message or wallet prompt. -2. Manually set the Nonce value as suggested. For example: - - If the error suggests **Nonce = 1**, then manually update the Nonce to `1`. -3. Confirm and resend the transaction. - -This adjustment ensures the transaction is processed in the correct sequence by the network. +### How to fix nonce issues +1) Determine your account’s pending nonce (recommended): + • From your wallet/explorer, or via JSON‑RPC: + ```bash + curl -s -X POST https://json-rpc.uno.sentry.testnet.v3.kiivalidator.com \ + -H 'content-type: application/json' \ + --data '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionCount","params":["0xYourAddress","pending"]}' + ``` + Use the returned hex value as the nonce. +2) If a tx is stuck, replace/cancel it: + • Send a new tx with the same nonce and a slightly higher fee (EIP‑1559: bump maxPriorityFeePerGas/maxFeePerGas). + • Or send a 0-value self‑transfer with the same nonce to cancel. +3) If your wallet suggests a nonce, use that exact value (e.g., “nonce = 1” → set nonce to 1) and resend. + +Note: Nonce is per‑account, starts at 0, and must be sequential. Skipping values will keep higher‑nonce txs queued until gaps are filled.
57-57: Consistency: lowercase “nonce”.
Use “transaction nonce” (lowercase) for standard EVM terminology.-If you encounter a **failed transaction or swap** on [KIIDEX](https://kiidex.kiichain.io/), one possible cause is an incorrect **transaction Nonce**. +If you encounter a **failed transaction or swap** on [KIIDEX](https://kiidex.kiichain.io/), one possible cause is an incorrect **transaction nonce**.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.MD(1 hunks)
🔇 Additional comments (1)
README.MD (1)
55-55: Nice addition: troubleshooting section is valuable for users.
Clear, discoverable heading. Good call-out to KIIDEX.
| More information about how to use our discord Faucet can be found at: | ||
|
|
||
| - [Testnet Faucet](https://docs.kiiglobal.io/docs/build-on-kiichain/developer-tools/testnet-faucet) | ||
| - [Testnet Faucet](https://docs.kiiglobal.io/docs/build-on-kiichain/developer-tools/testnet-faucet) |
There was a problem hiding this comment.
Fix mismatch: mentions “discord Faucet” but links to Testnet Faucet docs.
Aligns wording with the actual link target.
-More information about how to use our discord Faucet can be found at:
+More information about how to use the Testnet Faucet can be found at:
-- [Testnet Faucet](https://docs.kiiglobal.io/docs/build-on-kiichain/developer-tools/testnet-faucet)
+- [Testnet Faucet Docs](https://docs.kiiglobal.io/docs/build-on-kiichain/developer-tools/testnet-faucet)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| More information about how to use our discord Faucet can be found at: | |
| - [Testnet Faucet](https://docs.kiiglobal.io/docs/build-on-kiichain/developer-tools/testnet-faucet) | |
| - [Testnet Faucet](https://docs.kiiglobal.io/docs/build-on-kiichain/developer-tools/testnet-faucet) | |
| More information about how to use the Testnet Faucet can be found at: | |
| - [Testnet Faucet Docs](https://docs.kiiglobal.io/docs/build-on-kiichain/developer-tools/testnet-faucet) |
🤖 Prompt for AI Agents
In README.MD around lines 71–73 the text says "discord Faucet" but the hyperlink
targets the Testnet Faucet docs; update the copy and/or link so they
match—either change the phrase to "Testnet Faucet" to match the existing URL, or
replace the URL with the correct Discord Faucet documentation link if the intent
was to reference a Discord faucet.
1 participant
Description
This PR updates the README.md to include troubleshooting steps for failed swap or transaction issues on KIIDEX.
Specifically, it documents how to adjust the transaction Nonce manually when a swap fails.
Type of change
How Has This Been Tested?