token-flow-tracing

Trace Coin<T> and Balance<T> token flows in Sui Move protocols.

276|56|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/PlamenTSV/plamen --skill token-flow-tracing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-flow-tracing
Source: https://github.com/PlamenTSV/plamen/tree/main/agents/skills/sui/token-flow-tracing
Command: npx skills add https://github.com/PlamenTSV/plamen --skill token-flow-tracing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace and analyze token flows in Sui Move protocols to identify accounting desync, unsolicited deposits, and token lifecycle issues.

Core Features & Use Cases

  • Enumerate and classify Coin<T> and Balance<T> types used by a protocol
  • Trace entry and exit points for deposits, withdrawals, and transfers across modules
  • Detect potential unsolicited deposits or accounting mismatches and provide actionable findings
  • Use case: audit a Sui Move-based DeFi protocol to map token flows and verify reconciliation

Quick Start

Run the token-flow-tracing skill against your target Sui Move project to begin tracing token transfers.

Frequently Asked Questions about token-flow-tracing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace token flows in Sui Move protocols?

To trace token flows in Sui Move protocols, enumerate Coin<T> and Balance<T> types to map entry and exit points for deposits, withdrawals, and transfers across modules. This process identifies accounting desync and token lifecycle issues.

What is accounting desync in Move modules and how do I detect it?

Accounting desync in Move modules occurs when expected token balances diverge from actual movements. Detect it by tracing end-to-end Coin<T> and Balance<T> transfers across modules to identify unsolicited deposits and reconciliation mismatches.

How do I audit a Sui Move DeFi protocol for unsolicited deposits?

Audit a Sui Move DeFi protocol for unsolicited deposits by tracing Coin<T> and Balance<T> token flows across deposit, withdrawal, and transfer functions. Mapping these entry and exit points reveals unexpected token lifecycle issues.

Do I need Move module sources to trace Coin<T> and Balance<T> transfers?

Yes, you need Move module sources to trace Coin<T> and Balance<T> transfers. Accessing the source code is required to map entry and exit points and accurately analyze token movements across the protocol.

What's the best way to map token lifecycle issues in Sui Move?

The best way to map token lifecycle issues in Sui Move is to classify Coin<T> and Balance<T> types and trace their movement across module boundaries. This approach pinpoints accounting mismatches and unsolicited deposits.

Can I use token-flow tracing for Move modules that don't handle Coin<T>?

Token-flow tracing is specifically applicable to Move modules that handle Coin<T> and Balance<T> types. Modules lacking these representations fall outside its scope for tracing deposits, withdrawals, and transfers.