@ApexGlobalGroup, @Chainlink, @trex_network and the ERC-3643 Association have implemented a modular compliance framework for onchain bonds, aligned with Swift standards.
As part of the initiative, Swift has joined the ERC-3643 Association.
Full announcement:
ICYMI: We have revamped our website!
- A new look at the standard
- Better in-depth info on how it works
- Solutions pages on who it benefits and how
- Who is building on the standard already
- and more...
Have a look here: erc3643.org
Welcome to the Association, Zenith.
The standard gets stronger with every member working on what happens after issuance: settlement, collateral and moving across environments with the rules intact.
Zenith has joined the ERC3643 Association, bringing our experience in interoperability standards and settlement design to the work on compliant tokenization.
@ERC3643Org was originally created in 2018 as the T-REX (Token for Regulated EXchanges) protocol by Tokeny Solutions. ERC-3643 is an open-source token standard for the issuance, management and transfer of permissioned tokens. It enables issuers to enforce compliance requirements, including investor eligibility and transfer restrictions, even on public blockchains. The ERC3643 Association brings together TradFi institutions and blockchain technology providers to advance the adoption of this standard. Its founding members include: Apex Group, @ArchaxEx , @BitstampSupport, @Capgemini, @DLA_Piper, @InvescoUS, @0xPolygon Labs, @TokenySolutions, and others.
This matters because tokenizing a regulated asset is only the beginning. Once issued, these assets need to participate in financial workflows involving settlement, collateral, lending, and trading, often across different applications and environments.
That second step is what Zenith is built for. As the EVM and SVM extension for @CantonNetwork, Zenith allows Solidity applications to interact atomically with Canton-native assets and workflows. This opens a path for applications using Ethereum standards such as ERC-3643 to connect with Canton's institutional financial infrastructure while retaining their established Ethereum tooling.
We look forward to working with the Association and its members as regulated tokens move into production.
More about the ERC3643 Association and its members: erc3643.org/members
Zth.
We use ERC-3643 because eligibility has to travel with the asset.
A proprietary format has to be integrated venue by venue. A standard gets read by anything that already supports it.
140+ institutional members sit behind it. That is what separates a standard from a proposal.
Compliance that travels.
T-REX x @Chainlink
CCIP moves it, ACE enforces it, Data streams prices it
ERC-3643 compliance, coming to the 60+ chins CCIP connects.
ERC-3643 is released under CC0.
You can implement it, fork it, and never speak to us. No membership, no license, no fee. A standard that can be adopted without permission is the only kind that can be tested by people ho owe us nothing.
A credit rating is issued once and read by every lender.
No bank re-rates the borrower at its own desk.
ERC-3643 gives investor eligibility the same shape: issued by an accountable party, read wherever the investor shows up.
Good tooling matters. OpenZepelling's RWA Wizard now generates contracts that follow ERC-3643 for Stellar.
The interfaces were written for the EVM. The model travels: verified identities, transfer-time compliance, issuer control.
Five years ago this month, the proposal was merged into the EIPs repository as pull request 3643.
The number stuck.
It reached Final in December 2023 and it has been free to implement for anyone ever since. 🫂
RWA security is not an ERC-20 review with extra steps.
$38B already live. $355B represented. Almost all of it sits on three standards:
3643: identity + freeze/force
4626: share price + rounding
7518: partitions + lock math
This is the attack surface. Checklists in the thread 👇
Nethermind has joined @ERC3643Org, the standard for identity and compliance in regulated tokenised assets.
Our work with it has focused on privacy: proving compliance without unnecessarily exposing identities, balances, or transaction history.
Good to see ERC-3643 and T-REX referenced in GL1’s paper on programmable compliance.
Putting a regulated asset on-chain is only the start.
The infrastructure must verify who can hold it, approve or reject each transfer and keep those checks working wherever the asset moves.
Tokenized assets move between institutions that have never transacted before. Who verifies the entity on the other side?
A new Global Layer One white paper, written with the @IMFNews, @BIS_Org Innovation Hub, @MAS_SG, @JPMorgan, @StanChart, @Chainlink, and GLEIF, makes verifiable identity the starting point. The #vLEI lets an organization assert an identity that a counterparty can computationally verify.
Read it: global-layer-one.org/pdf/gl1…
Institutional tokenization is a multi-chain reality, and for it to work at scale, compliance needs to travel with the tokenized asset.
Join our President, @RealDennisO, as we host a live conversation on X Spaces with @mssteuer, President & CTO of @Casper_Network and @0xMuchScience, CTO & Co-founder of @trex_network, on the compliance and identity layer across EVM and Non-EVM chains.
🗓️ June 3 at 11:00 EST
We look forward to the insightful conversation.
Save in your agenda: x.com/i/spaces/1DGLddYRXOmGm…