Tokenization Engine
Create and operate permissioned assets with reusable identity and issuer-controlled access.
From an asset to an operating token
The Tokenization Engine brings together asset contracts, investor identity, issuer tools, and transaction workflows. It supports the work that continues after a token is created: admitting investors, maintaining asset information, applying transfer controls, and recording operations.
Each issuer can operate multiple token suites. A suite uses ERC-3643 through the T-REX contracts to connect token balances with identity and compliance checks. Investor identities can be reused, while each suite retains its own admission and eligibility requirements.
What the engine provides
| Area | Purpose |
|---|---|
| Asset tokens | Deploy a suite and configure its token and operating roles |
| Investor access | Combine reusable identity claims with issuer-controlled admission |
| Asset information | Associate a token with its issuer, classification, metadata, and documents |
| Operations | Support issuance, transfers, freezes, recovery, and other authorized actions |
| Offerings | Coordinate subscriptions, agreements, payments, and delivery |
| Secondary trading | Support signed sell orders and on-chain settlement where enabled |
| Integration | Connect portals and applications to platform workflows and indexed chain data |
Who controls what?
The issuer controls admission to its assets and performs authorized token operations. Organization membership governs access to the issuer workspace; contract permissions govern what a wallet can execute on-chain.
The platform coordinates identity verification, claims, deployment jobs, and supporting services. In the platform deployment model, the issuer receives ownership of the token, identity registry, and modular compliance contracts. Required-topic and trusted-issuer registry authority remains with the platform.
Investors hold asset tokens in their designated wallets. Personal wallets and existing Safe multisignature wallets have different approval flows. A platform session does not replace a wallet signature or the approvals required by a Safe.
Choose a reading path
- Issuers: follow the issuer workflow from workspace setup to ongoing operations.
- Investors: follow the investor workflow from identity verification to holding and transferring tokens.
- Integrators: use the integration overview to understand service boundaries and transaction state.
Scope and availability
Self-service issuer onboarding is testnet-specific. Deployment, public directory listing, and market activation are separate decisions. Start with the tested developer guide, configuration reference, or trust model. Remaining coverage gaps are listed in Documentation status.