SEC Innovation Exemption: Where Is the Wallet Check Done?
The SEC lets tokenized US stocks trade in pools only approved wallets can use, on a public chain. It names two places for the wallet check and requires neither.
Tokenization turns a share or a fund unit into a token that carries its own rules.
Tokenization means writing the ownership of a real asset, like a share, a fund unit or a building, as a token on a blockchain. Think of it as a digital share certificate that can move in seconds and that carries its own rules: who may hold it, who may receive it, and what happens when a court orders a freeze.
That last part is what makes it different from a normal crypto coin. A security token has to follow securities law, so the token checks identity and eligibility before every transfer. The articles here explain how that works in practice: the main token standards and how they differ, what a regulator has or has not said, how you check that a token is really backed by the asset it claims, and how you spot a fake one.
Where an article touches on law or regulation, it says what the source states and what is still unclear, and it never treats a proposal as a final rule. Nothing here is legal or investment advice. Every article opens with a 30-second answer and a short list of words to know, so you can start with no background at all.
The SEC lets tokenized US stocks trade in pools only approved wallets can use, on a public chain. It names two places for the wallet check and requires neither.
When a permissioned token hides balances, how does a freeze still work? One OpenZeppelin check step by step, and why a successful transfer can move nothing.
Converting ERC-3643 tokens on a Cosmos EVM chain parks them in one escrow account. Why the agent’s freeze then misses the people holding the bank coins.
Three ways to build a security token, and the one question that separates them: where each transfer gets checked. A plain guide to picking ERC-3643, ERC-1400 or CMTAT.
Lessons from preparing a Cosmos EVM chain at Integra: choosing between contracts, an L2 and an application chain, with explicit costs and permission boundaries.