Tokenization Platform Development on Contracts Your Firm Deploys
Protofire offers tokenization platform development to fund managers, banks and platform operators. We build the factory, upgrade authority, identities and vaults that your firm deploys from its keys, or what Securitize, Centrifuge or Brickken leave to you. We built the DEX core for Swarm Markets, a BaFin-licensed DEX at launch.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Who controls the contracts of a tokenization platform
In tokenization platform development, the first question is who holds the decision to change the platform's contracts. A hosted platform's terms answer that question. On contracts your firm deploys, your firm writes the answer into the deploy call. The register and the signing of investor claims remain with each issuer, its licensed agents and its KYC provider.
For example, your firm is about to onboard a second issuer onto its tokenization platform. Both tokens now follow one set of contracts, and someone has to own the decision to change them.
Who builds and who decides on a multi-issuer platform
Issuers and their agents set the terms and keep the register. Protofire builds the contracts and services around them. The contracts are deployed from keys on your firm's side.
Issuer and counsel
Appointed agents
Factory and upgrade authority
Identity and onboarding
Subscription and redemption vaults
Data and venue interfaces
Investor wallets
Venues and lending markets
One owner can change the code of all your issuers' tokens
In the ERC-3643 reference code, one owner picks the code version for all token suites that still point to the factory's implementation authority.One call to useTREXVersion moves all of those suites together (TREXImplementationAuthority.sol). On a shared platform, that owner is the operator.
An issuer can move its token to an implementation authority of its own. But the code accepts that move only when one caller owns all six contracts of the suite, including the identity storage. That storage "can be shared by multiple tokens". On a shared platform, the operator owns that sixth contract.
A KYC provider's claim-signing key also affects many tokens at once. The reference claim issuer accepts a claim only while the key that signed it still has the claim-signing purpose (ClaimIssuer.sol). Once the key is removed, the claims it signed stop counting on all tokens that trust that provider.
Ownership roles that nobody writes down are decided by the platform's own rules. For example, on Brickken the tokenizer is "the wallet that performs the first newTokenization" (Brickken docs).
Multiple blockchains, token standards and regulatory regimes could easily recreate the silos that market infrastructure has spent decades working to eliminate.
What Protofire builds in tokenization platform development
A token factory owned by your firm
Your firm decides who can add an issuer. The call that creates each issuer's suite writes its owner and agent addresses. Protofire builds a T-REX factory and implementation authority, or a factory for a permissioned ERC-20. The factory is deployed from your firm's keys.
A timelock on code version changes
The owner of the implementation authority is a timelock, and its proposer is a Safe your firm controls. So a new version waits out a notice period that issuers can read onchain. An issuer that owns all six suite contracts can move to its own authority before the change applies. Protofire writes the release procedure, which names who proposes a version, who approves it and which tokens follow it.
Investor identities shared across your issuers
An investor's checks are reused across your issuers, or kept per issuer if you choose that. Protofire builds the identity storage and a claim issuer contract for each KYC provider. We also build a staged plan for rotating claim-signing keys, with a written list of the tokens a key change would affect. Our compliance integration service connects the provider checks and screening.
Subscriptions and redemptions on each issuer's dealing calendar
Requests queue against the NAV struck for the dealing day. Protofire builds an ERC-7540 vault for each share token. Each vault has cut-off logic and a cancel rule in its code. The fulfiller key is held by the administrator or transfer agent that the issuer appoints. A request moves from Pending to Claimable only when the fulfiller key applies the dealing day's NAV. An indexer matches vault events against the transfer agent's file and names the side that moved first.
NAV and reserve readers with a maximum age
A vault should not queue requests against a stale price. Each NAV and reserve reader has a maximum age and a named source type: a third party, a custodian or an issuer-hosted source. When a figure exceeds that age, requests wait and the figure is flagged. More detail is on our proof of reserve and oracle integration pages.
ERC-7943 transfer checks for venues
A lending market or exchange can ask the token whether a transfer would pass before the venue submits one. Protofire adds ERC-7943 views such as canTransfer. ERC-7943 has been Final since 5 May 2026 (EIP-7943). We also give venue contracts identities of their own.
Tokenization platform or contracts your firm deploys
A platform's issuance product decides who deploys each token, who sets its code version and whose KYC checks investors pass.On contracts your firm deploys, your firm makes those decisions.
Deploying a token
On a tokenization platform: The platform's factory or app deploys each token.
On contracts your firm deploys: Your firm's own factory deploys each issuer's suite.
Code version
On a tokenization platform: Whoever owns the platform's proxies or shared authority sets the version.
On contracts your firm deploys: Your own authority sets the version, under an approval rule you write.
Investor onboarding
On a tokenization platform: Investors use the platform's KYC flow and identity records.
On contracts your firm deploys: Your KYC providers sign claims in each investor's identity contract.
Data and reporting
On a tokenization platform: You read data through the platform's apps and exports.
On contracts your firm deploys: An indexer you control reads your contracts' events.
Moving later
On a tokenization platform: A move is bound by the platform's terms and its admin and upgrade roles.
On contracts your firm deploys: The owner and upgrade roles are yours. A new chain still needs fresh tokens and a register entry for each holder.
Our record: Swarm Markets, reserve data and Safe
Protofire's public record includes a permissioned DEX, reserve data and Safe deployments, and each applies to a platform that issues tokens for many issuers.
A permissioned DEX for Swarm Markets
In 2021 Protofire built the DEX core (Balancer-fork AMM) and subgraph for Swarm Markets, a BaFin-licensed DEX at launch where only KYC-verified wallets trade. We also contributed to dOTC. Swarm held the license and ran KYC and permissioning.
A reserve-data pipeline for asset-backed tokens
For a large auditing firm, Protofire built and ran the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens.
Safe on 120+ EVM networks since 2018
In May 2026 the Safe Ecosystem Foundation wrote that Protofire "has been contributing to Safe since 2018". We deployed Safe on 120+ EVM networks, where it secures $2B+. Our Safe multisig work has its own page.
How a tokenization platform build with Protofire runs
You send the asset types and the chains.You also name the firms that keep each register and run KYC, and say whether a platform is already chosen.
- Step 1
The proposal names the owner of each contract and key
Before a contract is deployed, the proposal names who owns the factory and the implementation authority. The proposal also names who owns the identity storage and the claim keys. The issuer's terms say whether its token follows your authority or moves to its own, and who approves a version change. - Step 2
The factory deploys the first suite
In ERC-3643 release 4.1.3, deployTREXSuite runs only from the factory owner's key (TREXFactory.sol). So your operations team signs the call. The call names the issuer's owner and agents, and the issuer owns five of the six contracts once the factory deploys the suite. If the call passes your storage address, the new suite reuses the investors already onboarded. - Step 3
The vault opens and the readers start
The vault opens for the issuer's share token. Because the vault holds tokens, it gets an identity with the claims the token requires. Then the issuer's registry agent registers the vault. The NAV and reserve readers start with their maximum ages set. - Step 4
The issuer's agent opens trading
The ERC-3643 reference token starts paused. An agent of the issuer unpauses the token once the register and the vault match. - Step 5
Code, keys and roles your firm holds at the end
By contract, the code Protofire writes and the keys that the build creates belong to your firm. From the first deployment, each owner, agent, upgrade and claim role is assigned to your firm, an issuer or their agents. Your team runs the platform, or Protofire operates a part of it under a written scope that names the service's write calls.
Commercial terms for work with Protofire
Protofire's commercial terms are listed below.
- 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.
Platforms we integrate for tokenization
Where a firm already chose Securitize, Centrifuge, Brickken, the ERC-3643 standard or Canton, Protofire builds what that choice leaves to the firm.
Securitize
Transfer agent, fund tokenization and investor onboarding APIs.
Left to you: Your onboarding screens and KYC, webhook and whitelisting status handling, balance reconciliation per chain, and eligibility state in any lending market you connect.
Securitize integrationCentrifuge
Protocol for issuing and running tokenized funds.
Left to you: Investor KYC and the allowlist entries that follow it, NAV from your administrator, the register when a transfer agent keeps it, stablecoins on each network where investors redeem, and booking orders in your ledger.
Centrifuge integrationBrickken
Software an issuer uses to create and run its own tokens.
Left to you: Signing your token, offering and dividend writes from the tokenizer wallet in your custody, reading your token's role set with Brickken, deciding which investors to approve, and the links to your payments and books.
Brickken integrationERC-3643
Permissioned tokens with onchain identity.
Left to you: Issuance flows, investor onboarding, transfer agent sync and distribution.
ERC-3643 service pageCanton
Network for private capital-markets transactions.
Left to you: Daml applications, node operation and connections to booking.
Canton service pageWhen a platform's own product or another service fits better
A platform's own issuance product fits better when the work involves one issuer, one register and no internal systems.
- You need one permissioned token built in depth. That is our ERC-3643 development work.
- You are one issuer working out its record and resale. Our RWA issuers page covers that case.
- You are a bank putting deposits on chain rather than securities. That build is our tokenized deposits service.
- You need a transfer agent, a register keeper or an administrator. You may also need a legal opinion. Those roles are appointed directly.
- You need a regulated status. Licensed activity is the responsibility of you and your providers. Your counsel decides which role your platform holds.
FAQ
What is tokenization platform development?
Who can build a tokenization platform for a fund manager, a bank or a platform operator?
Who signs deployments on a platform Protofire builds?
Can an investor cancel a redemption request in an ERC-7540 vault?
Is a figure on a proof-of-reserve feed proof that the assets exist?
Can an issuer leave a shared platform later?
Does running a platform for other issuers make my firm a transfer agent or register keeper?
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.
