Skip to content

Stablecoin Development Company for Banks, Payment Firms, Fintechs and Chains

Protofire is a stablecoin development company for banks, payment firms, fintechs and chains. We build the token contract, mint controls, reserve feed and reconciliation, or your side of a provider's program. We built and operated the reserve-data pipeline behind 15+ proof-of-reserve deployments. The issuer keeps the license, reserve and keys.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Why it matters
  3. Four routes
  4. What you get
  5. Why Protofire
  6. How the work goes
  7. How work starts
  8. Not the right fit
  9. Related guides and services
  10. FAQ

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

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

The issuer of record decides the stablecoin build

A stablecoin build starts from one legal answer: which firm is the issuer of record. That firm holds the license and the reserve, and it must redeem the tokens. For example, a payment firm's board approves a dollar token. Then counsel asks who the issuer of record is, and the answer changes which contracts, accounts and ledgers the firm needs.

Protofire is a stablecoin development company for banks, payment firms, fintechs and chains. On each route to a token, we build the engineering that the route leaves to the firm.

Who holds each layer of a stablecoin

The issuer holds the license, the reserve and the mint keys.

Your firm or your licensed issuer

Authorization, reserve and redemption

The issuer holds the license and the reserve and redeems the tokens.

Mint keys and approvals

The issuer's signers approve each mint and burn.
Protofire builds

Token contract and roles

The contract gives the mint, pause, freeze and upgrade powers separate roles.

Mint controls

Caps and a check against the reserve figure gate each mint.

Reserve feed and reconciliation

One reserve figure feeds the mint check, the accountant's file and the daily match.
Outside firms

Code review

An outside audit firm reviews the contracts.

Reserve examination

The issuer's accounting firm examines the reserve report.

US and EU rules limit who may issue and offer a stablecoin

US and EU rules decide which firms may issue a stablecoin.In the US, the GENIUS Act takes effect on 18 January 2027 (OCC Bulletin 2026-50). It then becomes unlawful for any person other than a permitted payment stablecoin issuer to issue a payment stablecoin in the United States (Sec. 3(a)).

In the EU, whoever offers an e-money token to the public must be its issuer or have the issuer's written consent (MiCA Article 48(1)). The issuer must be authorized as a credit institution or an electronic money institution. On 8 October 2026 ESMA published an opinion to national authorities on crypto-asset service providers. It says the providers "should not maintain, introduce or facilitate access to non-MiCA compliant" e-money tokens for EU clients (ESMA). ESMA says the authorities should require remediation of remaining exposures as soon as possible and no later than three months after publication.

A firm that designs its token before counsel names the issuer may have to rebuild the contracts and the ledger once the answer comes.

The issuer's own platform is part of the risk in a stablecoin. For example, StablR issued the USDR and EURR tokens. On 24 May 2026 StablR identified irregularities in its platform infrastructure "consistent with unauthorised external access" (StablR). StablR did not resume minting and redemption. On 3 November 2026 StablR's shareholders resolved to seek the dissolution and winding-up of the company (StablR update).

A new token also enters a concentrated market. On 16 November 2026 DefiLlama counted $288.8B of stablecoin supply, and USDT and USDC made up 84.7% of it (DefiLlama). So a new token has to win wallets, venues and chains.

[...] I think there's too many banks who think that they can have their own stablecoin and it's gonna actually create a lot of value. [...] In order for payments to be effective onchain, you need liquidity at both sides.
Eric Queathem, Founder & CEO, Velocity · The Protocol Roundtable by Protofire, Episode 6, 1:01:51

Four stablecoin routes differ in who issues the token

The four routes to a stablecoin differ in who issues the token and holds the reserve, and that choice sets what Protofire builds.

Fiat-backed, under your own authorization

Who issues and holds the reserve: Your firm, as a US permitted payment stablecoin issuer or an EU credit or e-money institution

What Protofire builds: The token contract, the mint and burn paths, the reserve feed and the daily reconciliation (native stablecoin development)

Issued for you by a licensed provider

Who issues and holds the reserve: A licensed provider such as Paxos or Bridge, with your brand on the token. With Circle's xReserve, a chain deploys a USDC-backed token.

