A security can move across networks. Can its compliance move with it?
Consider a tokenized bond financing an income-producing property, offered exclusively to professional investors. An approved holder wants to transfer it to another investor through a different platform or blockchain network. The recipient has completed KYC elsewhere. Can the receiving environment recognise the relevant credentials, apply the offering’s restrictions and maintain a consistent ownership record?
This is where a technically possible transfer can become a manual exception, a repeated verification exercise or a blocked transaction. For institutional tokenization, including real estate, the rules governing ownership and distribution must remain enforceable throughout the asset’s lifecycle.
Two capabilities need to work together: programmable compliance, which checks whether a transfer is permitted, and interoperable infrastructure, which keeps ownership and compliance information consistent across connected environments.
The initiative announced by Apex Group, Chainlink, T-REX Network and the ERC3643 Association on 4 November 2026 addresses this combination through an initial bond implementation aligned with Swift standards.[1]
Programmable compliance starts with the investor and the offering
ERC-3643, also known as T-REX, is an open token standard for regulated assets. It reached Final status in Ethereum’s standards process in December 2023 and runs on EVM-compatible networks. It extends ERC-20 with identity-based permissions, transfer checks and authorised administrative controls.[2][3]
We explored these controls in our earlier article, The silent backbone of digital asset markets. Their practical value becomes clearer when mapped to three questions.[8]
Identity
Who is behind the wallet, and which checks have been completed?
Investor identification and verification form part of customer due diligence under AML/CFT requirements. ERC-3643 can check signed claims from trusted verifiers, such as confirmation that a KYC check has been passed. The underlying identity documents remain off-chain.[3][4]
This makes verification results usable by connected applications, subject to their acceptance of the verifier and the evidence. Responsibility for due diligence and ongoing monitoring remains with the relevant obliged institution.
Eligibility
May this investor hold this particular security?
For a professional-only real estate offering, identity verification alone is insufficient. The recipient must also meet the applicable investor classification and jurisdictional conditions. A verified retail investor would therefore still fail the eligibility check for that offering.
This supports the implementation of distribution restrictions within frameworks such as MiFID II and Switzerland’s FinSA. The legal assessment determines the requirements; the technical configuration makes the relevant conditions enforceable. Whitelisting records permission based on those checks.[3][5][9]
Transferability
Is this specific transfer permitted now?
The answer may depend on a lock-up, permitted jurisdictions, holder limits or a freeze affecting a wallet or part of its balance. Sanctions-related restrictions can also be reflected through appropriately maintained rules and authorised controls.[2][3]
These categories overlap. An investor may be identified and eligible, yet unable to receive a particular transfer. Programmable compliance therefore needs current inputs, correctly configured rules and accountable operators.
Interoperability connects those rules with existing market processes
Programmable controls become more useful when an institution can apply them consistently beyond one platform. This requires both coordination between blockchains and compatibility with the processes through which regulated firms already operate.
According to the announcement, the participants contribute complementary capabilities:[1]
| Participant | Contribution |
| Apex Group | Regulated asset servicing and the operational environment |
| ERC3643 Association | The open framework for identity, eligibility and transfer rules |
| T-REX Network | A shared source of record and distribution across supported networks |
| Chainlink | Cross-chain transfers through CCIP and compliance enforcement through ACE |
| Swift standards | Alignment of asset representation and lifecycle data with established market practices |
The distinction matters. ERC-3643 defines token-level interfaces and controls. T-REX Network and Chainlink provide infrastructure for coordinating assets across supported networks. Swift standards and taxonomy help make their representation understandable within existing capital market processes.[1]
Our reading is that this offers a practical route to connecting DLT-based securities with incumbent institutions. Institutions can build on familiar data models while developing new execution capabilities, reducing the need to reconstruct the entire operating framework for every network.
Institutional support is widening
The ERC3643 Association currently lists 152 members, including ABN AMRO, Swift, DTCC Digital Assets, Invesco and SS&C alongside digital asset specialists such as Chainlink Labs, Fireblocks and Kraken Institutional.[6]
In the United States, SEC Chairman Paul Atkins explicitly cited ERC-3643 as an example of a token standard incorporating compliance features in his July 2025 Project Crypto speech.[7]
Together, these are meaningful signals of institutional attention. Productive adoption still depends on what each participant actually implements.
The practical test for real estate capital markets
At HammerBlocks, our focus is structuring, tokenization and distribution of institutional-grade real estate investments for professional and qualified investors, within the relevant regulatory framework. Our work combines legal and compliance considerations with the selection and coordination of ecosystem partners.
In that work, support for ERC-3643 across custodians, registrars and trading venues remains uneven. Integration decisions can still limit which investors can access an instrument, where it can be held and how it can be transferred.
For a developer or asset manager planning successive financings, the opportunity is repeatability: reuse an operating framework across suitable issuances, connect additional distribution partners and reduce avoidable manual checks. Each asset retains its own investment terms, investor rights and applicable restrictions.
The announced bond implementation provides a concrete starting point.[1] The next test is whether its approach can be repeated across issuers and service providers in routine regulated business.
Peter Hughes points to the foundations for institutional scale. We fully share that view. At HammerBlocks, we see this as a practical step towards what we are building: repeatable RWA issuance and distribution for professional investors, connecting tokenized securities with regulated capital markets. With adoption picking up, this model is set to scale well beyond individual bonds.
From bricks to blocks. This isn’t about hype. It’s about real-world adoption. #Web3getsConcrete
Exploring institutional real estate tokenization? We support developers and asset managers from structuring to investor-ready execution. Get in touch at hammerblocks.com/contact/
Sources
[1] Apex Group — interoperable compliance framework announcement, 4 November 2026
[2] Ethereum — ERC-3643 specification
[3] ERC3643 Association — how the standard works
[4] EU AML Directive 2015/849 — Articles 13 and 25
[5] MiFID II — Articles 16 and 24 and Annex II
[6] ERC3643 Association — members, checked 7 November 2026
[7] Paul S. Atkins — American Leadership in the Digital Finance Revolution, 31 July 2025
[8] HammerBlocks — The silent backbone of digital asset markets, 13 June 2025
[9] FINMA — client adviser registration and FinSA conduct requirements
Â