HostDeFi › Library › Is PYUSD safe on Ethereum?

Is PYUSD safe on Ethereum? The proxy every PayPal dollar rides on

PayPal USD on Ethereum grades B (80): an upgradeable proxy, controls not assessed in this snapshot — and ~$71M of real on-chain liquidity backing a ~$2.78B stablecoin.

Token safety check · snapshot September 27, 2026 · not financial advice

PYUSD — PayPal's US-dollar stablecoin issued by Paxos — is ~$2.78B in market cap, ~108,000 holders, 250 days into its on-chain life, with ~$71M of tracked Ethereum liquidity — the deepest pool of any token in this series' B-band. On our September 27, 2026 read it grades B, score 80 on two warns, no bad flags: an upgradeable proxy contract and contract-level controls not assessed in this snapshot.

It's the second proxy-flagged regulated stablecoin this series has written (the first is USDC on Arbitrum) — and the pair now forms a pattern worth naming: the regulated dollar's standard shape is a proxy.

Why every regulated stablecoin is a proxy

A fiat-backed stablecoin can't afford an immutable contract — the operator must be able to respond to legal orders, patch bugs, and evolve compliance features, and an upgradeable proxy is how that requirement ships as code. USDC's deployments carry the same flag for the same reason; Paxos's PYUSD is no different in kind, just earlier in its on-chain history at 250 days.

The practical content of the flag here: Paxos can repoint the logic behind the address you hold — change minting rules, add restrictions, re-author the admin surface — without your signature or even a new contract. The redeemable-dollar guarantee lives in the issuer's legal obligations, not in contract code that can't change. The B is the checklist recording that distinction.

The liquidity the B-band rarely shows

~$71M of tracked on-chain liquidity is the standout number on this page — deeper than USDC-Arbitrum's ~$79.5M-relative scale and an order of magnitude beyond anything else in the B-cohort. There is no liquidity warn here: the checklist itself calls the pool "workable for the token's size." For a holder, that's the difference that matters in the mundane case — an ordinary on-chain exit isn't a market event.

The 108K holder count over 250 days tells the adoption story the liquidity implies: PYUSD isn't a token that exists on paper. It's a live payment rail with a wallet base that grew into the proxy's shadow — every one of those holders holding a contract whose rules Paxos can rewrite.

What the unassessed-controls warn means for PayPal's coin

Of all the "controls not assessed" warns in this series, PYUSD's is the one where the unassessed surface is the most predictable: Paxos-issued stablecoins carry the standard regulated-coin admin set — a minter, a pauser, an asset-freezer for sanctioned or compromised addresses. The snapshot didn't enumerate them, which is why the warn fires — but the reason they're almost certainly there is the same reason the proxy is there: a regulated dollar instrument is required to be controllable.

So the honest read isn't "unknown risk" — it's "known shape, unenumerated surface." The B holds the proxy flag and the unassessed flag together, and the two are really one statement: this is an institution-operated token, and institution-operated tokens are controllable by design.

The PayPal factor, priced correctly

PYUSD's unusual feature is distribution: it's the only stablecoin that ships inside a mass-market consumer payments app. That reach is why 108K wallets hold it in 250 days — and why the proxy flag matters more here, not less. A retail holder who received PYUSD through PayPal likely never read a contract at all; the checklist's job is to say on their behalf that the thing they hold is a revocable-rules instrument backed by an issuer's promise.

That's not a criticism — it's the honest shape of regulated money on-chain. The B is the grade a proxy-kept stablecoin earns when everything else is clean: workable liquidity, verified source, no adverse powers found in the surface that was checked.

The stablecoin B-cohort, compared

PYUSD is now one of four regulated dollars at B in this series — alongside USDC-Arbitrum, RLUSD, and USDG — and the four pages form a clean taxonomy of the same architecture at different ages. All four carry the proxy flag; all four carry controls-not-assessed; what separates them is pool depth and deployment age. PYUSD's ~$71M pool is the deepest of the cohort and the reason its read feels the most settled: the contract is the same shape as the others, but the market has had 250 days to grow around it, and the liquidity shows it.

That comparison is the useful answer to "is PYUSD safer than X": within the regulated-dollar cohort, the grades track deployment maturity and pool depth, not issuer quality. The checklist can't rank Paxos against Circle — it can rank a 250-day deployment with a $71M pool against an 11-day-old one with $12.5M, and it does.

What would move PYUSD's grade

The B's path upward is the same checklist shape as the other proxy stablecoins: enumerate the admin surface (removes the unassessed warn), keep the pool deep (already there), age the deployment (already accruing), and the one thing that would lift it to an A — burn or timelock the upgrade key — is the thing a regulated issuer structurally can't do. PYUSD's ceiling is B-by-architecture, and the page's value is saying that plainly: the grade isn't a problem to fix, it's the honest label for a fiat-backed instrument.

The path downward is the one the flag exists for: a bad upgrade, a key compromise, an exercise of the freeze power at scale — any of those lands through the proxy and would show in a re-read. The dated snapshot is the check on it — and on a token this clean, the checklist's own discipline is the content: two warns, nothing bad, everything dated, nothing assumed.

Holding it, honestly

If you hold PYUSD on Ethereum you hold a Paxos-issued, PayPal-distributed dollar token behind ~$71M of real on-chain liquidity — one of the best exits in the B-band — under a proxy contract whose controls this snapshot didn't enumerate — with a holder base that never read the contract and a brand that never asked it to. The trust object is the issuer, not the code; the grade's job is to keep that visible. For most holders that's exactly the trade they signed up for when they held a regulated stablecoin — the B just makes sure it's a visible one.

Frequently asked