Paxos Stablecoin Minting and Redemption, Onchain
A step-by-step walk through Paxos minting and redemption: what the issuer does off-chain, what appears on the blockchain, and how to trace each mint and burn.
When a Paxos-issued stablecoin is minted, no existing coins move. The supply-changing events are a mint (tokens created and sent to a holder) and a burn (tokens destroyed on redemption), and both originate from a Paxos-controlled contract that widens or shrinks total supply rather than transferring existing balances. Everything a customer experiences (send dollars, receive tokens; return tokens, receive dollars) is orchestrated off-chain, and only the token creation and destruction leave a permanent onchain trace.
According to Allium's stablecoin dataset (as of 2026-09-18), total onchain stablecoin circulating supply sits at $335B, with USDG (a Paxos-issued token in the Global Dollar Network) at $3.3B, tracked alongside the majors led by USDT at $192.9B and USDC at $78.0B. Circulating supply is not a market feed. It is the running sum of every mint minus every burn, which is exactly why the mint and redeem mechanics below matter for anyone reading the numbers.
Key takeaways
- Minting and redemption change supply; ordinary transfers do not. A mint increases circulating supply, a burn decreases it, and a peer-to-peer send leaves supply unchanged.
- Paxos operates the token contracts for the stablecoins it issues (including PYUSD for PayPal and USDG in the Global Dollar Network), so mint and burn instructions come from Paxos-controlled addresses.
- On Ethereum-style deployments a mint onchain is a Transfer event from the zero address to the recipient. On the same deployments a burn is a Transfer to the zero address (or a dedicated burn function).
- The dollar leg (customer wire in, redemption payout) happens in the banking system and is not visible onchain. Only the token leg is.
- To read supply correctly you have to separate mint and burn events from the flood of ordinary transfers, per chain, and net them.
The two events that actually change supply
A Paxos stablecoin like PYUSD is an ERC-20 style token with a controlled supply. Paxos, as the issuer, holds the authority to create and destroy tokens. That authority is what makes minting and redemption distinct from every other transaction the token is involved in.
Per PayPal's PYUSD overview, the token is issued by Paxos Trust Company and is designed to be redeemable one-for-one for US dollars. The redeemability commitment lives off-chain in Paxos's reserves and banking relationships. The mint-and-burn mechanic expresses that claim on the blockchain: a dollar comes in, a token is minted; a token comes back, it is burned and a dollar goes out.
How a mint happens, step by step
The customer-facing flow (a business buying PYUSD, or a user funding a PayPal balance) hides most of the machinery. Here is the sequence, split into the off-chain leg and the onchain leg.
- Dollars arrive off-chain. A customer or platform sends USD to Paxos through the banking system. This is a wire or ACH movement and produces no blockchain record.
- Paxos confirms and instructs a mint. Once funds settle and compliance checks clear, Paxos issues a mint instruction from a controlled address.
- Tokens are created onchain. The contract increases total supply and credits the recipient address. On the chain this appears as a Transfer event from the zero address (0x000...000) to the recipient.
- Reserves back the new tokens. Paxos reports that incoming dollars are held in reserve assets backing outstanding supply, in disclosures it publishes off-chain.
The onchain observer sees only step three. Total circulating supply goes up by the minted amount at the moment that Transfer-from-zero event lands.
How a redemption (burn) happens, step by step
- Tokens are returned to Paxos. A holder sends the stablecoin back to a Paxos-designated address, or initiates redemption through a platform that does so on their behalf.
- Paxos burns the tokens. The contract destroys the returned tokens. Onchain this is a Transfer event to the zero address, which reduces total supply by that amount.
- Dollars go out off-chain. Paxos releases the corresponding USD from reserves back to the redeemer through the banking system. This leg is invisible on the blockchain.
The order matters for anyone reconciling supply. A redemption shows up as a burn onchain first, and the dollar payout follows through rails you cannot see from a block explorer.
What the events look like, in fields
On an ERC-20 deployment the clean signal for both operations is the counterparty being the zero address, and in routine operation mint and redeem are what put it there. Treat that as the Ethereum-style pattern rather than a universal rule: implementations differ by chain, and some use a dedicated burn function or a different sentinel address instead.
| Operation | From | To | Effect on supply | Off-chain leg |
|---|---|---|---|---|
| Mint (issuance) | 0x000...000 (zero address) | Recipient | Increases by amount | USD received into reserves |
| Burn (redemption) | Holder / Paxos address | 0x000...000 (zero address) | Decreases by amount | USD paid out from reserves |
| Ordinary transfer | Wallet A | Wallet B | No change | None |
A worked example: net supply from a day of activity
Suppose a Paxos-issued token records the following in one day on a single chain:
- Three mints: 10,000,000 + 4,500,000 + 500,000 = 15,000,000 tokens minted
- Two burns: 3,000,000 + 1,200,000 = 4,200,000 tokens burned
- 18,000 ordinary transfers moving tokens between wallets
Net change in circulating supply for the day is 15,000,000 minus 4,200,000, which equals +10,800,000 tokens. The 18,000 ordinary transfers, no matter how large in aggregate volume, contribute zero to that figure. This is a common mistake in reading stablecoin data: treating transfer volume as if it were issuance. Volume measures usage. Only mints and burns move supply.
Why separating mint and burn events is a data problem
A Paxos stablecoin does not always live on one chain. PYUSD, for example, is issued on multiple networks, and USDG is designed for cross-chain circulation. To produce a correct circulating-supply number for a single issuer, every mint and every burn on every chain has to be identified, tagged as a supply-changing event rather than a transfer, attributed to the right issuer and token, converted to a consistent USD value, and then netted. The zero-address pattern does not exist on some chains at all: Solana records mints and burns as distinct instructions rather than transfers to a sentinel address, some tokens use an explicit burn function instead of a transfer to zero, and bridging can create mint-and-burn pairs that must be recognized as bridge mechanics rather than genuine issuance.
The hard part is field-level consistency: the same event has to resolve to the same fields (issuer, token, event type, amount, USD value and chain) whether it lands on Ethereum, Solana or anywhere else. Allium normalizes those records across 150+ blockchains into a standardized stablecoins dataset so a mint on one chain and a burn on another net into a single supply figure. Allium data has been cited in Federal Reserve research and powers onchain stablecoin reporting that depends on getting this mint-and-burn accounting right.
For builders who need the issuance side directly, the mint and burn events are the raw material behind an issuance view, and they are what any reliable supply chart is built from.
Frequently asked questions
Does minting a Paxos stablecoin move existing coins?
No. A mint creates new tokens and sends them to the recipient, appearing onchain as a Transfer from the zero address. Existing balances are untouched, and total circulating supply increases by the minted amount.
What does a redemption look like on the blockchain?
Redemption produces a burn: the tokens are destroyed, shown as a Transfer to the zero address (or via a dedicated burn function), which reduces total supply. The matching US dollar payout happens off-chain through the banking system and is not visible onchain.
Who can mint and burn a Paxos-issued stablecoin?
Paxos, as the issuer, controls the token contract and holds the authority to mint and burn. Mint and burn instructions originate from Paxos-controlled addresses, not from ordinary holders.
Is transfer volume the same as newly minted supply?
No. Ordinary transfers move tokens between wallets without changing total supply. Only mints and burns change circulating supply, so a day with huge transfer volume can still show almost no net issuance.
Why is a single stablecoin's supply hard to measure across chains?
A Paxos stablecoin can be issued on several networks, and mints, burns and bridge mechanics differ in implementation across chains. A correct supply figure requires identifying every supply-changing event, attributing it to the right issuer and token, and netting mints against burns across all chains.
Where do the dollars sit after a mint?
The US dollars received during minting are held in reserve assets that back the outstanding tokens. That reserve information is reported by the issuer off-chain and does not appear on the blockchain.
Interested in learning more about Allium’s stablecoin data? Speak to someone on the team.
Informational only. Not investment, legal, accounting or tax advice. Allium has commercial relationships with companies named in this post.
