DFNS now supports transfer hooks on Solana. Tokens built on Solana’s Token-2022 program can attach a hook, a program that runs on every transfer of that token and can inspect it, enforce rules or reject it. Institutions on DFNS can now hold and transfer such tokens through the same Transfers API they use for everything else, with the extra accounts a hook requires resolved by the platform, the transfer evaluated by the Policy Engine before it is signed, and the result recorded in the same audit trail.
What a transfer hook is
Solana’s original token program treats every token the same way. A transfer moves a balance from one account to another, and the token itself has no say in the matter. For a meme coin that is fine. For a security, a fund share or a regulated stablecoin, it is a problem, because the rules that govern who may hold and transfer the asset have to live somewhere, and the original program gives an issuer a single onchain lever for them: an optional freeze authority that can lock a holder’s account outright, which is how USDC enforces its blocklist on Solana. That is a switch, not a rule. Who is eligible, under what conditions and on which transfers could only be decided offchain, and nothing on the chain checked it at the moment of transfer.
Token-2022, also called Token Extensions, changes that. A token can be created with extensions that add behaviour to the mint itself, such as transfer fees, non-transferability, a permanent delegate or confidential balances. The most consequential of them is the transfer hook. When a mint has the transfer hook extension, the token program calls a hook program the issuer chose as part of every transfer instruction. The hook sees the source, the destination, the mint, the transfer authority, the amount and any additional accounts it asked for. The transfer accounts are passed to it read-only, so it can inspect the movement but not alter it. It can check an allowlist, verify an identity credential, enforce a holding period, apply a jurisdictional restriction or record a royalty. If it rejects the transfer, the whole transaction fails and nothing moves. The rule is enforced by the chain, on every path, including paths the issuer never built.
That makes transfer hooks the mechanism behind permissioned tokens on Solana. An issuer encodes its transfer restrictions once, in the hook, and every wallet, exchange and application that touches the token inherits them.
Why they were hard to support
A hook does not run in a vacuum. The accounts it needs, an allowlist account, a registry, a per-holder record, must be passed into the transfer instruction, and the token program will fail the transfer if they are missing. Each hook needs a different set. The transfer hook interface solves this with an extra account metas list, stored onchain in a separate account that the hook program owns and derives from the mint, which describes the accounts a hook requires and how to derive them. A wallet that wants to transfer a hooked token has to read that list, resolve each entry, which may depend on the source, destination or mint, and append the resolved accounts to the transaction in the right order.
The standard Solana client libraries do this for a developer who builds the transaction with them. Custodial infrastructure often does not: a custody platform builds and signs transactions in its own pipeline, for mints it has never seen, and when that pipeline does not read the hook’s account list the transfer fails with an opaque error, and the institution concludes the token does not work. In practice it means the most carefully governed tokens on Solana were the hardest for institutions to hold.
What DFNS supports
DFNS resolves transfer hooks automatically. When a transfer involves a Token-2022 mint with the transfer hook extension, the platform reads the hook program and its extra account metas list from the chain, resolves every required account, including those derived from the specific source, destination and mint, and builds the transaction so the hook executes as the issuer intended. The developer sends the same Spl2022 transfer request as for any other Token-2022 token. Nothing about the hook has to be known in advance.
The result is a transfer that the token’s own rules have approved, carried out under the institution’s rules as well. Before the transaction is signed, the Policy Engine evaluates it like any other transfer, with approval quorums, limits, allowlists and screening. If the hook rejects the transfer onchain, DFNS surfaces the failure with the hook’s reason rather than a generic error, so operations teams know whether the token’s rules or their own stopped the movement. Transfers of hooked tokens appear in wallet history and fire the standard webhooks, and balances of Token-2022 mints are indexed alongside everything else.
Support covers the transfer hook extension together with the other Token-2022 extensions commonly combined with it, including transfer fees, metadata and the permanent delegate. Confidential transfers, which hide amounts, are a separate extension and are not covered here.
Why it matters
Transfer hooks are one of the mechanisms behind Solana’s institutional use cases, and the one that carries the most logic. Token-2022 gives an issuer blunter tools as well. Accounts can be frozen by default until a holder is approved, a permanent delegate can seize or burn a balance, and a pause switch can halt the whole mint. Some of the best-known tokenized stocks and stablecoins on Solana enforce their rules that way today, and most royalty enforcement still runs through Metaplex’s programmable NFTs rather than a hook. A hook is what an issuer reaches for when the rule has to be checked on every transfer rather than at onboarding. A fund whose shares can only move between eligible holders. A security that must stay within a verified investor base. A stablecoin that screens each transfer in the token itself. A royalty that pays its creator on every sale. Tokens built that way were out of reach for an institution whose wallet infrastructure could not resolve the hook, and they are the ones this release unlocks.
For issuers, the match with DFNS is direct. An issuer encodes its rules in a hook and the chain enforces them everywhere. DFNS adds the institution’s own layer on top, the approvals, limits and evidence a regulated business needs, so a transfer has to satisfy the token and the institution before it signs. Two sets of rules, neither of which can be bypassed, both recorded.
For holders, it means the tokens that carry the most governance are now the ones that work with the least friction. A bank holding a permissioned security on Solana transfers it the same way it transfers USDC, and the compliance encoded in the token comes along for free.
Getting started
Transfer hook support is available now for all DFNS wallets on Solana mainnet and devnet, through the dashboard and the API, with no configuration required. Transfers of hooked Token-2022 mints use the same Spl2022 transfer request as any other Token-2022 token. Nothing hook-specific is added to it.
- Learn more about onchain core banking: dfns.co
- Explore the platform and documentation: docs.dfns.co
- Talk to our team about Solana: sales@dfns.co