XAUT Market Cap: $2.8B ▲ Tether Gold | PAXG Market Cap: $2.5B ▲ Paxos Gold | Gold Token TVL: $5.5B+ ▲ +180% YoY | UAE Gold Trade: $75B+ ▲ Annual Volume | Islamic Finance: $4.5T ▲ Global Assets | VARA Licensed: 23 Entities ▲ +8 in 2025 | DGCX Volume: $18B+ ▲ Annual | Sukuk Issued: $1T+ ▲ Cumulative | XAUT Market Cap: $2.8B ▲ Tether Gold | PAXG Market Cap: $2.5B ▲ Paxos Gold | Gold Token TVL: $5.5B+ ▲ +180% YoY | UAE Gold Trade: $75B+ ▲ Annual Volume | Islamic Finance: $4.5T ▲ Global Assets | VARA Licensed: 23 Entities ▲ +8 in 2025 | DGCX Volume: $18B+ ▲ Annual | Sukuk Issued: $1T+ ▲ Cumulative |
HomeEncyclopedia › ERC-3643

ERC-3643

Definition

ERC-3643 is an Ethereum token standard designed for compliant security tokens and regulated digital assets. It embeds identity verification and transfer restriction logic directly into the smart contract, enabling regulatory compliance at the protocol level rather than relying on off-chain enforcement. Originally developed by Tokeny Solutions under the name T-REX (Token for Regulated EXchanges), ERC-3643 was formally adopted as an Ethereum Improvement Proposal and has become the most widely deployed standard for regulated tokenized assets.

In the UAE’s commodity and traditional asset tokenization ecosystem, ERC-3643 addresses the fundamental challenge of reconciling blockchain’s open, permissionless architecture with the regulatory requirements imposed by VARA and ADGM. Commodity token issuers, tokenized bond platforms, and Shariah-compliant token projects operating under UAE regulation require a token standard that prevents unauthorized transfers while preserving the operational benefits of blockchain settlement.

Architecture

ERC-3643 extends the basic ERC-20 token standard with four additional smart contract components:

Identity Registry. An on-chain registry that maps Ethereum wallet addresses to verified digital identities. Each registered address is associated with an identity contract (following the ERC-734/735 standard for claims) that stores verifiable credentials issued by trusted claim issuers. In the UAE context, these credentials typically include KYC/AML verification status, investor accreditation level, and jurisdictional eligibility.

Compliance Smart Contract. A modular contract that defines the rules governing token transfers. Before any transfer is executed, the compliance contract checks whether both the sender and receiver meet the eligibility criteria. These rules can encode investor accreditation requirements, maximum holder limits, jurisdictional restrictions, and holding period lockups. The compliance contract can be updated by the token issuer to reflect changes in regulatory requirements without modifying the token contract itself.

Trusted Claim Issuers. Entities authorized by the token issuer to verify and attest to investor credentials. In a UAE commodity tokenization context, trusted claim issuers might include licensed identity verification providers, regulated banks that have completed KYC on the investor, or VARA-approved compliance service providers.

Identity Storage. The on-chain storage contract that maintains the mapping between wallet addresses and identity claims. This contract is managed by the identity registry and provides the data layer that the compliance contract queries during transfer validation.

How Transfer Validation Works

When a token holder attempts to transfer ERC-3643 tokens, the following validation sequence executes on-chain:

  1. The token contract calls the compliance contract with the transfer details (sender, receiver, amount).
  2. The compliance contract queries the identity registry to retrieve the identity claims for both the sender and receiver addresses.
  3. The compliance contract evaluates the transfer against its defined rules — checking investor status, jurisdictional eligibility, and any transfer restrictions.
  4. If all checks pass, the transfer executes. If any check fails, the transfer is rejected at the smart contract level.

This on-chain validation means that non-compliant transfers are technically impossible, not merely prohibited by terms of service. The blockchain itself enforces the regulatory requirements, which is a significant advantage for regulated environments like VARA’s VASP framework and ADGM’s digital asset framework.

UAE Regulatory Relevance

ERC-3643’s compliance architecture directly addresses several UAE regulatory requirements:

VARA Requirements. VARA mandates that licensed exchanges and custody providers implement transfer controls preventing unauthorized access to virtual assets. ERC-3643’s built-in transfer restrictions satisfy this requirement at the protocol level, ensuring that only verified investors can hold or trade the tokens.

ADGM Requirements. ADGM’s FSRA imposes securities-style investor protection requirements for digital assets classified as securities or financial instruments. ERC-3643’s accreditation checking ensures that tokenized bonds and tokenized sukuk are only accessible to appropriately qualified investors.

AML/CFT Compliance. Both VARA and ADGM require comprehensive anti-money laundering and counter-terrorism financing controls. ERC-3643’s identity registry provides an on-chain compliance layer that supplements traditional off-chain AML systems, creating a verifiable record of investor identity verification.

Application to Commodity Tokens

For commodity tokens in the UAE market, ERC-3643 provides several specific benefits:

Gold Token Compliance. Gold-backed tokens like XAUT and PAXG currently use standard ERC-20 contracts without built-in compliance. Future gold token issuers operating under VARA or ADGM licensing may adopt ERC-3643 to embed regulatory compliance directly into the token, particularly if they offer products targeting institutional investors who require regulated custody.

Cross-Border Transfer Control. UAE-regulated commodity tokens may face restrictions on transfers to investors in certain jurisdictions. ERC-3643’s compliance contract can enforce these jurisdictional limits automatically, preventing tokens from reaching wallets associated with sanctioned or restricted territories.

Shariah Compliance Layer. For Shariah-compliant tokens, the compliance contract could theoretically enforce Shariah-specific rules — such as preventing transfers that violate sarf (currency exchange) timing requirements or restricting trading during specific periods. However, this application remains experimental and would require Shariah governance board approval.

Comparison with Other Standards

ERC-3643 is not the only compliant token standard, but it is the most widely deployed. Alternatives include:

ERC-1400. A security token standard that provides partition-based token management, useful for tranched structures like senior/subordinate bond classes. ERC-1400 focuses on document management and partition controls but does not include ERC-3643’s built-in identity verification.

ERC-1404. A simpler restriction standard that allows transfer validation but without the identity registry architecture. Suitable for basic compliance needs but less comprehensive than ERC-3643.

Proprietary Standards. Some tokenization platforms, particularly those built on permissioned blockchains like R3 Corda or Hyperledger Fabric, implement proprietary compliance mechanisms that are not interoperable with Ethereum-based tokens.

For UAE commodity token issuers deciding between standards, the ADGM digital asset framework and VARA commodity VASP licensing guidance should inform the choice based on the specific regulatory classification and compliance requirements of the token.

See Also

Policy Intelligence

Full access to legislative analysis, country profiles, and political economy research.

Subscribe →

Institutional Access

Coming Soon