Labs
Tokenization lifecycle
Run issuance, subscription, transfer, distribution and redemption against a small ledger. Inspect which participant can act and what changes.
Fictional educational scenarios. No wallet connection, live transaction or investment recommendation.
Choose a scenario
Changing scenario starts a fresh run and clears the assessment.
The fictional recipient/buyer passes this scenario’s stipulated holding and transfer checks. This is not real eligibility verification.
Reset restores all initial balances, scenario, inputs and learning-check state. Nothing is saved or sent.
Scenario assumptions
- A fictional redeemable claim has 100 units at USD 10 each. The issuer begins with USD 1,000 and the investor with USD 2,000. No named asset or jurisdiction is represented.
- One subscription and one optional transfer precede a single USD 0.50 per held unit distribution. Redemption pays USD 10 per held unit and burns only those units. Unsubscribed units remain issued inventory.
- The distribution is a stipulated cash event funded from issuer cash, not an APY or promised return. A pause is an operational incident; recovery restores processing, not legal solvency.
Participants and responsibilities
Issuer creates and services claims; investor pays subscription cash; transfer agent checks the recipient; recipient receives transferred units and subsequent cash events.
Holder claim
Only the stated contractual redemption and distribution rights are simulated. A token balance alone does not establish ownership of an unspecified underlying asset.
Failure and recovery
Try transferring to the restricted recipient or acting during a servicing pause. Rejection preserves the cash and unit ledger.
Simulation ledger
Current state:Draft contract
- Issued units remaining
- 0 units
- Investor units
- 0 units
- Recipient units
- 0 units
- Investor cash
- $2,000.00
- Recipient cash
- $0.00
- Issuer cash
- $1,000.00
- Distribution paid
- $0.00
Latest result · Scenario update
A fresh scenario is ready. Read its assumptions, then run an action.
Run the mechanism
Actions follow the contract. You can try a blocked action to inspect why it is rejected; rejected actions preserve the ledger.
Check your understanding
What does a completed subscription establish in this scenario?
Attempts: 0