PUSD is a USDT-wrapped settlement rail with an explicit “review gate” on exits

Pleasing USD (PUSD) is positioned as the Pleasing Golden ecosystem’s dollar unit: you bring USDT in, receive PUSD 1:1, then use PUSD to trade into on-chain gold (PGOLD) or to stake for rewards. The project’s own token features describe PUSD as fully USDT-backed and 1:1 redeemable to USDT, but they also make the control surface clear: redemption requires compliance checks, and “in rare cases” addresses can be restricted or blacklisted.

That combination is the tokenomics story. PUSD is not trying to be the most censorship-resistant stablecoin on Arbitrum. It is trying to be the most operationally useful stable unit for a precious-metals venue that links on-chain trading to off-chain metal businesses. The how it works page frames three roles: Depositors provide capital (USDT in, PUSD out, optional staking), Investors use PUSD as the transactional rail for metals exposure, and Operators monetize physical metals flows to fund yield and liquidity.

As a treasury risk manager, I read that as: PUSD’s survivability depends less on “emissions design” and more on reserve operations and redemption throughput under stress. If the redemption gate jams, everything else becomes cosmetic-consistent with core design principles for token-economy reviews.

Supply and issuance: a capped token that already sits at the cap

On Arbitrum, the PUSD contract address published in the official docs is 0xC8Fb643D18F1e53698CFDa5c8Fdf0cdC03C1dBec.

Arbiscan’s Arbitrum token page shows the token as an ERC-20 with 18 decimals and lists a Max Total Supply of 120,000,000 PUSD.

CoinGecko, meanwhile, reports circulating supply = 120,000,000 and total supply = 120,000,000. It also shows “max supply = ∞”, which conflicts with Arbiscan’s displayed cap. Practically, the relevant point is that CoinGecko’s tracked circulating supply equals 120,000,000, which matches Arbiscan’s max total supply figure.

Tokenomics implication: if the system wants to grow beyond 120,000,000 PUSD in the future, it likely needs either (a) a new token deployment, (b) a contract upgrade that changes supply constraints, or (c) multi-chain supply expansion that does not rely solely on the Arbitrum deployment. Any of those paths increases governance and operational risk, because it changes the “hardness” of the backing and the credibility of the peg under governance discretion.

Distribution-wise, PUSD behaves like an inventory-backed stable asset rather than a governance token. There is no published allocation schedule or emissions program in the primary docs for PUSD itself. What exists is issuance against USDT inflows and redemption back into USDT, with optional staking rewards paid in PUSD.

Mint/redeem mechanics: 1:1 on paper, operationally gated in practice

On-ramp: the user guide describes swapping on-chain USDT to PUSD at a 1:1 ratio with a minimum of 1 USDT per swap.

Off-ramp: the redemption flow is also described as 1:1 and without slippage, but it has two structural constraints that matter more than the ratio:

This is the defining trade-off. PUSD is “permissionless” for transfers and secondary-market swaps on supported chains, but the issuer keeps a staffed, compliance-aware choke point on the primary redemption path. For a stablecoin design that leans more on on-chain arbitrage than staffed exits, compare with our Frax USD review.

From a treasury perspective, this design can be rational. Off-chain metals businesses do not settle like DeFi. They have cutoffs, inventory constraints, fraud risk, and compliance exposure. A review gate can protect reserves. It can also break the stablecoin reflexivity that normally stabilizes price, because arbitrage is slower and permissioned at the exit.

The legal and compliance posture is consistent with that. The AML/CFT & Sanctions Policy states they conduct KYT/transaction monitoring and may reject funds, freeze accounts or tokens where legally permissible, request information, and restrict services when suspected illicit activity is detected.

Also note the docs’ “risk controls” clause: in rare cases, specific addresses may be restricted or blacklisted for security and legal compliance. That is not a theoretical possibility. It is stated policy.

Utility, fees, and fiscal flows: where the yield is supposed to come from

PUSD has two core utilities inside the product:

The on-chain trading venue charges a 0.04% trading fee on swaps between PUSD and PGOLD, per the user guide.

Price discovery for the gold leg is described as following an on-chain XAU price stream from Chainlink.

On the yield side, the docs frame PUSD as a “synthetic dollar” that is intended to finance physical metals infrastructure. They state a target of 6-10% APR and distinguish between PUSD (non-yield-bearing) and “staked PUSD” (yield-bearing, potentially subject to redemption periods).

The staking UX makes the liquidity trade explicit: users choose a lock-up period, redemption is unavailable during the lock-up, and the documented minimum stake size is 1,000 PUSD.

One sentence in the docs is doing a lot of work for treasury risk: they state that “idle capital is preferentially held in physical gold as a defensive base and inflation hedge.”

That has two readings:

The public docs do not resolve that ambiguity. The “Reserve Report” page exists in the docs navigation, but it does not contain an accessible reserve breakdown in the version available via GitBook.

As a result, the PUSD “fiscal flows” model is conceptually clear but operationally under-specified. Users are meant to earn rewards funded by a mix of on-chain activity and off-chain precious-metals business income. What is missing is the budget policy that prevents a yield target from turning into a promise.

Governance and control surface: upgradeability, compliance powers, and parameter discretion

PUSD’s on-chain control plane is meaningfully centralized. Two datapoints matter:

Independently of any intent, upgradeability changes the risk profile. It means the rules governing minting, transfers, and blacklisting can evolve. That is workable if the project publishes strict upgrade governance and time-lock constraints. Those constraints are not documented in the primary materials surfaced through GitBook and the explorers above. We discuss similar admin-control trade-offs in our Avant USD review.

