Skip to content

explicitly mention regarding the nonce #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Ishita-02 merged 1 commit into from
Mar 31, 2026
Merged

explicitly mention regarding the nonce #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 16 additions & 3 deletions yield-agentkit-skills/skills/yield-agentkit-privy/references/privy-transactions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,10 +130,23 @@ Most DeFi positions require multiple transactions (e.g., ERC-20 approval
followed by deposit). Always process them in `stepIndex` order, one at
a time, never in parallel:

> **⚠️ Nonce handling:** The yield.xyz MCP may return all transactions
> with the **same nonce** because they are built before any are executed
> on-chain. You **must** increment the nonce for each subsequent
> transaction. Take the nonce from `stepIndex=0` and add the stepIndex
> value to compute the correct nonce for each transaction:
>
> - `stepIndex=0` → use nonce as-is
> - `stepIndex=1` → nonce + 1
> - `stepIndex=2` → nonce + 2
>
> Convert the nonce from hex to decimal, add the offset, then convert
> back to hex before submitting to Privy.

```
TX stepIndex=0: Privy signs → broadcast → poll CONFIRMED
TX stepIndex=1: Privy signs → broadcast → poll CONFIRMED
TX stepIndex=2: Privy signs → broadcast → poll CONFIRMED
TX stepIndex=0: use nonce as-is → Privy signs → broadcast → poll CONFIRMED
TX stepIndex=1: increment nonce by 1 → Privy signs → broadcast → poll CONFIRMED
TX stepIndex=2: increment nonce by 2 → Privy signs → broadcast → poll CONFIRMED
```

If any transaction reaches `FAILED`, stop immediately. Do not proceed
Expand Down
15 changes: 15 additions & 0 deletions yield-agentkit-skills/skills/yield-agentkit-privy/references/semi-autonomous.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -297,14 +297,29 @@ approved individually on the dashboard. Process them in `stepIndex`
order — do not submit the next intent until the previous one reaches
`executed`.

> **⚠️ Nonce handling:** The yield.xyz MCP may return all transactions
> with the **same nonce** because they are built before any are executed
> on-chain. You **must** increment the nonce for each subsequent
> transaction. Take the nonce from `stepIndex=0` and add the stepIndex
> value to compute the correct nonce for each transaction:
>
> - `stepIndex=0` → use nonce as-is
> - `stepIndex=1` → nonce + 1
> - `stepIndex=2` → nonce + 2
>
> Convert the nonce from hex to decimal, add the offset, then convert
> back to hex before submitting to Privy.

```
TX stepIndex=0:
→ Use nonce from unsignedTransaction as-is
→ POST /v1/intents/wallets/{id}/rpc → get intent_id_0
→ Notify user → user approves on dashboard
→ Poll GET /v1/intents/{intent_id_0} until "executed"
→ Read hash from action_result → submit to yield.xyz

TX stepIndex=1:
→ Increment nonce by 1 from stepIndex=0's nonce
→ POST /v1/intents/wallets/{id}/rpc → get intent_id_1
→ Notify user → user approves on dashboard
→ Poll GET /v1/intents/{intent_id_1} until "executed"
Expand Down