Can ERC-3643 Become an ISO Standard?
ERC-3643 is a Final Ethereum standard for permissioned security tokens and is now the subject of an ISO standardization initiative. The proposal is moving through ISO/TC 307 in coordination with ISO/TC 68, but ERC-3643 is not yet an ISO standard and the organizers have published no completion date.
TL;DR — Key Takeaways
- ✓Current status: ERC-3643 is Final as an Ethereum ERC, not as an ISO standard.
- ✓The route: A Spanish committee is advancing an NWIP through ISO/TC 307 with ISO/TC 68 coordination.
- ✓The draft: Working Group GT4 is preparing an English Committee Draft for international review.
- ✓The benefit: ISO status could make the specification easier to cite in procurement, audit, and policy.
- ✓The limit: Standardization cannot certify an implementation, license an issuer, or settle local securities law.
The ISO Initiative Is a Proposal, Not an Approval
The ERC3643 Association announced the initiative on 20 November 2025. A national committee is preparing a New Work Item Proposal, while Working Group GT4 is drafting text in English for broader expert participation.
That status matters because an Ethereum Request for Comments and an ISO standard answer different questions. ERC Final status means the interface completed Ethereum's standards process. ISO publication would add an international consensus process with national delegations, committee ballots, comments, and revisions.
The initiative will submit a “New Work Item Proposal” through ISO/TC 307 in coordination with ISO/TC 68.
— ERC3643 Association, November 2025
Until that process completes, procurement teams should describe the work as an ISO standardization initiative. Calling ERC-3643 “ISO-certified” or an “ISO standard” would overstate its current status.
TC 307 and TC 68 Bring Different Review Lenses
ISO/TC 307 supplies the blockchain and distributed-ledger standards route, while ISO/TC 68 supplies the financial-services context. The combination can test both the token interface and its fit with established market identifiers, messaging, and control practices.
| Body | Role in the initiative | Institutional question |
|---|---|---|
| Spanish national committee | Initiates the proposal | Is the work mature enough to begin? |
| ISO/TC 307 | Blockchain and DLT standards route | Are interfaces and terminology interoperable? |
| ISO/TC 68 | Financial-services coordination | Does the model fit market infrastructure? |
| GT4 and contributors | Develop and review draft text | Can different jurisdictions implement it consistently? |
The initiative names ANNA, INATBA, and European standards bodies CEN/CENELEC as contributors. Their involvement can broaden the draft, but it is not the same as final approval by ISO members.
ISO Status Would Change Procurement More Than Code
An ISO reference could let banks, custodians, and public bodies specify a common permissioned-token interface without naming a vendor. The immediate value is shared requirements and test language, not a different transfer function.
ERC-3643 already defines identity registries, trusted claim issuers, transfer pre-checks, recovery, freezes, forced transfers, minting, and burning. ISO review can formalize terms, conformance boundaries, and cross-standard mappings, but an issuer would still deploy and govern those functions.
That is why the initiative belongs inside a broader RWA token standards decision. A referenced standard reduces specification ambiguity; it does not replace legal opinions, custody controls, or operational testing.
An ISO Number Would Not Certify Every ERC-3643 Token
Conformance to an interface does not prove that privileged keys, identity providers, upgrade rights, or compliance rules are safe. Those choices sit in each issuer's implementation and governance documents.
The distinction is especially important because ERC-3643 exposes powerful agent functions. An implementation can conform while allowing one key to freeze holdings, force transfers, mint, burn, or recover assets. Our analysis of ERC-3643 agent-key governance covers that off-spec risk.
- ISO publication would not authorize a securities offering.
- It would not certify a specific smart-contract deployment.
- It would not select trusted identity or claim issuers.
- It would not set multisig, timelock, or upgrade policy.
- It would not resolve conflicts between jurisdictions.
ERC-7943 Shows Why the Draft Cannot Freeze the Market
ERC-7943 is also Final and defines a smaller universal RWA interface. It standardizes common transfer checks and enforcement actions without requiring ERC-3643's full identity-registry and role architecture.
ERC-7943 stays “minimal and not opinionated about specific implementation details.”
— Ethereum ERC-7943 specification
The two standards are not exact substitutes. ERC-3643 specifies a broader permissioned-security stack; ERC-7943 gives wallets and protocols a common surface across different RWA implementations. The detailed comparison appears in our ERC-7943 uRWA guide.
For ISO work, the design challenge is to standardize a useful baseline without making one 2025 architecture the permanent ceiling. Versioning and extension rules will matter as much as the first published text.
Issuers Should Build a Versioned Conformance Plan Now
Institutions do not need to wait for ISO publication, but they should avoid hard-coding a procurement claim they cannot update. A versioned control map can separate today's ERC conformance from future ISO requirements.
| Control | Evidence now | Future ISO mapping |
|---|---|---|
| Interface support | Contract tests against ERC-3643 | Clause-level conformance matrix |
| Identity | Claim issuer and registry policy | Mapped terminology and assurance levels |
| Privileged roles | Key, multisig, and recovery policy | Any governance requirements in final text |
| Change management | Upgrade and migration procedure | Tracked draft-to-final differences |
The defensible statement today is narrow: ERC-3643 is a Final Ethereum standard undergoing an ISO standardization initiative. Everything beyond that should wait for a published ISO document and a defined conformance method.
Frequently Asked Questions
Is ERC-3643 already an ISO standard?
No. ERC-3643 is a Final Ethereum standard, while the ISO initiative is still a proposal moving through a New Work Item Proposal and Committee Draft process. The organizers have not published a completion date.
Which ISO committees are involved in the ERC-3643 initiative?
The initiative was started through the Spanish national correspondent committee of ISO/TC 307, which covers blockchain and distributed ledger technologies, in coordination with ISO/TC 68 for financial services.
What would ISO status change for ERC-3643?
ISO status could give procurement, audit, and policy teams a consensus standard they can cite in requirements. It would not license an issuance, approve a smart contract, or prove that an implementation is legally compliant.
What does ERC-3643 standardize?
ERC-3643 defines interfaces for permissioned security tokens, identity registries, trusted claim issuers, compliance checks, recovery, freezes, forced transfers, minting, and burning.
Does ERC-7943 compete with ERC-3643?
ERC-7943 overlaps at the interface level but has a different scope. It defines a minimal universal RWA interface and does not require ERC-3643's identity-registry architecture, so applications can support common controls without adopting the full T-REX stack.
Should an issuer wait for ISO standardization before using ERC-3643?
Not solely because of the ISO process. Issuers should select a token architecture based on current legal, custody, identity, governance, and interoperability requirements, then map future ISO changes through versioned controls.
Related Articles
How Are RWA Token Standards Evolving?
A framework for updating token controls without trapping issuers in one implementation.
Smart-Contract Compliance or Layer-0 Governance?
Where token interfaces end and system-wide governance begins.
How Does Decentralized Identity Support RWA Issuance?
The identity and attestation layer used by permissioned securities.
What Are the Best Tokeny Alternatives for RWA Governance?
Platform choices for issuers that need regulated-token controls.