What's real today. The permissioned-token stack — CRC3643, IdentityRegistry, ClaimTopicsRegistry, TrustedIssuersRegistry and ModularCompliance — is implemented and covered by automated tests (crc3643.test.ts) on the real EVM. ◷ Issuer console wiring connecting this screen to a deployed deployment on the testnet RPC is the next integration step.
Issuance pipeline
1
Define claim topics
Declare the credentials investors must hold — e.g. KYC, accreditation, jurisdiction — in the ClaimTopicsRegistry.
2
Authorize trusted issuers
Whitelist the KYC providers / regulators allowed to attest each topic in the TrustedIssuersRegistry.
3
Register & verify investors
Investors get an on-chain identity (ONCHAINID-style); trusted issuers attest their claims. isVerified() turns true only when every required claim is present.
4
Issue the compliant token
Mint the CRC-3643 asset to verified holders only. Every transfer is gated by identity + ModularCompliance; agents can freeze and perform court-ordered recovery.
Compliance controls
  • KYC-gated holders — only verified identities receive tokens
  • Per-holder maximum balance caps
  • Country allow/deny rules
  • Global pause switch
  • Address freeze + court-ordered forced transfer
  • Instant de-verification when an issuer's trust is revoked
Why ERC-3643
ERC-3643 / T-REX is the institutional standard for permissioned security tokens — the framework used across a 78-member ecosystem (incl. DTCC, Fireblocks, Tokeny) with tens of billions tokenized. Speaking it natively means Cashmereum interoperates with how regulated assets are already issued.
Compliance checker
An illustrative model of the exact transfer rules enforced on-chain by CRC-3643 + ModularCompliance. Not a live chain call.
(= current + amount)