On the “policy” side, the docs are explicit about legal jurisdiction and enforcement posture. The Terms of Use identify the entity as Pleasing International Limited and state the governing law as Hong Kong SAR, with disputes resolved via HKIAC arbitration.

On the “regulated footprint” side, the docs publish certificates titled “Certificate of Registration for Category A Registrant” and “Certificate of Registration for Category B Registrant” issued by Hong Kong’s Customs and Excise Department under the Anti-Money Laundering and Counter-Terrorist Financing Ordinance (Cap 615). The Category B certificate shown lists Pleasing International (HK) Limited with validity from May 14, 2024 to May 13, 2027.

Finally, smart contract risk around the yield leg has at least one disclosed audit. The docs link a Beosin audit report for “Pleasing Golden Yield” dated January 16, 2026, describing a staking contract that supports flexible and fixed-term pools, with owner-controlled pool parameters.

The audit notes a centralization risk in an owner withdrawal function and reports it as fixed, and it also flags parameter-change design issues and a scenario where insufficient reward reserves could lock user withdrawals, both marked as fixed.

This is good hygiene, but it is not the same thing as a reserve attestation or a redemption stress test.

Risk analysis: the peg is only as strong as the redemption queue

Dominant risk: Liquidity and reserve governance risk driven by gated redemption and off-chain balance sheet transformation.

PUSD’s promise is straightforward on the surface: 1 PUSD equals 1 USDT in and out. The mechanism is more conditional. USDT-to-PUSD swaps are instant in the app and 1:1.

But PUSD-to-USDT redemption is constrained by a 10,000 PUSD minimum and an “Under Review” T+1 approval process.

That creates a two-tier market:

Under normal conditions, this might be fine. In stress, it becomes the system’s failure mode. If a stable asset cannot be redeemed quickly at scale, the market starts pricing the probability and duration of being stuck. The peg then becomes an expectations game, not a mechanical arbitrage. For another case study in redemption and governance trade-offs, see our DOLA tokenomics review.

The second layer of the dominant risk is reserve composition uncertainty. The docs simultaneously claim “fully USDT-backed” and describe “idle capital” being preferentially held in physical gold.

If reserve assets are always USDT and always available, then the main risk is operational delay and compliance denial. If reserves are partly deployed into inventory, financing, or hedging for metals operators, then PUSD starts resembling a credit instrument with a stable face value. That is not automatically bad. It can even be sustainable. It just needs explicit buffer policy, transparent reporting, and conservative payout discipline.

Today, the primary docs do not publish a PUSD-specific reserve breakdown or cadence of attestations. The “Reserve Report” page in the docs is not populated in the accessible version, which lowers confidence in parameter stability and raises the probability that a future change to policy is “announced after the fact.”

One more accelerant is market liquidity. As of March 4, 2026, CoinGecko shows PUSD trading on a single tracked DEX venue and reports very low 24-hour volume, which implies thin secondary liquidity at the margin.

In practice, that means the redemption gate is not just a compliance control. It is the main stabilizer. If it works smoothly, PUSD can behave stable enough for its niche. If it slows, the market has limited shock absorbers.

  1. Redemption suspension or backlog
    Trigger: a surge in redemption requests, a compliance event, or a reserve liquidity shortfall that slows approvals.
    Mechanism: T+1 approval becomes T+N, redemptions become selectively delayed, and secondary market price starts discounting time-to-cash and rejection risk given minimum redemption sizing.
    Who bears it: PUSD holders, with the largest burden on smaller holders who cannot use the 10,000 PUSD primary redemption route.
    Measurable indicators: on-chain PUSD price deviations vs USDT; increase in “Under Review” count and average approval time in the dApp UX; widening spreads and falling depth on DEX pools tracked publicly.

  2. Admin action and upgrade risk
    Trigger: contract upgrade, emergency controls, or a policy-driven restriction event (sanctions, exploit response).
    Mechanism: upgradeable proxy design plus stated blacklisting powers can change transferability, fees, or mint/burn behavior, creating discontinuous risk for holders and integrators.
    Who bears it: DeFi integrators (sudden token behavior changes), liquidity providers, and end users caught on the wrong side of a restriction.
    Measurable indicators: proxy implementation changes on-chain; public communications of policy updates; increases in restricted-address events; third-party monitoring alerts about proxy-admin activity.

  3. Yield budget mismatch
    Trigger: staking rewards set (or market-implied) above sustainable net revenue from trading fees and off-chain operator income, or a drawdown in operator profitability.
    Mechanism: reward obligations consume reserves or force riskier deployment of backing assets, increasing the chance that redemptions are slowed or constrained. The audit history also highlights that insufficient reward reserves can create withdrawal issues in staking systems if not engineered carefully.
    Who bears it: stakers first (delayed rewards), then all PUSD holders (peg confidence), and finally operators (liquidity contraction).
    Measurable indicators: effective reward rates vs observable fee throughput (0.04% trading fee volume proxy); changes in lock-up participation; any documented reward “top-ups” or parameter tightening (higher mins, longer settlement windows).

If you are underwriting PUSD as a treasury asset, you are underwriting a managed redemption instrument with compliance-enforced exits and an opaque reserve operations layer. That can still work. It just needs disclosures that match the control reality. For more due-diligence frameworks like this, see our research reports.

If you need lightweight tokenomics consulting for a PUSD-style design review, the most productive scope is not “incentives brainstorming.” It is a reserve policy memo, a yield budget constraint, and an upgradeability and redemption-controls threat model tied to measurable KPIs-work that typically fits under our tokenomics consulting scope.



This article is part of our Tokenomics Deep Dive series.