Static analysis of token contract metadata for regulatory compliance. Paste ERC-3643 (T-REX security token) or ERC-1400 contract metadata JSON. Checks identity registry linkage, compliance contract, claim topic lists, forced transfer provisions, recovery addresses, and partition-level restrictions. Maps to ESMA, SEC, SAMA, and MAS regulatory frameworks.
ERC-3643 (T-REX): The T-REX standard requires: identityRegistry (on-chain investor KYC registry), compliance contract (enforces transfer restrictions), claimTopics list (defines required investor claims e.g. KYC=1, accredited=7, country=23), forced transfer capability (required for regulatory recovery), and recovery address. This tool validates these against the metadata JSON you provide.
ERC-1400: The ERC-1400 standard requires: isIssuable() function, canTransfer() pre-check, transferWithData() for regulatory data, partition-level restrictions, and controller list for regulatory forced transfer.
Jurisdictional mapping: ESMA/MiCA requires investor claims for all transfers; SEC requires accredited investor status (Reg D) or offshore confirmation (Reg S); SAMA requires Saudi resident status claim; MAS requires CMS license holder counterparty verification for capital markets products.
Canton reference: For Canton-deployed tokenized US Treasury compliance handling, see the Digital Asset Canton A2A documentation on the Global Synchronizer and DTCC ComposerX integration.