ERC-3643 vs ERC-7943
Both make a security token enforce its own compliance – only verified, eligible wallets can hold or move it. The difference is philosophy: a complete identity framework versus a lean, vendor-neutral interface. Written by a contributor to ERC-7943.
The short version
ERC-3643 (T-REX) is the proven incumbent: a full permissioned-token framework with its own on-chain identity system, ~$32B tokenized, strongest in institutional white-label deployments. ERC-7943 (uRWA), finalized in 2026, is the neutral second generation: a minimal interface that delivers the same on-chain enforcement while letting each implementation choose its identity source – which is how Stobox Compass issues tokens that read eligibility from attestations without ever storing identity documents. They will coexist; pick by ecosystem, not by hype.
| ERC-3643 (T-REX) | ERC-7943 (uRWA) | |
|---|---|---|
| What it is | The incumbent permissioned-token framework (T-REX), authored by Tokeny and recognized as an Ethereum standard in 2021. | A leaner, vendor-neutral interface for regulated real-world-asset tokens (uRWA), finalized in 2026 with contributions from across the industry – including Stobox. |
| Design philosophy | A full framework: the token ships with its own on-chain identity system (ONCHAINID), an identity registry mapping wallets to verified identities, and pluggable compliance modules. | A minimal common interface: the token exposes standard permissioning hooks and leaves identity mechanics to the implementation – so eligibility can come from attestation layers, registries, or credentials. |
| How eligibility is checked | The token queries its identity registry: does this wallet map to an ONCHAINID with the required claims (KYC, accreditation, jurisdiction)? | Implementation-defined. In Stobox Compass, the token reads a verified yes/no attestation (EAS / Coinbase Verifications) – no platform stores identity documents, and verification is reusable across assets. |
| Enforcement | Transfers that fail identity or compliance checks revert on-chain. Recovery and forced-transfer mechanics included. | Same guarantee – ineligible transfers revert on-chain; freeze and enforcement actions are part of the interface. |
| Adoption | The most-adopted standard of the first generation – roughly $32B in tokenized assets; governed by the ERC-3643 Association (members include Apex Group, Polygon, Invesco, major law firms). | The emerging second generation – finalized 2026, backed by multiple platforms (Stobox, Brickken, DigiShares, CMTA and others), designed to be the neutral common denominator. |
| Who uses which | Institutional white-label deployments, especially in the Tokeny/Apex ecosystem. | Platforms that want compliance guarantees without adopting one vendor's identity stack. Stobox Compass issues ERC-7943 tokens on Base. |
Context: permissioned token standards ·Stobox vs Tokeny (ERC-3643's author) ·how Compass issues on ERC-7943
Questions this raises
Answered plainly.
Do ERC-3643 and ERC-7943 do the same job?
At the guarantee level, yes: both make a security token enforce its own compliance – only eligible, verified wallets can hold or receive it, and ineligible transfers fail on-chain. They differ in how much machinery the standard prescribes: ERC-3643 ships a complete identity framework (ONCHAINID + identity registry + compliance modules); ERC-7943 defines a minimal interface and lets implementations choose their identity source.
Is ERC-7943 replacing ERC-3643?
No – and anyone who tells you otherwise is selling something. ERC-3643 has years of production history and roughly $32B tokenized on it, with an institutional association behind it. ERC-7943 is the newer, leaner, vendor-neutral layer that multiple platforms – including ones that also use ERC-3643 – converged on in 2026. Expect both to coexist, the way multiple database engines do.
Why does Stobox issue on ERC-7943?
Two reasons. First, neutrality: ERC-7943 doesn't bind the token to any single vendor's identity system, which fits Stobox's open-standards architecture (Base, USDC, EAS, ERC-4337 wallets – every layer has a documented alternative). Second, privacy: eligibility is read as a verified yes/no attestation, so Stobox never stores investor identity documents. Stobox is a backer of the standard and issues on it via Compass.
Does the standard choice matter to my investors?
Mostly it's invisible to them – either way they verify once and receive a token that enforces its own transfer rules. It matters to you as the issuer: which ecosystems and wallets the token works with, whether you're tied to one vendor's identity registry, and how eligibility verification is reused across offerings. ERC-3643 facts reflect public sources as of July 10, 2026 (the EIP, the ERC-3643 Association, and adoption figures published by its ecosystem); T-REX is a trademark of its owner. General information, not legal advice – see Legal & disclosures .
Primary sources: ERC-3643, the T-REX permissioned token standard – EIP-3643 · ERC-7943, the universal RWA interface (uRWA) – EIP-7943.