What Protofire builds: Your firm's ledger, reconciliation, payouts and controls. We integrate Paxos, Bridge, Circle and Monerium.

Collateral-backed, on your own contracts

Who issues and holds the reserve: Your chain or protocol, against collateral that users lock. Counsel decides how the law classifies the token.

What Protofire builds: The collateral design, issuance contracts, oracle integration and liquidation modules (collateral-backed builds)

Tokenized deposit instead of a stablecoin

Who issues and holds the reserve: Your bank, as a deposit. If the token qualifies as a deposit, the stablecoin rules of the GENIUS Act and MiCA do not cover it.

What Protofire builds: The contract, the mint and redemption service and a daily reconciliation that traces each token to one core posting (tokenized deposits)

The parts Protofire builds as a stablecoin development company

Your route decides which parts you need.

Each power in the token contract has its own role

Your firm can freeze, seize or burn tokens on a lawful order. Protofire gives minting, cap raises and forced transfers separate roles. The allowlist and pause get separate roles too, so the minting key cannot move a holder's tokens.

Mints stop at the reserve and at your signers' caps

A mint that the reserves cannot cover is rejected onchain. Protofire wires the mint check to the reserve feed with a staleness limit. We put mint caps and parameter changes behind a multisig that your signers hold. Our blueprint on reserve-capped mint controls shows how an issuer divides mint authority and rate-limits it against the reserve.

One reserve figure for the contract, the accountant and holders

Your accountant, your mint check and your holders read one reserve figure. Protofire builds a pipeline that reads, values and matches a token's reserves to supply at one cut-off for your accountant and a Chainlink feed. The feed reports a figure and gives no opinion on the reserves.

A daily match of token supply, ledger and bank

Your finance team checks supply against the bank daily. Protofire builds a daily reconciliation that runs at 00:00 UTC. It matches the supply on each chain against your records and the reserve on the bank's latest end-of-day statement.

Venues and new chains that accept the token

Venues decide each listing. Protofire builds the evidence each venue reads, distributor APIs and new-chain deployments. We deploy the token on Chainlink's Cross-Chain Token standard, Circle's CCTP for non-USDC assets, LayerZero's OFT or Wormhole's NTT (stablecoin distribution).

Your firm's side of a provider-issued token

When Paxos or Bridge issues the token, your firm still books each mint and redemption once in its own ledger. For Paxos, Protofire builds the per-client rules and puts the memo ID in each wire template. We also build a second approver on API calls, the payouts and the daily match against the provider's reports (Paxos, Bridge).

Our record: reserve pipelines, oracles and MakerDAO tools

The record Protofire brings to a stablecoin build covers reserve data, the Chainlink layer and collateral tooling.

Reserve data for 15+ attestation deployments

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. A stablecoin's reserve feed depends on the same kind of data work.

Chainlink core contributor and CCIP

Protofire is a Chainlink core contributor and helps maintain Chainlink CCIP.

CDP Alert and the Maker governance dashboard

In 2018 Protofire built CDP Alert, an open-source monitoring and alerting tool for MakerDAO collateralized debt positions. In 2019 and 2020 we built the Maker Governance Analytics Dashboard, funded by the Maker Foundation's community grants program (Maker forum). The repositories of both tools are archived.

Somnia's oracle stack, 2025

In 2025 Protofire built Somnia's Chainlink-compatible oracle stack. The stack consisted of five oracle nodes in OCR consensus behind three mainnet price feeds and VRF. We operated the stack until the engagement ended in late 2025 (case study).

From the issuer decision to a deployment from your keys

