
How fast institutional allocators want to exit tokenized assets
Ivan Postavskyy, Centrifuge
Moment at 36:21Episode 2 · Ghost Town Markets: Building Secondary Liquidity for Real-World Assets
Protofire builds RWA tokenization for issuers of funds, notes, bonds and shares. We build the token, register sync, redemptions and NAV delivery to match your legal record. Your agents keep the register. In 2021 we built the DEX core and subgraph for Swarm Markets, a BaFin-licensed DEX at launch.

Reviewed by Diego Torres, Offer Owner at ProtofireLast reviewed: November 2026
Work shipped for 60+ networks and 95+ protocols, including
A tokenized issue has two records of each holding: the token on the chain and the register that the issuer's agents keep. RWA tokenization for issuers keeps the token matched to the legal record, and Protofire builds that match.
For example, a holder sends your tokenized fund units to another wallet on a Saturday evening. The chain settles the transfer. Your transfer agent's register moves on business days, so the transfer reaches the register on the next business day. Meanwhile, a holder who asked to redeem on Friday wants a price. Your fund strikes NAV once per dealing day, so the request queues against a figure that does not exist yet. Which record do you show that holder, and who owns the difference between the two records?
The issuer and its licensed agents set the rules and keep the record. In the layers Protofire builds, each figure has a named cut-off.
SEC staff and ESMA say a token does not change the rules for the security.SEC staff said on 28 January 2026 that the format of a security "does not affect application of the federal securities laws". That statement comes from SEC staff and is not a rule. ESMA's guidelines (text dated 19 March 2025) say tokenized financial instruments "should continue to be considered as financial instruments for all regulatory purposes". So the token is one record of the right the issuer owes the holder.
The governing law and the offering documents name the legal record, which can be the chain or an agent's system. Franklin's FOBXX is one example. The fund's Summary Prospectus of 1 August 2026 says its transfer agent "maintains the official record of share ownership" in a blockchain-integrated system. Your counsel names the legal record for your issue. The other record is matched to the legal record at a named cut-off, and each break has an owner.
When the token and the register are not matched, the damage can occur on payment days. A coupon is paid from a holder list, and that list can be wrong when the chain and the register disagree. A transfer that the register did not accept needs its own state: rejected, pending or corrected.
Under our existing framework the person responsible for the register must retain authority over it, including to process decisions of a court or to resolve consumer issues.
You get an issue whose token, register, redemption queue and published figures can be read against each other.
Each limit in the token points to the clause of the offering document that sets it. Protofire builds the ERC-3643 token or a permissioned ERC-20, including its identity claims and rule modules. The owner and agent roles are set from your keys, and our ERC-3643 page has the details. The standard gives an agent the powers of freezing and forced transfer (EIP-3643). The standard also gives the agent minting, burning and recovery. These powers let an agent act on a court order or correct an error. Each power gets a holder, an approval rule and a register entry.
Your paying agent receives one holder list per record date. A named person owns each break between the register and the chain. Protofire builds an indexer over the token's transfer events. We match the indexer against the transfer agent's or register keeper's file, at that file's own cut-off. Each record date gets a holder snapshot at a named finalized block. Where one share class is tokenized and the legal register does not move, our blueprint shows the design.
A holder files a request. The request is Pending until the administrator has struck NAV and the custodian has funded the vault. Then the request turns Claimable, and the holder claims. If a batch is marked Claimable earlier, holders see money that the vault does not have. Protofire builds the ERC-7540 request queue to your cut-offs, and the flow that moves cash from the custodian to the vault. A missed NAV or a cash shortfall gets a stated outcome. VaultOS is our vault for asynchronous subscriptions and redemptions.
Your administrator strikes NAV, and a feed publishes that figure. A figure older than its age limit is shown as stale and does not settle a request. Protofire delivers the NAV through a Chainlink feed or a signed update. For a token that claims backing, we read custodian statements, SPV records and supply at one cut-off.
The exit routes are written down before launch: redemption at NAV, block trades between eligible holders, or admission to a licensed venue. Protofire builds block-trading contracts on the dOTC model, which we contributed to. You set the access rules, and each settlement is fed into the register match. Under MiFID II Article 4(1)(22), a multilateral trading facility is a system that matches third-party buying and selling interests in financial instruments under non-discretionary rules. Running a multilateral trading facility takes a license.
RWArmor, Protofire's parametric protection offer, is scoped to events such as a redemption freeze, a custody break or a NAV deviation. You get a list of triggers, and each trigger is tied to the source that proves it. Your counsel reviews how the arrangement is classed in each market.
Four parts of Protofire's record apply to a tokenized issue.The first two are wallets gated by identity under a venue's license, and block-trading contracts. The other two are reserve data that an outside checker reads, and oracle integrations on new chains.
In 2021 Protofire built the DEX core (a Balancer fork) and subgraph for Swarm Markets and contributed to dOTC. The DEX core repository is public. Swarm Markets was a BaFin-licensed DEX at launch where only KYC-verified wallets trade. Swarm held the license and ran the KYC.
Protofire built and operated the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens, for a large auditing firm.
Under Chainlink Community Grants between 2020 and 2022, Protofire built node deployment repositories for five chains and External Adapters. We also built integration testing on 9 EVM networks and a cross-testnet LINK faucet (Chainlink case). Chainlink's post of 27 August 2021 says Protofire had completed several grants for integrating the Chainlink stack into chains (Chainlink, archived). The post names xDai (now Gnosis Chain), Avalanche, Plasm and Celo as examples. Protofire's node repositories are public and archived, including the Avalanche node repository.
Protofire starts an issue build from one transfer and one redemption.
Counsel and procurement can read the shared terms before the first call.
How we work shows a worked proposal.
The build fits once counsel is engaged and the register keeper or transfer agent is named. The token then has to match their record through transfers, redemptions and payments.

Ivan Postavskyy, Centrifuge
Moment at 36:21Episode 2 · Ghost Town Markets: Building Secondary Liquidity for Real-World Assets
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.