ERC-3643 permissioned token issuance
PazaLabs issues every asset as an ERC-3643 permissioned security token. The standard enforces transfer restrictions in the smart contract itself, so only verified, whitelisted addresses can hold or transact the token, and every transfer is checked against identity, claims and jurisdiction rules before it settles.
ERC-3643: permissioned security tokens
ERC-3643 (T-REX) is the institutional standard for compliant security tokens on EVM chains. It enforces transfer restrictions at the smart contract level — so only verified, whitelisted addresses can hold or transact the token. Read the full ERC-3643 explained guide for identity registry, claim topics, and transfer flow.
What the standard enforces
Identity Registry
Verified holder identities stored on-chain and used to validate every transfer.
Claim Topics
Investors must hold valid claims (KYC, accreditation, jurisdiction) that expire and renew.
Transfer Rules
Configurable rules by jurisdiction, category, lock-up, or limits — executed atomically.
Forced Transfers & Recovery
Authorized issuers or regulators can force-transfer or freeze tokens for compliance.
The ERC-3643 transfer flow
- 1
Sender initiates transfer
Token holder calls transfer() with recipient address.
- 2
Identity check
Contract queries Identity Registry: is recipient verified?
- 3
Claim validation
Are all required claims valid and unexpired?
- 4
Transfer rules check
Do jurisdiction, category, and lock-up rules pass?
- 5
Transfer executes
All checks pass → transfer settles on-chain.
- 6
Event logged
Transfer event emitted; compliance audit trail updated.
Ready to tokenize your assets?
Book a session with our structuring team and we'll scope the right asset class and legal wrapper for your use case.