Protofire starts from counsel's answer on the issuer, because the contracts and ledgers follow from it.

  1. Step 1

    Counsel's answer on the issuer and the route

    Your counsel decides who issues the token and how the law classifies it. Protofire designs the build around that answer.
  2. Step 2

    Roles, mint limits and the reserve cut-off in writing

    Protofire's written proposal names who holds each role and each mint key. The proposal also sets the mint caps, the rate limits and the time and time zone of each reserve cut-off.
  3. Step 3

    Contracts, reserve feed and reconciliation

    Protofire writes Solidity on OpenZeppelin Contracts 5.x where a library contract fits. We then build the reserve feed and the reconciliation.
  4. Step 4

    Outside audit and fixes

    Protofire prepares the code for an outside audit firm. We then fix the audit findings. An audit does not guarantee the absence of bugs.
  5. Step 5

    Deployment from your firm's key

    Your engineer deploys the contracts from your firm's key, and you own the code and the keys. After launch your firm runs mint and redemption. If Protofire runs tools for you, it does so under a written scope.

How work with Protofire starts

A stablecoin engagement with Protofire starts with the route your firm is weighing and the currency the token will reference.You send the chains and venues you plan for and name the firm that will issue the token. For a provider's program, you also name the provider.

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.

Where Protofire's stablecoin work does not fit

Protofire builds the engineering of a stablecoin.The issuer's role remains with an authorized firm.

  • You want a firm that issues the token or lends you a license. Protofire is not the issuer and holds no financial or crypto-asset license. Protofire holds no reserve, client funds or keys, and it gives no legal opinion and no assurance opinion on reserves. On a provider's program, your firm opens the account and holds the credentials, and Protofire signs and approves no mints or redemptions.
  • A provider's dashboard covers your volume. Paxos says firms can "Mint on demand from our Dashboard" (Paxos). With approvals and the daily CSV, the Dashboard can be enough.
  • The token must pay holders for holding it. The GENIUS Act bars a permitted issuer from paying holders interest for holding a payment stablecoin (Sec. 4(a)(11)). MiCA bars interest on e-money tokens (Article 50).
  • Your token must run on a non-EVM chain. Protofire's contract work is Solidity for EVM networks.

FAQ

What is stablecoin development?
Stablecoin development is the engineering behind a currency-pegged token. It covers the contract and its roles, the mint controls and the reserve feed. It also covers reconciliation and distribution to venues and chains. Protofire builds this engineering, while the issuer of record holds the authorization and the reserve.
Who can build a stablecoin for a bank, a payment firm, a fintech or a chain?
Protofire builds stablecoins for banks, payment firms, fintechs and chains. For an issuer under its own authorization, we build the token contract, mint controls and reserve feed. When a licensed provider issues the token, we build the firm's ledger, reconciliation and approval controls. Our record includes the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens.
Should a firm issue its own stablecoin or use a white-label stablecoin?
A white-label or stablecoin-as-a-service program puts the provider's name on the obligations. Paxos describes its program as "Your brand on the token, our name on the obligations" (Paxos). The firm still runs its booking, approvals and distribution. Issuing under the firm's own authorization keeps the reserve with the firm and brings mint controls and redemption in-house.
Who may issue a stablecoin in the US and the EU?
In the US from 18 January 2027, the issuer of a payment stablecoin must be a permitted payment stablecoin issuer. Such an issuer is an approved subsidiary of an insured depository institution, a Federal qualified issuer or a State qualified issuer (Sec. 2(23)). A Federal qualified issuer can be a nonbank entity that the Comptroller approves (Sec. 2(11)). In the EU, the issuer of an e-money token must be a credit institution or an e-money institution (Article 48(1)).
Should a bank issue a stablecoin or a tokenized deposit?
A tokenized deposit remains a claim on the bank. If it qualifies as a deposit, it falls outside the stablecoin rules of the GENIUS Act (Sec. 2(22)(B)(ii)) and MiCA (Article 2(4)(b)). But unless a shared network connects banks, a deposit token moves between the bank's own onboarded clients. A stablecoin reaches people who do not bank with the issuer. Our tokenized deposits page covers the deposit route.
What must a stablecoin contract be able to do?
Under the GENIUS Act, a permitted issuer needs the technological capability to comply with lawful orders (Sec. 4(a)(6)(B)). Such an order can require the issuer to "seize, freeze, burn, or prevent the transfer" of its tokens (Sec. 2(16)). Circle's open-source FiatToken contract is pausable and upgradable and has a blacklist. Its master minter controls the list of minters and how much each may mint.

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.