Stablecoin Distribution for Issuers Who Need More Venues and Chains
For issuers of a stablecoin, e-money token or fund token, Protofire builds the evidence each venue reads, distributor APIs and new-chain deployments. Venues decide each listing, and you keep the 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
Getting an issued token accepted by more venues and chains
In stablecoin distribution work, Protofire assembles the evidence on contracts, roles and reserves that exchanges, payment firms, wallets and Aave's reviewers read. We build the APIs distributors connect to, and we deploy the token on each new chain with a rate limit per route. The venues decide, and your multisig or custody platform keeps the admin roles.
For example, your euro token passed an exchange's review last quarter. Now the board wants it on a second chain, and everyone who approved it will ask what changed.
Layers between a token and its holders, and who is responsible for each
Venues decide each listing. Your keys hold the admin roles on each chain, and Protofire builds the layers around those keys.
Listing decisions
Evidence and distributor interface
Reserve feed and mint check
Cross-chain layer
Token contracts and roles
New chains and upgrades reopen a token's reviews
A new chain, a contract upgrade or a new admin key reopens reviews the issuer already passed.Aave's technical listing framework was adopted by Snapshot on 13 July 2026. The framework names new chain deployments, new bridge routes and changes to role holders as material changes. It wants the assessment refreshed "immediately when a material change occurs".
Each added chain also needs its supply counted against the same reserve. If nothing is updated, the token is deployed on the new chain while its earlier reviews are still open.
What each channel checks before it accepts your token
Each channel checks a different part of your evidence, and several channels approve nothing at all.Protofire's guide to where a stablecoin should be distributed first compares the channels by holders, volume and fit.
EU exchanges
What the channel checks or decides: The platform assesses the reliability of the technical solutions that the token uses, under its own operating rules (MiCA, Article 76).
What you supply: You supply verified contracts and audit links for each chain and the white paper's token identifiers. When the platform seeks admission, you also give your written consent (Article 48).
Payment firms
What the channel checks or decides: The firm decides its coin list by region and chain.
What you supply: You supply mint and redemption APIs, webhooks and a sandbox on chains that the firm already runs.
Wallets
What the channel checks or decides: MetaMask "doesn't keep a proprietary list" and detects tokens from aggregated community token lists (MetaMask).
What you supply: You supply contracts verified on each explorer and token-list entries with the right chain ID and decimals.
Aave V3 and V4
What the channel checks or decides: Aave Labs or TokenLogic publish the business case. LlamaRisk and Aave Labs assess it, and two votes follow (Aave governance).
What you supply: You supply the role holders, mint caps and upgrade path that the framework expects. You also supply the bridge setup and audits, plus a deposit of at least 150 US dollars' worth of the token.
Morpho and DEX pools
What the channel checks or decides: A Morpho market needs no approval to create, and its oracle is fixed when the market is created.
What you supply: You choose an oracle once for each market and supply opening liquidity. Aave pauses a listing when DEX liquidity is thin.
What Protofire delivers for stablecoin distribution
One evidence file for exchanges and Aave
Exchanges and Aave draw on the same facts, so you answer once and update the file when a chain or a role changes. Protofire verifies contracts on each chain and matches audited code to deployed bytecode. We map each privileged role to its holder and limits, and we map the redemption path.
One documented API for distributors
Exchanges and payment firms onboard against one documented API. You keep a consent record for each distributor that offers your e-money token. Protofire builds mint and redemption APIs, webhooks and a sandbox. We also build a register of written consents, which records the white-paper version that each distributor's marketing must match.
One token supply across chains
Your token keeps one supply across chains, so integrators get no wrapped copy that they must treat as a second asset. Protofire deploys the token on Chainlink's Cross-Chain Token standard, Circle's CCTP for non-USDC assets, LayerZero's OFT or Wormhole's NTT. We check decimals against each venue. We place the admin roles with your multisig or custody platform.
A mint check against the reserve
A mint that the reserves cannot cover is rejected onchain. A lending market can also read the reserve onchain. Protofire connects reserve data from a custodian or an auditor to a proof of reserve feed. A mint check then reads the feed, with a staleness limit and reserve margin that follow the feed's update cycle. This is because MiCA Article 49(3) has the issuer issue tokens "on the receipt of funds".
Fixes made before a lending market reviews the token
When Paxos's USDG was proposed for Aave, BGD Labs and LlamaRisk asked for timelocks on critical flows and a bug bounty (Aave governance). Protofire makes fixes of that kind before a lending market looks at the token. We also check that a Chainlink price feed exists on each chain.
Fund units that move between eligible holders
A permissioned fund token reaches DeFi through the markets built for it. Its units can move to eligible holders alone. Protofire writes the fund's eligibility rules into the token's compliance contract. We give each venue, vault and liquidator address an identity that passes those rules, and we add a NAV feed. Our ERC-3643 development service covers the standard.
How a token deployment on a new chain runs
Before holders can use the token on a new chain, the deployment passes through a bridge standard, ESMA's register, each venue and Aave's reviewers.
- Step 1
Cross-chain standard chosen to fit your roles
The Cross-Chain Token standard, CCTP for non-USDC assets, OFT and NTT can burn the token on one chain and mint it on another. A third-party bridge, by contrast, would leave a wrapped copy that you did not issue. The four standards differ in who controls the pools and which chains they reach. - Step 2
Roles and rate limits on the new chain
Each route gets a rate limit. Your signers hold the pauser, pool owner, token admin and rate-limit roles. Aave Labs checks who can change each route's verifiers. It also asks for a timelock on critical bridge changes: "24 hours acceptable, 48 hours preferred" (Aave governance). - Step 3
New token identifier and notice to venues
ESMA's register lists one Digital Token Identifier for each chain deployment, and the USDC row has 36 (ESMA register). Kraken asks projects to "notify Kraken of contract migrations or significant tokenomic changes 30 days in advance" (Kraken). So Protofire schedules each notice ahead of the deployment date. - Step 4
Aave's review of each new chain
Aave's reviewers read each chain on its own terms. They check the contracts, the oracle path, the bridge topology and access control. Protofire hands the reviewers the refreshed file and fixes what they find. - Step 5
Supply published and reconciled each day
The new deployment gets token-list entries and explorer verification. 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. The reconciliation also counts tokens burned on one chain and not yet minted on the next. Tokens in flight are listed separately as a timing item until the mint completes.
How work with Protofire starts
A first call needs the token's contracts and chains, the venues and markets you want next, and today's holder of each admin role.Protofire sets each target channel's checklist against your evidence and lists the gaps. 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: Chainlink CCIP, a Hyperlane route and a mint design
Protofire's public record includes the cross-chain layer and a published design for mint control.Both apply to a stablecoin distribution program.
Chainlink CCIP
Protofire is a Chainlink core contributor and helps maintain Chainlink CCIP. CCIP is the protocol behind the pools of Chainlink's Cross-Chain Token standard. Our CCIP integration page lists what we build on CCIP.
The VANA warp route on Hyperlane's registry
Hyperlane's registry records the VANA warp route between Ethereum and Vana as "Deployed by Protofire" (Hyperlane registry). The entry was merged in December 2024. Protofire built the bridge interface for moving assets onto Vana, as one part of a wider build. See our cross-chain integration page.
A published blueprint for mint authority
Protofire's reserve-capped mint controls blueprint shows how an issuer divides mint authority and rate-limits it against the reserve.
When distribution work with Protofire does not fit
Some gaps come down to a venue's decision, a legal file or a license.
- You need a listing or a market maker. Venues decide each listing. Kraken says "there is no paid fast-track for review" and leaves liquidity to projects. Protofire sells neither listings nor market making.
- You distribute USDC or EURC, or you need one EVM chain and one bridge. Circle's CCTP already moves USDC and EURC. Registration for Chainlink's token standard is self-serve for a Solidity team.
- Your gap is legal. White papers, consent agreements and key information documents belong to your counsel. No engineering work supplies the MiCA white paper that an EU exchange expects.
- You want an issuer. Protofire is not an issuer and holds no reserves and no license. Your auditors provide the reserve attestation.
FAQ
What is stablecoin distribution?
Who can build stablecoin distribution for an issuer that wants more chains, venues and apps?
What does MiCA ask of a firm that offers an e-money token someone else issued?
Can a permissioned fund token reach the same DeFi markets as a stablecoin?
Banks and brokers distribute fund units as financial instruments under MiFID II, outside MiCA. Protofire's share class blueprint and fund tokenization blueprint cover distribution through banks and brokers.
Can Circle's CCTP move our own stablecoin between chains?
Who holds the mint, bridge and admin keys after launch?
Can an EU exchange keep a stablecoin that has no MiCA white paper?
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.
