Issuers
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. Issuers use it in the issuer portal, and investors use it in the investor portal. It handles the work that continues after a token exists: admitting investors, keeping asset information current, applying transfer controls, and recording operations.
Each issuer can run several token suites. A suite uses the T-REX contracts, which implement ERC-3643, a standard for permissioned tokens. These contracts tie token balances to identity and compliance checks. An investor can reuse one identity across suites. Identity and eligibility explains what reuse gives and what it does not give.
What the engine provides
| Area | Purpose | Where in the portals |
|---|---|---|
| Asset tokens | Deploy a suite and configure its token and operating roles | Issuer: Assets, asset tab Rules & roles |
| Investor access | Combine reusable identity claims with issuer-controlled admission | Investor: Get verified, Request access. Issuer: asset tab Investors |
| Asset information | Associate a token with its issuer, classification, metadata, and documents | Issuer: asset tab Profile & documents |
| Operations | Run issuance, transfers, freezes, recovery, and other authorized actions | Issuer: asset tab Operations |
| Offerings | Manage subscriptions, agreements, payments, and delivery | Issuer: asset tab Fundraising. Investor: asset tab Invest |
| Secondary trading | Let holders sign sell orders and settle them on-chain, where enabled | Investor: asset tab Trade |
| Payouts | Pay holders from funded on-chain distributions (how payouts work) | Issuer: Payouts. Investor: Income |
| Integration | Connect portals and applications to platform workflows and indexed chain data | Platform API |
Who controls what?
The issuer decides who is admitted to its assets and performs authorized token operations. Workspace membership and contract roles are separate; token suites explains who owns which contract.
The platform runs identity verification, claims, deployment jobs, and supporting services. On Real Testnet, identity verification is a test verification with no real KYC.
Investors hold asset tokens in their designated wallets. Personal wallets and existing Safe multisignature wallets use different approval flows. Signing in to the platform does not replace a wallet signature.
Choose a reading path
- Follow the issuer workflow from workspace setup to ongoing operations.
- Read token suites to see which contracts you own and which roles you assign.
- Use the guides for offerings, token operations, and asset information.
Real Testnet
On Real Testnet, you can onboard as an issuer yourself, create a test token, and publish your own listing in the Marketplace. Deployment, listing, and market activation are still separate steps. Start with the developer guide, the configuration reference, or the trust model.