페이지를 넘기고 있습니다.
다음 장을 불러오고 있습니다…
잠깐… 나만의 읽기 환경을 만들어 보세요.
글꼴과 테마는 화면 설정에서 설정하세요. 눈의 편안함도 중요합니다.
다음 장을 불러오고 있습니다…
Additional behavior and dependencies introduced when a token calls custom logic as part of a transfer.
브라우저의 읽어주기 지원을 확인하는 중…
이 읽기 자료는 현재 영어로 제공됩니다. 인터페이스에는 선택한 언어가 적용됩니다.
영어 원문 읽기 →Solana's Token-2022 transfer hook extension allows a mint to associate additional program logic with transfers. The feature can support legitimate controls and application behavior, but it changes what an integration must understand. A token transfer is no longer fully described by amount, sender, and recipient alone; the hook's rules and required accounts can determine whether the operation succeeds.
Suppose a token's hook requires a particular account or eligibility condition. A wallet or exchange that assumes every token follows only the basic transfer path may fail to build a usable transaction. That failure does not automatically prove a scam, but users need an explanation of the restriction. Conversely, a successful small transfer does not establish that all later transfers, recipients, or market routes will satisfy the same custom logic.
Check the hook program, the authority that can configure it, any upgrade authority, and the conditions the program actually enforces. Determine whether normal transfers depend on an external service or mutable account state. A token can have a revoked mint authority while retaining other meaningful controls, so one reassuring badge is insufficient. For an encyclopedia, explain the extension as a capability and document specific observed restrictions without assuming that every hook is malicious or that every supported token behaves like a basic SPL token.