- July 7, 2026
OpenZeppelin
OpenZeppelin
As strategic technical partners, OpenZeppelin and T-REX Network are working together to co-design the next phase of the T-REX Protocol, the infrastructure layer also known as ERC-3643, the onchain compliance standard for regulated assets. The partnership focuses on hardening the Protocol's foundations and delivering ERC-3643 as a standard audited OpenZeppelin Contracts library component accessible to developers.
For institutions across asset management, banking, and capital markets, ERC-3643 brings compliance that is programmable, automatically enforced at every transfer, and built into the token itself rather than managed offchain.
Apex Group, which services $3.5 trillion in assets, has recently committed to adopting the T-REX Ledger as its default infrastructure, with a target of $100 billion in tokenized assets by June 2027. OpenZeppelin, with over $35 trillion in value transferred through its contracts, is now adding its established security foundation to the infrastructure carrying those assets.
What OpenZeppelin and T-REX Network Are Building
- Protocol architecture and security hardening
- ONCHAINID evolution for cross-chain identity, including an SDK for developers integrating frontends with an ONCHAINID smart account
- ERC-3643 as an audited OpenZeppelin Contracts library component
- Expansion to non-EVM networks, with a Stellar-native implementation already complete
- Ecosystem integrations with Zama for privacy-preserving encryption
The foundation of the T-REX Protocol is ERC-3643, an onchain compliance standard that embeds rules, transfer restrictions, and its identity framework ONCHAINID directly into the token. As its adoption grows, the compliance guarantees have to hold across every environment regulated assets touch: modern wallets, cross-chain messaging, and institutional identity systems. That is where OpenZeppelin's collaboration with T-REX comes in, hardening the protocol architecture and compliance workflows. This work includes T‑REX v5, the next major protocol upgrade, and DINO, the ecosystem’s distribution and market infrastructure.
“We wanted OpenZeppelin involved early, while the important design decisions are still being made. Having them help shape the T-REX Protocol, how the system is structured, how identity is handled, raises the bar for everyone who builds on T-REX.”
OpenZeppelin is also collaborating with T-REX Network on the evolution of ONCHAINID, including a cross-chain identity model that makes onchain identities easier to verify and rely on at scale. Drawing on the ERC-4337 and ERC-7579 frameworks OpenZeppelin built for its own library, this work brings account abstraction into the identity layer. It will enable compliance checks that are more composable and aligned with how wallets are evolving, without compromising issuer control.
Alongside the protocol work, ERC-3643 is being delivered as an audited component in the OpenZeppelin Contracts library, so any developer on any EVM chain can import it the same way they import ERC-20 or ERC-721, out of the box. OpenZeppelin-reviewed ERC-3643 releases already ship in the Stellar Contracts and Confidential Contracts libraries, with a companion module planned for the Solidity OpenZeppelin Contracts library.
"The T-REX Protocol and ONCHAINID are already established as leading compliance standards. With OpenZeppelin having spent a decade developing standards and secure smart contracts that onchain assets valued in the billions depend on, we are now committed to scaling the Protocol, ensuring security, and further defining what compliance looks like across chains and at institutional scale."
Confidentiality at the Compliance Layer
To meet the privacy requirements of financial institutions, the T-REX Protocol has integrated Zama’s fully homomorphic encryption (FHE). This allows compliance rules to be evaluated on encrypted data so that investor identities, holdings, and transaction details are private throughout. OpenZeppelin's FHE Confidential Contracts library, built in collaboration with Zama, brings this natively into the stack, building upon the ERC-7984 Confidential Token Standard co-authored by OpenZeppelin, Zama, and Inco.
Taking ERC-3643 Multichain with OpenZeppelin
To make ERC‑3643 practical at institutional scale, the compliance layer has to protect sensitive data as it moves across ecosystems. A native Stellar implementation already lives in OpenZeppelin's Stellar Contracts library, with an EVM-anchored cross-chain design using ERC-7786 messaging and ERC-7930 addressing to extend T-REX compliance to non-EVM chains. More integrations are planned.
Follow OpenZeppelin and T-REX as work progresses across workstreams and releases become available.
FAQs
What is ERC-3643 and why does it matter?
ERC-3643 is the onchain compliance standard that embeds transfer rules, eligibility checks, and identity verification directly into a token. It ensures tokenized assets can only move between parties who meet the issuer's requirements, automatically and without manual intervention.
What is OpenZeppelin doing with T-REX?
OpenZeppelin is co-designing the next phase of the T-REX Protocol as a strategic technical partner, covering protocol architecture, ONCHAINID identity evolution, security hardening, and delivering an audited ERC-3643 implementation in the OpenZeppelin Contracts library.
What is ONCHAINID and why is it important?
ONCHAINID is the decentralized identity framework at the core of ERC-3643. It verifies who is permitted to hold a regulated token onchain, and OpenZeppelin is collaborating on its evolution to make identity verification work across chains and modern wallet types.
How does this partnership help developers?
ERC-3643 is being delivered as an audited component in the OpenZeppelin Contracts library, so any developer can import it the same way they import ERC-20 or ERC-721, out of the box, without reconstructing the standard from scratch.
What is the role of Zama in this partnership?
Zama's fully homomorphic encryption integration with T-REX allows compliance rules to be enforced on encrypted data, so investor identities and transaction details stay private throughout. OpenZeppelin's Confidential Contracts library, built with Zama, brings this natively into the stack.