官方的 MASTR 标志 MASTR 支持这项工作
目录
← 知识库首页

Wallets & security

Transfer hooks: the extra programme inside a transfer

Read the additional logic before assuming a token behaves like a simple balance.

Research guide · 9 September 2026 · 1 min read

研究文章和参考条目以英语发布。导航提供七种语言。

本文目录
  1. Map the dependency Identify the hook programme, its configuration and any additional accounts it requires. Determine whether that programme can be upgraded and who holds the authority. Review the actual conditions under which transfers succeed, rather than assuming the behaviour from a token description.
  2. Test the relevant direction A successful incoming transfer does not establish that every outgoing transfer will work under the same conditions. Where testing is authorised, compare the intended user operation with a small, controlled example and record the accounts, slot and response. Do not expose someone else's funds to prove a point.
  3. Explain the practical consequence Report the conditions and the authority that can change them. Do not call every hook a honeypot. A restriction might implement a disclosed product rule, while an undisclosed restriction might contradict the market-facing promise. The difference is established through configuration, execution and communication, not through a label pasted onto a scanner result.

Solana's transfer-hook extension allows custom programme logic to execute during token transfers. This creates another dependency to examine alongside the mint and token account. A transfer can involve more than subtracting one balance and adding another.

Map the dependency Identify the hook programme, its configuration and any additional accounts it requires. Determine whether that programme can be upgraded and who holds the authority. Review the actual conditions under which transfers succeed, rather than assuming the behaviour from a token description.

Test the relevant direction A successful incoming transfer does not establish that every outgoing transfer will work under the same conditions. Where testing is authorised, compare the intended user operation with a small, controlled example and record the accounts, slot and response. Do not expose someone else's funds to prove a point.

Explain the practical consequence Report the conditions and the authority that can change them. Do not call every hook a honeypot. A restriction might implement a disclosed product rule, while an undisclosed restriction might contradict the market-facing promise. The difference is established through configuration, execution and communication, not through a label pasted onto a scanner result.

来源

Solana documentation · transfer-hook

Technical reference checked 9 September 2026. The review questions are editorial analysis, not findings about a named project.

相关阅读

MASTR

支持独立研究

这里的调查、原始证据和指南均可免费阅读。自愿捐赠帮助支付研究成本,让 MASTR 能够继续提供工具。

打开钱包