Docs/t rex network

T-REX Protocol

How T-REX Network implements ERC-3643 at institutional scale.

How T-REX Network implements ERC-3643 at institutional scale.

The protocol layer of T-REX Network

The T-REX Protocol is the implementation of ERC-3643 across the T-REX Network — the smart-contract stack that makes compliant tokenization usable in production, on every supported chain, with the operational guarantees institutions require.

The protocol itself is open and standardized. ERC-3643 — code name "T-REX" — is a Final EIP, audited, governed by the ERC-3643 Association, and used to tokenize more than $32 billion of real-world assets to date. T-REX Network takes that open standard and turns it into a complete institutional framework: deployed across chains, integrated with identity and asset registries, served by audited factories and a production API, and reinforced by the broader Compliance Engine.

Within the four-layer architecture of T-REX Network, the protocol is the foundation. The Ledger gives it a canonical home, the Compliance Engine gives it institutional defense-in-depth, and the AppStore gives it a usable application surface.

For the technical specification of the standard itself — interfaces, claim topics, compliance modules, transfer logic — see ERC-3643 Protocol, which routes to the authoritative documentation at erc3643docs.erc3643.org.

What the protocol does

The T-REX Protocol streamlines the tokenization of financial assets by encoding compliance, identity, and operational control directly into the smart-contract layer.

It enables:

  • Seamless representation of assets on-chain, with embedded references to their underlying data (documents, prices, ratings, certifications).
  • Legal identification of stakeholders — issuers, agents, investors, regulators — through verifiable on-chain identities.
  • Tracking of all investment activities — transactions, subscriptions, redemptions, corporate actions — at the protocol level.
  • Protocol-level enforcement of compliance — every transfer is validated against identity, eligibility, and rule criteria before it executes.

The result: tokens that behave like regulated financial instruments by construction, not by external monitoring.

Key features

Multi-chain by design

The T-REX Protocol can be deployed and operated on any EVM-compatible blockchain. The same contract architecture, the same identity model, and the same compliance enforcement run consistently across every supported chain — including the canonical T-REX Ledger and connected external chains for distribution and liquidity.

Efficient token issuance

Issuers can deploy compliant tokens in a single transaction through the T-REX Token Factory dApp, with compliance and distribution rules set at deployment. No bespoke contracts. No reinvention.

Identity-aware transfers

Every transfer is validated against the identity of both sender and receiver through OnchainID. Compliance follows the verified identity, not the wallet address — which means transfer restrictions, eligibility rules, and operational controls remain consistent even as ownership moves.

Asset-level credentials

Tokens deployed through the protocol receive an AssetID by default — a verifiable identity for the asset itself. AssetID can carry the issuer's Legal Entity Identifier (LEI), the financial instrument's ISIN, the Digital Token Identifier (DTI), Net Asset Value, ratings, certifications, and legal documents. Any of this data can be signed and attested by the issuer or by authorized third parties (auditors, regulators), ensuring authenticity.

Operational controls

The protocol gives issuers and transfer agents the operational levers regulated finance requires: freeze, force transfer, recovery (for lost wallet access), and on-the-fly rule updates. These are protocol-native, not bolted on.

Open-standard interoperability

Because the protocol is built on ERC-3643 — and ERC-3643 is recognized as the Ethereum community's standard for tokenized securities — every service provider, custodian, distributor, or application that supports ERC-3643 works with any T-REX-issued asset out of the box. Integration is done once, not per token.

How the protocol fits in the stack

With the T-REX Ledger

The Ledger is the canonical chain for protocol deployments. Assets issued on the Ledger hold the authoritative ownership state; representations on external chains derive their compliance and transferability from the Ledger's canonical record. See T-REX Ledger — Issuance model.

With the Compliance Engine

Protocol-level enforcement is the first line of the broader defense-in-depth model. Above it sit application vetting, institutional validator governance, the distributed node network, and Ethereum settlement. Real-time threat detection and selective FHE-based privacy run across the whole stack. See Compliance Engine.

With the AppStore

The protocol is what the AppStore is built on. Official applications — Token Factory, Identity, DINO Primary, DINO Secondary, and others — interact natively with ERC-3643 contracts. Builder applications integrate against the same surface. See T-REX AppStore.

With developers

For production integrations, the T-REX Engine API abstracts protocol-level calls behind a stable REST surface. For direct contract work, the open-source reference implementation is available at github.com/ERC-3643. See Getting Started for the developer's path.

Standardization matters

A standardized framework for tokenizing financial assets is what makes the ecosystem coherent. By providing clear guidelines, audited contracts, and shared identity and compliance primitives, the protocol lets stakeholders execute their roles efficiently:

  • Service providers integrate once with the standard, then work with every compliant token.
  • Issuers and investors rely on the protocol's audited foundations rather than analyzing bespoke smart contracts.
  • Regulators see the same operational model across issuances, reducing the cost of supervision.
  • Builders target a stable, broadly adopted surface rather than chasing a moving target.

This is what enables tokenization to scale beyond pilots: not a faster chain, not a cheaper VM, but a shared standard institutions and regulators trust.