Skip to content

RWA Tokenization for Issuers of Funds, Notes, Bonds and Shares

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.

Diego Torres

Reviewed by Diego Torres, Offer Owner at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Legal record
  3. What you get
  4. Why Protofire
  5. How the build runs
  6. How work starts
  7. Not the right fit
  8. Related guides and blueprints
  9. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

Who runs each layer of a tokenized issue

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.

The issuer and its agents

Issuer and counsel

The issuer and counsel own the offering document, the eligibility rules and the redemption promise, and choose which record is primary.

Licensed agents

The issuer appoints each agent: the transfer agent or register keeper, the custodian, the fund administrator and the paying agent.
Protofire builds

Register sync

The sync matches the holder list, the transfer log and the record-date snapshots between the agent's file and the chain.

Token and transfer rules

The permissioned token has investor identities, agent roles and the limits that the offering document sets.

Redemption and data

The request queue follows the dealing cut-offs, and NAV and reserve figures are delivered with a staleness rule.
Investors and venues

Investor wallets and custody

Holders use their own wallets and custody accounts.

Licensed venues

A licensed venue is where the token trades.

What RWA tokenization for issuers gives your issue

You get an issue whose token, register, redemption queue and published figures can be read against each other.

A permissioned token with limits from your offering document

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.

A register and a chain that match at the cut-off

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.

Redemptions that follow your dealing calendar

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.

NAV and reserve figures with a source and an age limit

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.

Resale routes that fit your offering terms

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.

Parametric protection for events named in your issue

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.

How the build runs, from offering document to launch

Protofire starts an issue build from one transfer and one redemption.

  1. Step 1

    Send the offering document

    Send the draft offering document under NDA, with investor data removed. Add the jurisdictions you will sell into and the firm that keeps, or will keep, the register.
  2. Step 2

    The first proposal traces one transfer and one redemption

    Protofire's first written proposal starts from the record that counsel has named as primary. The proposal traces a transfer and a redemption through the agent's file, the chain and the custodian's statement. The proposal then lists each power with a suggested holder, and sets the cut-offs that tie the register, the supply and the cash together.
  3. Step 3

    Token rules and the register match come first

    Protofire's plan puts the token rules and the register match first, because the payment files and the redemption queue read from them. Redemption and NAV delivery come next. The trading contracts and the trigger list follow where your asset needs them.
  4. Step 4

    An outside audit, then launch from the issuer's keys

    Plan an outside audit before launch. Scope the custom rule modules into the audit, because a review of the base standard does not cover them. Each deployment runs from keys held on the issuer's side.

How work with Protofire starts

Counsel and procurement can read the shared terms before the first call.

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

When this build is not the right fit

  • A full-service platform already keeps your register. Securitize's SEC-registered transfer agent keeps the ownership record of the fund tokens it serves. Our Securitize integration page sets this out. If your asset is on such a platform, the build is the link to your reporting and custody.
  • You need a firm in a licensed or legal role. Protofire does not act as transfer agent, registrar or depositary. We also do not act as administrator or placement agent. Protofire holds no license and gives no legal opinion. Whether a token is a security, or a design amounts to a trading venue, is for your counsel.
  • You want a market or a promise that the asset cannot back. An order book for your own securities needs a venue license. An asset that settles in days or months needs a redemption term that the asset can meet.
  • You run a fund mandate for a sponsor or a platform for many issuers. A firm running a fund mandate for a sponsor should read our asset managers page. Our tokenization infrastructure page covers a platform that serves many issuers.

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.

FAQ

What is RWA tokenization for issuers?
RWA tokenization for issuers puts a fund unit, note, bond, share or asset-backed claim on a blockchain. It keeps the token in step with the legal record. Protofire builds the permissioned token and its transfer limits. We also build the register sync, redemption and NAV data around the issuer's transfer agent, custodian and counsel.
Who can build the token and register sync for a tokenized issue?
Protofire builds the token and the register sync around the agents that the issuer appoints. Once an issuer has chosen them, we integrate ERC-3643 platforms, Securitize, Brickken and Canton. We integrate Fireblocks, Taurus, BitGo and Safe for custody, and Chainlink for NAV and reserve data. Protofire builds the links to your register, custody and reporting. The full list is on our platforms page.
Do I need a transfer agent or a register keeper?
Yes, where the governing law or the offering documents name one. A German crypto security exists through its register entry (eWpG § 4(3)). Keeping that register is a financial service under the German Banking Act (KWG § 1(1a)).
Can a US investor buy my token on a public chain?
Yes, when the sale is registered or fits an exemption. SEC staff say the format of a security "does not affect application of the federal securities laws". J.P. Morgan's MONY, launched on 15 December 2025, is a 506(c) private placement fund on public Ethereum (J.P. Morgan). The token's transfer rules can include Regulation D resale limits and Regulation S compliance periods.
Can I move the token to another chain or registrar later?
Yes, for both the registrar and the chain. KfW has done both under German law, in what it calls a stress test. On 23 September 2026, during the bond's term, KfW's third blockchain bond moved from Cashlink to DekaBank as register keeper. The bond also moved from Polygon to SWIAT. The tokens could not move between the two infrastructures, so DekaBank generated new ones on SWIAT while Cashlink deleted those on Polygon (KfW). Under German law, an issuer may change its register keeper without holder consent unless the issue terms say otherwise (eWpG § 16(2)).
How is the token standard chosen?
The transfer and redemption model that the offering needs decides the standard. ERC-3643 suits identity checks and rule modules on the token. ERC-7540 suits queued subscriptions and redemptions. A permissioned ERC-20 can be enough where one transfer agent runs everything. Protofire's token standards guide compares ERC-3643 with ERC-1400 and a permissioned ERC-20, and states our stake.
Who can freeze, force a transfer, mint or upgrade a tokenized issue after launch?
The issuer or its licensed agent holds both roles that control these powers. The holder of the token's agent role can freeze and force a transfer. That holder can also mint, burn and recover wallets. The holder of the owner key decides who has the agent role. On the T-REX reference contracts, the owner key holder also decides which code version the token runs, through the implementation authority. After launch, Protofire holds no owner, agent, registry or upgrade key on the token.

Discussed on The Protocol Roundtable

All episodes

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.