Platform · Tokenization
Securities that enforce their own rules
Unykorn issues permissioned security tokens on the ERC-3643 (T-REX) standard. Every transfer is validated against an on-chain identity registry and a set of modular compliance rules, so an ineligible holder simply cannot receive the asset.
What standard does Unykorn use for tokenized securities?
ERC-3643 (T-REX), the institutional standard for permissioned security tokens. Identity is anchored with ONCHAINID attestations, holdings are tracked in an on-chain cap table, and transfer eligibility is decided by an IdentityRegistry plus a ModularCompliance rule set evaluated on every canTransfer check.
How is compliance enforced on a transfer?
At the token boundary, before value moves. When a transfer is attempted, the token queries the identity registry (is the recipient verified?) and the compliance modules (does this transfer satisfy jurisdiction, lock-up, holder-cap, and eligibility rules?). If either fails, the transfer reverts. Compliance is a gate, not an after-the-fact report.
Who controls investor identity keys?
The investor. Each holder controls their own ONCHAINID, keeping the model non-custodial at the identity layer. Issuers and agents hold scoped roles for registration and lifecycle operations, and a forced-transfer path exists strictly for key-recovery and lawful-order scenarios — auditable and role-gated.
Frequently asked
What is ERC-3643?
ERC-3643 (the T-REX standard) is an EVM standard for permissioned security tokens. It binds every transfer to an on-chain identity registry and modular compliance rules, so only eligible, verified holders can hold or receive the token.
Can a non-KYC wallet hold a Unykorn security token?
No. Transfers to an unverified identity fail the canTransfer check and revert. Eligibility is enforced on-chain at the token boundary.