What is ERC-7943 (uRWA), the Ethereum standard for real-world asset tokenization?

ERC-7943 (uRWA) is Ethereum’s Final standard for tokenizing real-world assets: a minimal, vendor-neutral interface adding compliance primitives (transfer checks, freezing, forced transfers) to ERC-20/721/1155 tokens. Authored by Brickken’s Dario Lo Buglio; Stobox is a backer.

ERC-7943 answers one question the base token standards never did: how do you put a regulated asset on-chain without inventing a proprietary compliance stack every time? It standardizes the primitives and leaves the rules to you.

Why

A plain ERC-20, ERC-721, or ERC-1155 token moves freely to anyone. A real-world asset — a security, a fund, a property interest — cannot. It has to restrict who may hold it, be freezable, and support a forced transfer for a court order or recovery. Until ERC-7943, every issuer and platform solved that differently, which meant vendor lock-in and no interoperability.

ERC-7943 — “uRWA,” the Universal Real World Asset Interface — fixes that with a deliberately minimal interface layered on top of the existing token standards. It defines the compliance surface and nothing else, so it stays unopinionated about your identity provider, jurisdiction, or compliance logic. The interface has three core pieces:

• Transfer control (views): canSend, canReceive, and canTransfer let anyone check whether an account may send, may receive, or whether a specific transfer is allowed — before it happens.
• Freezing: setFrozenTokens freezes or unfreezes an amount (or token id); getFrozenTokens reads it. Frozen assets can’t move.
• Enforcement: forcedTransfer moves assets without the holder’s signature — the primitive for a court order, a recovery, or a sanctions action.
• Events: ForcedTransfer and Frozen make every enforcement action auditable on-chain.

It ships as parallel interfaces for fungible, non-fungible, and multi-token assets, so the same compliance model works whether the RWA is a security, a property NFT, or a basket.

The edge cases

Minimal is the point, and the limit. ERC-7943 standardizes that a token can gate transfers, freeze, and force-transfer — not how you decide eligibility. Identity, KYC, jurisdiction rules, and the actual allow/deny logic still live in your implementation (an off-chain KYC provider writing on-chain attestations, an identity registry, or a policy engine). The standard is the socket; you supply the compliance.

How it relates to ERC-3643. ERC-3643 (T-REX) is a fuller, opinionated framework with a built-in on-chain identity registry (ONCHAINID) and compliance modules. ERC-7943 is the lighter, universal alternative: it keeps naming compatibility (its canTransfer and forcedTransfer align with ERC-3643) but intentionally leaves identity and compliance unspecified. Think of ERC-3643 as a complete system and ERC-7943 as a shared interface many systems can implement — useful when you want portability across tools rather than one vendor’s full stack.

Final means frozen. ERC-7943 reached Final status, so its interface, events, and error definitions are fixed and production-ready across Ethereum and EVM chains. Adoption is real: CMTA integrated it into its CMTAT reference implementation (v3.2.0), and it has been demonstrated against compliance tooling in the wider ecosystem.

Who built it, and who backs it

ERC-7943 was authored by Dario Lo Buglio (@xaler5), a co-founder of Brickken, together with Tino Martinez Molina and Mihai Colceriu. Lo Buglio initiated the proposal on Ethereum Magicians in 2025, and it was refined through open community review before reaching Final status.

Around it formed a coalition of RWA platforms and infrastructure providers backing the standard — including Stobox, Brickken, DigiShares, Bit2me, Casper Network, CMTA, Compellio, Dekalabs, Forte, FullyTokenized, Propchain, RealEstate.Exchange, and Zoth, with Hacken and QuillAudits as security and audit partners. Stobox is a backer and founding coalition member of ERC-7943, and has committed to implementing it in its STV3 protocol — Stobox did not author the standard; it supports and adopts it.

What this means for your structure

If you are choosing how to make a tokenized asset compliant on-chain, ERC-7943 is the interoperability play. Building to it means your asset speaks a common compliance language that custodians, venues, and tooling can recognize, instead of a proprietary format only your vendor understands. Pair it with your own eligibility and identity layer, and keep the enforcement powers — freeze, forced transfer, and the keys behind them — governed and disclosed, because those are exactly the functions a regulator and your holders will ask about.

Gene Deyev’s take

The future of tokenization depends on building an interoperable and trusted framework for the issuance and management of real-world assets. ERC-7943 is a crucial step in ensuring institutional trust, transparency, and long-term scalability, and we are proud to back it and to implement it in STV3. I have watched the industry lose years to proprietary, vendor-locked compliance stacks — a shared, minimal interface is how you avoid repeating that. It does not decide your compliance rules for you, and it should not; it makes sure the asset can enforce whatever rules you and your counsel set, in a way the rest of the ecosystem can read.

— Gene Deyev, CEO & Co-Founder, Stobox. Co-author of the Stobox Tokenization Framework and the STV3 protocol; ERC-7943 backer; SEC Crypto Task Force roundtable participant (2025).

Related questions

• ERC-3643 vs ERC-7943 — the fuller framework vs the minimal universal interface.
• How do you enforce compliance on-chain at transfer time? — where these primitives run.
• What if the platform disappears? — why an open standard beats a proprietary format.

Last updated: 2026-07-12.