SKIP TO CONTENT
TOKENIZATION6 minBuilding the RWA Chain / Ep. 3 · Stage 3-2

Native Tokenized Shares: What a Token Register May Need

Say your share register lives on a blockchain. Who keeps out a buyer the law forbids, or applies a freeze a court ordered?

XIN
Pixel-art night scene on water: on the left a gift-wrapped magenta cube tied by a glowing thread to a locked vault on a distant hill, on the right a cyan cube holding an open ledger book and bound by a chain, with a gold coin crossing a small bridge between them.

IN 30 SECONDS

A native register is a share register kept on a blockchain, where the law accepts it. Then the token contract may have to do a register’s jobs: keep ineligible wallets out, apply freezes, force transfers the law requires and restore lost access.

KEY TAKEAWAYS · 3

  • ESMA finds wrapped set-ups only partly deliver a single source of truth and direct ownership through self-custodial wallets.
  • Depending on the law and the instrument, a native register may need eligibility, freeze, forced-transfer and recovery controls. ERC-3643 standardizes interfaces for them.
  • A standard can build those controls in. It can’t, by itself, give the record legal effect: that depends on the governing law.
On this page

Why go native at all

IN SHORT Wrapping works today, but ESMA finds it keeps only part of what tokenisation promised.

WORDS TO KNOW

Share register
The official list of a company’s shareholders. The law decides which list counts.
Native issuance
The company issues its own shares directly on a blockchain, so the on-chain record is meant to be the register.
Self-custodial wallet
A wallet you control yourself, with no firm holding it for you.
Agent
In ERC-3643, an administrator role with special powers over the token, such as forced transfers.

In its September 2026 report, ESMA lists the costs of wrapped set-ups. The “single source of truth” and “direct investor ownership through Self-custodial wallet A wallet you control yourself, with no firm holding it for you. See the glossary” are only partly realised.

These set-ups “may also introduce” more middlemen. They may also create new reliance on platforms and custodians as counterparties. That alone isn’t a verdict on a product, but it shows which risk you hold.

ESMA also warns about split markets. The same share may exist as several tokens that aren’t fully fungible (swappable one for one). Then liquidity may split “across venues and legal frameworks”.

IN PLAIN WORDS

With Native issuance The company issues its own shares directly on a blockchain, so the on-chain record is meant to be the register. See the glossary, the company issues its shares on-chain. The record is then meant to be the Share register The official list of a company’s shareholders. The law decides which list counts. See the glossary itself.

Coming up next: What does that change for one transfer of 10 tokens?

The same transfer, two structures

IN SHORT Run the same 10-token transfer through both models, and only one of them changes the register.

A WORKED EXAMPLE

Illustrative numbers

TOKEN MOVEDAlice sends 10 wrapped tokens to Bob

INPUT

Structure
wrapped, custodial
Share register
off-chain, at the custodian
Amount
10 tokens

WHAT HAPPENS

  1. The token contract records 10 tokens in Bob’s wallet.
  2. The share register is not touched. The custodian still holds the shares.

OUTPUT

Bob holds
10 tokens and the rights their terms give
Shareholder of record
the custodian (unchanged)

ENTRY MOVEDSame transfer, native register recognised by the law

INPUT

Structure
native issuance
Share register
on-chain, recognised by the governing law

WHAT HAPPENS

  1. The token checks that Bob’s wallet is eligible to hold the share.
  2. The register entry for 10 shares moves from Alice to Bob.

OUTPUT

Holder of record
Bob, if validly recorded

Same click, same wallet screen. What Bob ends up with depends on where the register lives, and on the law behind it.

What the token contract may have to do

IN SHORT If the token is the register, the token contract may have to do a register’s jobs.

This assumes the law behind your register accepts a DLT record (a record on a shared ledger) for your type of share. Then, depending on that law and the share, the token contract may carry real register duties.

ILLUSTRATIVE NATIVE TRANSFER

Flow diagram: 4 stepsFlow diagram: 4 steps. A transfer is requested, then Is the receiver eligible?. Is the receiver eligible?, then Any freeze or rule in the way?. Any freeze or rule in the way?, then The register entry moves.1A transfer is requested2Is the receiver eligible?3Any freeze or rule in theway?4The register entry moves
In ERC-3643 the token asks an identity registry whether the receiver is verified.

Step 1. Request. Alice asks to send 10 shares to a new holder.

Pick a step to see it move
  1. Request Alice asks to send 10 shares to a new holder.
  2. Not eligible: refused Carol’s wallet isn’t eligible, so the transfer is refused and the register doesn’t change.
  3. Freezes and rules For Bob, who is eligible, the token checks any freeze, such as one a court ordered, and its other rules.
  4. Entry moves Everything passes: the register entry moves to Bob.
Illustrative, modelled on ERC-3643. Whether the moved entry carries legal title depends on the governing law.
REGISTER DUTIES, IN PLAIN WORDS
Eligibility
Keep ineligible wallets out
Freeze
Apply a freeze ordered by a court
Forced transfer
Move shares when the law requires it
Recovery
Restore access for a holder who lost a key
Duties covered by the ERC-3643 specification (status Final). Usage examples are illustrative. The standard defines interfaces; whether they meet a given legal regime is a separate question.

Which of these sit in the contract, and which sit with an Agent In ERC-3643, an administrator role with special powers over the token, such as forced transfers. See the glossary, is a design choice you make with counsel.

Two limits from the spec. Minting (creating new tokens) and forced transfers check eligibility only for the receiver. And a pause stops ordinary transfers, while the agent’s privileged actions may stay available.

… cannot be permissionless like utility tokens; they must be permissioned to track ownership.

The ERC-3643 specification, on security tokens

Permissionless means no prior approval is needed; a utility token only gives access to a service from its issuer. The spec’s line is an engineering view, not a legal status.

ITEM GET

A standard is not the law

A standard can build in controls a register needs. It can’t, by itself, give the record legal effect; that depends on the governing law.

I compare ERC-3643 with ERC-1400 and CMTAT in this side-by-side, and the full interface is on the ERC-3643 page.

Sources: ESMA TRV Risk Monitor No. 2/2026, ERC-3643.

STAGE CLEAR

What you now know

  • Why ESMA finds that wrapping keeps only part of what tokenisation promised.
  • How the same transfer moves a token in one model and a register entry in the other.
  • Which register jobs a token contract may take on, and why that alone doesn’t give its record legal effect.

Check yourself

Tap or click a question to see the answer.

An issuer pauses its native ERC-3643 token during an incident. Can its agent still move tokens?

Possibly. Per the spec, a pause stops ordinary transfers, but the agent’s privileged actions, such as a forced transfer, may stay available. Review them on their own.

Next stage:Which law decides whether an on-chain record makes you the owner, in France, the EU and the US?6 min
Adam Boudjemaa
Adam Boudjemaa

Former CTO of Integra. Named author (1 of 5) of ERC-3643, first author of ERC-6960, co-author of ERC-7410, and co-author of ERC-8203, which is still a draft. Building production AI and regulated Web3 systems.

Have a project to ship or a role to fill?

Discuss your project or role
LinkedInTwitterGitHub
Follow the engineering notes

Get new articles on production AI and smart contracts by email.