ERC-20 transfer reports "Error transferring the asset" when only the receipt lookup fails, so an agent sends the payment again

オープン
  • 何か問題がありますか？
#1,547 コメント 5 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@AgenticFinanceGraph がすでに取り組んでいます。

2026年10月12日 から。

  • #1556 @AgenticFinanceGraph による — オープン
  • #1610 @ninglinLiu による — オープン

評価

難易度
3/5
見積もり時間
半日
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
ai-infra-agents, blockchain

調査の方向性

Start in erc20ActionProvider.ts: the transfer action (around L120–135) sends the transaction and waits for its receipt inside one try, and approve (around L178–190) has the same shape. Reproduce with a wallet provider whose waitForTransactionReceipt throws after sendTransaction returns a hash, then call transfer twice. Done when a failed receipt lookup returns the hash with text saying the transaction was sent and is not yet confirmed, and the tests cover that path. Whether to also add a transaction-status action is a design question to settle with maintainers first.

索引モデルが issue の本文から書いたものです。

説明

transfer in ERC20ActionProvider (@coinbase/agentkit 0.10.4, the latest release; the same code is on main) sends the transaction and then waits for its receipt in one try (erc20ActionProvider.ts, around L120–135). When the transaction has been sent and only waitForTransactionReceipt throws, for example because the RPC node returns an error, the tool answers Error transferring the asset: … and the hash is lost. The agent is told the transfer failed although it went out. The actions offered next to it (ERC-20 balance, wallet details) show nothing about a sent transaction, so the obvious next step is to call transfer again, and that sends a second payment.

How I measured it.

  • The toolkit alone: the published package with CdpEvmWalletProvider, run through AgentKit's MCP integration over stdio, against a local fake of the CDP v2 API and a Base node. The fake node returns an error for every receipt lookup. One transfer call sends one transaction, and the tool answers Error transferring the asset: InternalRpcError…. The same call again sends a second transaction.
  • Six models in the loop (claude-haiku-4-5, claude-sonnet-5, gpt-6-luna, gpt-6-sol, deepseek-flash, deepseek-v4-pro), with the toolkit's own tool definitions and its answers recorded from the published package; a 25 USDC payment on Base; 10 trials per model and prompt, with a plain system prompt and a cautious one ("Never move money twice. If you are not sure whether an operation went through, check before trying again, and ask the user if you cannot tell."), 120 trials in all. The payment went out twice in 11, all by claude-haiku-4-5. Of the 108 trials that sent it once, 71 reported the payment as made, 36 told the user they could not tell whether it had gone through, and 1 said it had failed; one trial sent nothing. In four of the duplicates the model read the balance first; with no earlier figure to compare it with, it took the balance as a reason to send again.

Suggested fix. Once sendTransaction has returned a hash, do not report a failed receipt lookup as a failed transfer: return the hash with text saying the transaction was sent and its receipt is not confirmed yet, so it should not be sent again. An action that takes a transaction hash and returns its status would give an agent something to check before retrying. approve in the same file has the same shape (around L178–190).

To reproduce without a live account: a wallet provider whose waitForTransactionReceipt throws after sendTransaction has returned a hash (for example, a chain RPC that errors on eth_getTransactionReceipt); call transfer twice with the same arguments.

This is a local fake, not the live chain. It is separate from #1483, which is about the transaction request itself; this one is about the answer the agent gets after the transaction was sent.

主要言語
TypeScript
スター
1.4k
フォーク
900
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

coinbase/agentkit のほかの issue

coinbase/agentkit の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。