On November 23, OKXICE, a joint venture between crypto exchange OKX and New York Stock Exchange owner Intercontinental Exchange, plans to let eligible US investors trade tokenized securities around the clock.
Most of the companies in its original proposed stock lineup have objected to inclusion. The resistance is a reminder that putting a share on a blockchain involves more than making it tradable.
For investors, a basic question follows: when a token changes hands, what rights pass to the buyer — and how is that transfer reflected in the records that establish those rights?
Consider a warehouse receipt for 25 tonnes of copper. Its corresponding token might change hands three times while the warehouse register still names the first buyer. The transaction history is intact. The metal has not moved. But what, exactly, has the last person who paid acquired?
The example illustrates a problem that real-world asset tokenization, or RWA, must address wherever trading and registration operate separately. A blockchain can record a transfer quickly.
Warehouses, custodians and registrars follow their own procedures to confirm rights. Buyers and sellers need to know how far the trading has progressed and how far registration has caught up.
RWA is already a working market. Tokenized Treasury products, money market funds and gold are in circulation. DTCC launched its securities tokenization service in October 2026, allowing eligible participants to convert rights in DTC-custodied securities between traditional and tokenized forms.
Hong Kong’s HK$20 billion digital green bond issuance in September incorporated tokenized deposits into primary settlement for its Hong Kong dollar tranche.
NFTs have found a more specific role in physical markets. Platforms such as Courtyard hold trading cards and watches in custody while corresponding tokens are traded, with physical delivery available under their terms.
RWA describes the asset or rights being represented; an NFT identifies an individual item. A particular warehouse receipt can correspond to one NFT. Interchangeable fund units need not use that format.
ERC-8415 addresses the relationship between the token’s holder and an external register. It is a draft technical proposal, separate from the institutional initiatives above.
ERC stands for Ethereum Request for Comments. ERCs define how tokens, smart contracts and applications interact within the application-level standards of the Ethereum Improvement Proposal or EIP, framework. Numbers such as 8415, 7540 and 3643 identify proposals.
They are neither technical ratings nor successive versions of the same technology. Editors assign and administer them under the proposal process; they carry no regulatory endorsement.
Understanding ERC-8415 requires separating the formation of a sale agreement from the transfer of rights in the asset. Under the project’s proposed trading arrangement, transferring an NFT expresses the formation of an on-chain sale agreement.
The asset register remains with the existing institution, and the transfer of rights follows applicable law and registration procedures. An NFT arriving in a buyer’s wallet does not, by itself, establish that the real-world transfer is complete.
The distinction cannot be reduced to a claim that other RWA tokens simply “are the asset.” Tokens can represent fund units, debt claims, income entitlements or delivery rights. Their legal meaning depends on the arrangement behind them. ERC-8415 gives applications a common way to distinguish a token transfer from confirmation by an external register.
It supplements the ERC-721 record of NFT ownership with a separate history of register-confirmed holders. The owner identifies the address currently holding the token. The holder identifies the party recorded by the external register at a specified time. The two records can update on different schedules.
Return to the copper receipt. A transfers its NFT to B, who transfers it to C. The blockchain now identifies C as the token owner, but the warehouse register may have confirmed only B. An application using ERC-8415 can present both facts.
That matters for payment, delivery and collateral. Treating C’s possession of the NFT as proof of completed registration could lead a platform to release money prematurely or lend against an interest that has not yet been confirmed. Separate records give the application a basis for deciding what can proceed and what must wait.
When owner and holder match, the on-chain holding and the reflected registration record are aligned. That alone does not establish that payment and every other settlement obligation have been discharged. Nor does a registered holder necessarily identify the ultimate beneficial owner, which requires separate identity and ownership information.
Participants can therefore follow successive on-chain transfers while registration remains incomplete, distinguish confirmed changes from those awaiting confirmation, and let supporting applications use that information to administer payments and refunds.
Proposer Michael Yip describes the protocol’s role as representing the external register on-chain. It records what the registrar has confirmed; it does not adjudicate legal ownership. The distinction preserves the responsibilities of the institutions whose records and decisions give the transaction legal effect.
Timing adds another complication. A register might confirm B’s holding with effect from 10 am, while the update reaches the blockchain at noon. An application needs to reconstruct the record from 10 am rather than mistake noon for the effective time. ERC-8415 provides historical queries and distinguishes provisional answers from final ones.
Existing platforms can build these functions themselves. Other standards already address related needs: ERC-7540 supports asynchronous deposits and redemptions, while ERC-3643 handles investor eligibility and transfer restrictions.
ERC-8415 would provide a shared interface for external registration records, reducing the need for platforms and wallets to interpret bespoke systems.
Visibility does not eliminate settlement risk. If A’s transfer to B remains incomplete while subsequent trades reach C, D and E, a failure in the first leg still leaves refunds, price differences and liability to be resolved.
Escrow, payment release and bounded unwinding require supporting applications and contractual arrangements. Adopting ERC-8415 does not automatically supply them.
Registration is not invariably slow, either. The London Metal Exchange already operates an electronic warrant-transfer system in which certain transfers appear in the recipient’s account once authorized.
ERC-8415 must show that better coordination, traceability and automation justify the costs of integration and maintenance. Its efficiency gains will depend on the systems it connects.
The proposed standard cannot settle the issuer objections surrounding OKXICE. Its narrower task is to make the relationship between on-chain transfers and external registration explicit and usable.
As trading hours expand, that task deserves attention. A buyer needs to establish what has been acquired, what remains outstanding and who is responsible if something goes wrong. ERC-8415 will be judged by how reliably it helps answer those questions in real transactions.
Jeffrey Sze is chairman of Habsburg Asia, General Partner of Archduke United LPF and director of the Austria and Central Europe to Asia AI & Innovation Exchange. He specializes in high-end art transactions and RWA-T operations, and secured a cryptocurrency exchange license in Switzerland in 2017.