Tokenization Structures
How Asset Tokenization Works
Map the legal, operational and technical steps connecting an asset to a token.
What you will learn
- Map issuance and redemption workflows
- Identify offchain dependencies
AI-assisted educational manuscript. The workflow and amounts are invented; they describe no live offering.
Learning objectives
- Map the path from an underlying asset to issuance and redemption.
- Separate a business approval from a ledger operation.
- Identify evidence needed at each external boundary.
From an arrangement to a record
Tokenization is a coordinated arrangement, not merely a mint function. It connects an underlying asset or claim, the rules governing that interest, and a programmable representation. The BIS framework treats these elements together. A useful implementation therefore begins with the right being represented and the parties responsible for maintaining that connection. BIS
A teaching lifecycle has six stages: define the interest; verify the asset and accountable parties; admit an eligible participant; reconcile subscription money; issue the appropriate units; service and eventually redeem the interest. This sequence is a proposed analysis model, not a mandatory sequence for every jurisdiction.
Before issuance, specify whether a unit represents debt, a fund share or another contractual relationship. Those instruments have different economics. Investor.gov explains that a mutual fund pools money into a portfolio and issues shares; holding a share is a different layer from directly holding its portfolio securities. SEC: Mutual Funds
Worked example: a subscription that arrives twice
Imagine a fictional fund with a stated subscription price of 10 currency units per share. A participant requests 2,000 of shares. The administrator confirms eligibility and sends payment instructions with reference SUB-41. A bank receipt for 2,000 is reconciled to that reference. The administrator authorizes 200 shares, and a ledger transaction records issuance.
Now the bank notification is delivered a second time. The subscription is still worth 200 shares, not 400. A unique business reference and a recorded completed issuance prevent duplicate processing. A blockchain transaction hash alone is insufficient if two different authorized mint transactions were created from the same payment.
Consider a different failure. Funds arrive but the participant's eligibility expires before issuance. The system should enter an exception state, preserve the payment evidence and route the case to a documented review or refund process. Automatically minting because money arrived would confuse two independent conditions.
Request → eligibility confirmed → money reconciled → issuance authorized
│
transaction fails? → retry same business case
│
▼
issued: 200 shares
Redemption request → units reserved → price confirmed → payout reconciled
The diagram leaves the timing of unit cancellation and payment deliberately explicit for the product designer to decide. Burning first can leave an unpaid claimant; paying first can leave transferable units. A mechanism must prevent double use while retaining evidence and recovery rights.
Reconciliation is part of the product
Maintain a relationship between the subscription record, participant identity, payment reference, authorized units and confirmed ledger result. Distinguish requested, authorized, submitted and confirmed. An unavailable node is not proof that a transaction failed; determine its authoritative status before resubmitting.
The reverse path needs equal care. Redemption is not simply a burn. Someone must determine entitlement, valuation date, available liquidity, fees, payment destination and completion. A fund's value and its particular redemption arrangement require separate examination. The cited SEC material provides fund fundamentals, not a conclusion about this imaginary tokenized fund.
Common misconceptions
“Minted means assets were verified.” A mint event establishes the recorded operation, not the quality of evidence for an external asset.
“A successful demonstration proves production readiness.” A happy path says little about duplicate notifications, failed payments or recovery.
Risks and limits
This is an educational state model. It omits real financial regulation, tax, safekeeping and finality decisions. External payment reversal, compromised authorization, stale eligibility and disagreement between registers remain possible. For each boundary, record who decides, what evidence they use and how a mistake is corrected.
Exercise and answer
Exercise: Two bank notifications refer to SUB-41, and one issuance of 200 shares is confirmed. What should a second notification do?
Answer: It should attach or match evidence to the existing subscription and preserve the completed issuance. It must not authorize another 200 shares merely because a notification was repeated.
Related learning
Continue through tokenization structures, then examine subscription state transitions in product architecture and Labs.
Source map
bis-tokenisation: BIS, arrangement-based tokenization and programmable records; international research, not legal guidance.sec-funds: SEC Investor.gov, pooled investment and fund shares; United States.
Source retrieval evidence is dated 2026-10-18 in the repository. The subscription lifecycle, duplicate event and recovery model are original teaching designs, not tested financial infrastructure.
Check your understanding
Preparing knowledge-check controls…
Your answer stays in this tab. No account or persistent completion record is created.
Source evidence
The tokenisation continuum
Retrieved: 2026-10-18 · VERIFIED OFFICIAL · VERIFIED
Mutual Funds
Retrieved: 2026-10-18 · VERIFIED OFFICIAL · VERIFIED
Related learning and research
Report an editorial correction · [email protected]
Include the page or chapter ID, the exact statement and supporting sources. Your email app opens; this site sends nothing. Do not include account details, balances, identity documents or private keys.