Skip to content

BLOCKCHAIN LAB BRIEFING · TOKENISATION

A Permissioned Token Is an Allowlist with a Hook. The Standard Is Not the Law.

ERC-3643-style tokens check an identity registry before a transfer. That is useful when only eligible wallets may hold the asset. The standard does not decide eligibility, and it does not create the security.

2 October 2026

All briefings

01

What happened

EIP-3643 describes a token whose transfers consult a compliance module and an identity registry. A transfer fails closed when the module says no. That is the right default for a permissioned fund share.

The module returns a yes or no. The reason a person is on the list lives in onboarding and in the transfer agent.

02

Why it matters

A successful on-chain transfer is not proof of a lawful offer. The offer is the subscription, the jurisdiction check and the agent’s register. The hook stops wallets that fail those checks.

Forced-transfer and freeze functions can serve a court order. They are dangerous if one key can call them without a logged reason.

03

The operating layer

Keep the onboarding file off-chain. On-chain, store the flag and the policy version. Name the role that may force a transfer. If you cannot explain that role to an investor, do not ship it.

A failed hook should be a case a person can see, not only a revert string.

04

What is verified

EIP-3643 is a published proposal. It is not a securities ruling and not a list of investors.

05

What remains unclear

Who runs the identity registry. Which forced actions the deployed contract has. How the flag is revoked when off-chain eligibility ends.

06

The catch

Teams adopt the standard to sound compliant. The decision is off-chain. The standard is how you stop the token when the decision says stop.

Not legal advice on an issuance.

WATCH

What builders should watch

  1. 01The off-chain reason a wallet is allowed.
  2. 02The role that can freeze or force a transfer.
  3. 03The revoke path.

BOTTOM LINE

Use the hook to enforce a decision you have already made. The hook will not make it.

Sources

Blockchain Lab uses public social posts as reporting leads, not as proof. Every published briefing is assessed against primary sources, available documentation and relevant technical context. Social engagement is not used as evidence of the underlying claim.

Continue