Transfer Restriction

A transfer restriction is a rule built into a token that limits how, when, and to whom it can be moved. For regulated real-world assets, these restrictions are how a security token enforces its legal constraints in code: instead of trusting holders to follow the rules, the contract checks each transfer and reverts any that would break them.

Securities come with transfer limits by law and by deal terms, and transfer restrictions encode them directly. Common examples include a whitelist check so only verified investors can hold the token; a lock-up that blocks transfers for a set period after issuance; a cap on the number of holders to stay within an exemption; jurisdiction blocks that prevent transfers to a restricted jurisdiction; and holder-limit or balance rules.

Mechanically, the token runs a check - a function often named something like canTransfer - before moving balances. If the transfer satisfies every rule, it proceeds; if not, it fails, sometimes returning a reason code that explains why. Standards such as ERC-3643 and ERC-1400 are designed around exactly this kind of pluggable restriction logic.

These restrictions are the main reason a security token does not behave like a stablecoin. You cannot send it to an arbitrary address on a whim - the rules travel with the token wherever it goes, which is what lets it trade on a compliant secondary market rather than leak into open circulation.

At the far end, a token can be made effectively non-transferable - see the non-transferable token - during a mandatory holding period or for assets never meant to move. For an investor, the practical lesson is to understand a token's restrictions before buying, because they determine whether and when you can actually sell.

Source: Ethereum Improvement Proposals (eips.ethereum.org), as of 2026.