Token suites
How a group of contracts manages an asset token and its rules.
What is a token suite?
A token suite is the group of contracts behind a permissioned asset token. In the issuer portal, the suite's roles and rules are on the asset's Rules & roles tab. Real's Tokenization Engine uses T-REX, an implementation of the ERC-3643 permissioned-token standard. T-REX ties token balances to identity checks and configurable transfer rules.
The token represents the asset according to its terms. The other contracts in the suite decide three things: which identities the suite recognizes, which attestations it accepts, and which extra rules apply to operations.
The parts of a suite
| Component | Responsibility |
|---|---|
| Token | Records balances and handles transfers and authorized token operations |
| Identity Registry | Associates wallets with identities and checks the required claims |
| Identity Registry Storage | Stores wallet-to-identity associations and a country field |
| Claim Topics Registry | Defines which kinds of claim the suite requires |
| Trusted Issuers Registry | Defines which claim issuers are accepted for each kind of claim |
| Modular Compliance | Applies additional configured rules to token operations |
Real's jurisdiction rules use trusted jurisdiction claims, not the storage contract's country field. See jurisdiction.
How the parts work together
For an ordinary transfer, the token checks its own operational conditions and then asks the identity and compliance contracts. The recipient must meet the suite's identity requirements, and the proposed transfer must pass the applicable rules. Identity and eligibility explains why these are two separate checks.
Ownership and operation
Contract owners and agents have different responsibilities. The owner usually controls configuration and role assignment, where the contract allows it. Agents perform the operations their roles allow, such as registering identities or minting, burning, and freezing tokens.
A role on one contract does not give the same role on the other contracts in the suite.
Good to know
When the platform deploys a suite, the issuer wallet owns three contracts: the token, the identity registry, and the compliance module. The issuer wallet also gets the token agent and identity-registry agent roles. The platform keeps control of the Claim Topics Registry and the Trusted Issuers Registry. This is the platform's ownership model. ERC-3643 does not require it.
Privileged operations have their own permission checks and can follow different rules from ordinary investor transfers. Asset operators should know who holds those powers and what the asset's terms permit.
What is shared across assets?
Assets can share identity infrastructure and still keep their own rules: an investor can reuse one ONCHAINID, but each suite decides which claims count. See identity and eligibility.