Native Stablecoin Development for Chains, Fintechs and Issuers
Protofire offers native stablecoin development to chains, fintechs and issuers that want their own dollar or euro token. We deliver the contracts, price and reserve layer, tooling and audit preparation. Your firm keeps the license, reserves and keys. Protofire is a Chainlink core contributor and helps maintain Chainlink CCIP.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What Protofire builds for a stablecoin of your own
Protofire builds native stablecoins for a chain, a fintech or an issuer. Our stablecoin development covers the collateral and risk design, the issuance and redemption contracts, the price and reserve layer and the tooling. Your engineer deploys the contracts with your key.
Who issues the token is a legal question, and it comes before the build plan. For example, your board has approved a token with your name on it. Then counsel asks who the issuer of record is, and the build plan gets redrawn.
Who owns each layer of your stablecoin
Your firm keeps the authorization, the reserves and the keys. Protofire builds the layers between them.
Authorization and reserves
Mint, redemption and keys
Price layer and reserve feed
Contracts and collateral design
Frontend, SDKs and subgraph
Code review
US and EU law decide who may issue a stablecoin
A stablecoin design built before counsel answers the issuer question may have to be rebuilt once the answer comes.
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 and must have notified a crypto-asset white paper. MiCA's rules for e-money tokens have applied since 30 June 2024.
A collateral-backed design has a failure point inside the mechanism. The authors of Liquity V2 state that failure point for forks of their code.
The system does its best to “contain” damage via branch shutdown, but in the worst case, a single oracle or collateral failure could lead to de-peg of the stablecoin and systemic failure.
Three routes to a stablecoin of your own
The three routes differ in who acts as the issuer, and that choice decides the rest of the build.Circle's xReserve belongs to the provider route. With xReserve, a blockchain team deploys USDC-backed stablecoins on its own chain, and the USDC is held in Circle-deployed contracts. If a provider fits, Protofire's Paxos, Bridge and Circle integration pages cover the build around that provider. Our guide to stablecoin models compares the fiat-backed and collateral-backed designs. Liquity V2 is source-available under BUSL 1.1. Liquity's docs say a commercial deployment needs approval from Liquity AG. The Liquity V2 LICENSE file sets a Change Date of 1 September 2027. After that date, GPL v2 or later applies to the version in that file. Where Liquity AG approves, Protofire starts from V2 code. Otherwise we write new contracts, and the approval is between you and Liquity AG.
Who issues and holds the reserve
Issued for you by a provider: The provider issues the token and holds the reserve. Paxos says it will "issue and manage the asset as a regulated trust, hold reserves in segregated accounts, and handle attestation and redemption" (Paxos). Bridge says it "handles reserve management, compliance, and infrastructure" (Bridge).
Fiat-backed, under your own license: Your firm issues the token and holds the reserve. Under the GENIUS Act, your firm is a permitted payment stablecoin issuer. Under MiCA, your firm is a credit institution or an e-money institution.
Collateral-backed, on your own contracts: Your protocol issues the token. Users lock collateral and mint against it. Your counsel decides how the law classifies the token.
What it leaves you to build
Issued for you by a provider: You fit the token into your chain, wallets and apps, and you build the integration with the provider. Paxos says it issues "white-label and partner assets only".
Fiat-backed, under your own license: You build mint and burn contracts and a reserve feed. The GENIUS Act requires the issuer to have the technical capability to comply with a lawful order (Sec. 4(a)(6)(B)). So the contracts need controls to freeze, seize or burn tokens on such an order.
Collateral-backed, on your own contracts: You build the collateral set, liquidation thresholds and mint caps. You also build the oracle integration and a stability pool. Liquity's docs call the stability pool its primary liquidation mechanism.
What it leaves you to run
Issued for you by a provider: You run less of the issuance itself. Paxos says it handles attestation and redemption. Bridge says it manages the complete token lifecycle, minting and burning included.
Fiat-backed, under your own license: You run mint and redemption. The issuer must publicly disclose its redemption policy (Sec. 4(a)(1)(B)). A supervised person must hold the reserve and the issuance keys in custody (Sec. 10(a)).
Collateral-backed, on your own contracts: You run parameter changes through a multisig that your signers hold. The design also assumes sound collateral and dependable price oracles, as Liquity's README states.
What Protofire delivers in a native stablecoin build
Collateral and risk design
Protofire agrees on the collateral set with you and checks each asset for liquidity and oracle coverage. Your reviewer then sees which assets back the token, where positions close and how much can be minted.
Issuance and redemption contracts
Protofire writes the token and its mint and burn paths from Liquity V2 code where Liquity AG approves its use, or as new code. Your engineer deploys them from your key.
Price feeds, liquidation and stability modules
Minting and liquidation need a price you can defend. Protofire integrates Chainlink or DIA oracles through our oracle integration service and builds the liquidation and stability modules. For a collateral-backed design, we can add an optional peg-stability layer.
Proof-of-reserve feed and reserve reporting
For an asset-backed token, Protofire wires a proof of reserve feed and the reserve reporting around it. Other systems can read the reserve figure, and holders and lenders see it next to your own reports. A Chainlink feed reports a reserve value from its configured source. The examination by an accounting firm is a separate document.
Frontend, SDKs and subgraph for your operators
Protofire builds a frontend template, SDKs and a subgraph, so your operators can follow mints, redemptions and collateral ratios without reading raw logs. We put mint caps and parameter changes behind a multisig that your signers hold.
Code prepared for an outside audit
Protofire prepares the code for an outside audit firm, in a state its reviewers can work with. We then fix the audit findings.
How stablecoin development with Protofire works
The build starts from counsel's answer on the issuer, because the contracts take their shape from that answer.
- Step 1
Route and legal classification
You and counsel choose a route and decide how the law classifies the token. Protofire designs around counsel's answer. - Step 2
Collateral and risk parameters
Protofire agrees with you on the assets and on the liquidation threshold, mint cap and oracle for each asset. We flag thin liquidity or oracle coverage early. - Step 3
Contracts, price feeds and reserve feed
Protofire writes or adapts the issuance and redemption contracts and integrates the oracles. We build the liquidation and stability modules. For asset-backed designs, we connect the reserve feed. - Step 4
Tooling and audit preparation
Protofire builds the frontend, SDKs and subgraph. The code then goes to an outside audit firm, and we fix the findings afterwards. - Step 5
Deployment with your key
Deployment scripts and parameters are handed over, and your engineer deploys with your key. Mint caps and parameter changes are behind a multisig that your signers hold. You own the code and the keys.
How work with Protofire starts
A first call with Protofire needs answers to three questions.Which chain or product is the token for, which route are you weighing, and who will hold the license and the keys? The full process is on how we work.
- 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.
Our record: reserve data, Chainlink, MakerDAO tools and Somnia
Protofire's record covers reserve data, the Chainlink layer, tools for MakerDAO's collateralized debt positions and Somnia's oracle stack.
Reserve-data pipeline for a large auditing firm
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 reserve feed depends on the same kind of data work.
Chainlink and CCIP
Protofire is a Chainlink core contributor and helps maintain Chainlink CCIP. Chainlink feeds are the price and reserve layer of a native stablecoin build.
Two tools for MakerDAO (now Sky)
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, case study). The repositories of both tools are archived.
Somnia's oracle stack
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). A chain's stablecoin needs a price layer of that kind.
When a native stablecoin build with Protofire does not fit
The issuer role, the license and the demand for the token remain with you.
- You want an issuer. Protofire is not the issuer and holds no license, no reserve and no client funds or keys. Protofire gives no legal opinion. Your counsel owns the white paper or the approval file.
- You want mint and redemption run for you. Mint and redemption remain with the issuer after launch. Protofire builds the tools. If Protofire runs them for you, it does so under a written scope.
- You expect the token to bring users on its own. Eric Queathem, founder and CEO of Velocity, spoke at the Protocol Roundtable on 15 October 2026. He said: "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."
- You want an audit to settle the risk. An outside audit reviews the code and does not guarantee the absence of bugs.
FAQ
What is a native stablecoin?
Who can build a native stablecoin for a chain or a fintech?
Who may issue a stablecoin, and what does the GENIUS Act ask of the issuer?
What does MiCA ask for a euro token?
Can a native stablecoin pass income to its holders?
Does a proof-of-reserve feed prove the reserves are there?
How does a collateral-backed token keep its peg, and what happens when the stability pool is empty?
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.
