Closing a YieldVault can leave a stale scheduled AutoBalancer tx that later fails with Invalid transaction handler

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

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
55/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
静か
技術スタック
blockchain
領域
blockchain

調査の方向性

Start at FlowYieldVaultsStrategiesV2.burnCallback() and FlowYieldVaultsAutoBalancers._cleanupAutoBalancer(), then trace DeFiActions.AutoBalancer.cancelScheduledTransaction and the FlowYieldVaultsSchedulerRegistry.unregister() path. Done means pending AutoBalancer schedules are canceled before the handler and capabilities are removed, so the stale transaction from the reported sequence cannot later fail in FlowTransactionScheduler.

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

説明

bug

Summary

Closing a YieldVault can leave behind an already-scheduled DeFiActions.AutoBalancer transaction. When that stale scheduled tx later executes, FlowTransactionScheduler fails with:

Invalid transaction handler: Could not borrow a reference to the transaction handler

This happened on mainnet for YieldVault 338.

On-chain sequence

  1. 2026-03-26 15:59:29 UTC
    Tx cebd06599a069af88b3ceb909b4fdadaa32d366cd4c7b72c48c9aca841ecb8b3

    • FYVEVM worker created YieldVault 338
    • same tx emitted DeFiActions.CreatedAutoBalancer with uuid = 13194142095838, uniqueID = 338
    • same tx emitted FlowTransactionScheduler.Scheduled with:
      • id = 156720
      • transactionHandlerTypeIdentifier = A.6d888f175c158410.DeFiActions.AutoBalancer
      • transactionHandlerUUID = 13194142095838
      • timestamp = 2026-03-26 16:09:29 UTC

  2. 2026-03-26 16:02:28 UTC
    Tx ccd2722170525c1bd7ece82dc50b71f899ea7e85324e8d2e78c482c64ab35087

    • FYVEVM scheduler picked up close request 97 for YieldVault 338
    • scheduled worker tx 156723

  3. 2026-03-26 16:02:29 UTC
    Tx 53d2d8169a77851b1a729e19cd2e39642e1ed20519cd14c07ac4eff307f24b71

    • FYVEVM worker closed YieldVault 338 successfully

  4. 2026-03-26 16:09:29 UTC
    Tx 2a6a879ca2049edca43dc7392fbe5f3420550366452117a41e90686335eece3e

    • generic scheduler wrapper attempted to execute scheduled tx 156720
    • failed with Invalid transaction handler: Could not borrow a reference to the transaction handler

Why this looks like a FlowYieldVaults cleanup bug

The scheduled tx 156720 is clearly the AutoBalancer tx created for YieldVault 338. But vault 338 was already closed about 7 minutes earlier, so when 156720 fired, its handler no longer existed.

From the deployed mainnet contracts:

  • FlowYieldVaultsStrategiesV2.burnCallback() calls FlowYieldVaultsAutoBalancers._cleanupAutoBalancer(id: self.id()!)
  • _cleanupAutoBalancer() unregisters the vault, deletes capability controllers, and burns the AutoBalancer
  • FlowYieldVaultsSchedulerRegistry.unregister() removes registry/capability mappings but does not cancel already-scheduled transactions
  • DeFiActions.AutoBalancer does have cancelScheduledTransaction, but AutoBalancer.burnCallback() does not cancel outstanding scheduled txs

So the close path appears to remove the AutoBalancer handler without first canceling its already-scheduled rebalance txs.

Expected behavior

When a YieldVault is closed, any pending AutoBalancer scheduled transactions for that vault should be canceled before the AutoBalancer handler/capabilities are removed.

Actual behavior

The AutoBalancer handler is cleaned up, but the already-scheduled transaction remains in FlowTransactionScheduler and later fails at execution time.

Additional note

The docs currently state that closing a YieldVault cancels pending schedules, but the observed mainnet behavior above shows that at least this path still leaves a stale scheduled tx behind.

主要言語
Cadence
スター
41
フォーク
0
30日以内にマージされた PR はありません

環境構築

はじめの一歩

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

onflow/FlowYieldVaults のほかの issue

onflow/FlowYieldVaults の issue をすべて見る

似ている issue

Blockchain の issue をもっと見る

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

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