PUSD is a par-backed universal stablecoin on Push Chain. Deposit USDC or USDT from any supported chain, receive PUSD 1:1 on Push Chain. Burn PUSD, receive a reserve token back. Rules-based, redeemable, reversible.
PUSD+ is its yield-bearing companion — a 6-decimal NAV-bearing ERC-20 minted by depositing PUSD (or any reserve token in one shot) into PUSDPlusVault. NAV grows monotonically as the vault collects LP fees from Uniswap V3 stable/stable pools.
- Chain: Push Chain Donut Testnet (chain ID 42101)
- RPC:
https://evm.donut.rpc.push.org/ - Explorer: donut.push.network
| Contract | Proxy address |
|---|---|
| PUSD | 0x774c799646bB60103e38Fd65b18D81bbDD1Aa760 |
| PUSDManager | 0x775A23E81fCd1f9C2997663b45401bEe80e4242A |
| PUSDPlusVault | 0x9C7A8Bae46d4dd0496bD3016d1D8FB9e83E68F16 |
| InsuranceFund | 0x995348eABc39ecdF591b8A93B3568Dc3C1c0BBAD |
All four are UUPS proxies (Deployment 6, 2026-05-18). The source of
truth for live addresses is contracts/deployed.txt
(newest deployment first) — update this table from there.
push-chain-pusd/
├── app/ ← React + Vite dApp (see app/README.md)
├── contracts/ ← Foundry contracts (see contracts/README.md)
├── docs/ ← Protocol design, ADRs, internal research
├── scripts/ ← Utility scripts
└── DEPLOYMENT.md ← Deployment runbook
Agent context is served, not stored in the repo. Point any LLM-based coding tool at the deployed entry points:
- llms.txt: https://pusd.push.org/llms.txt
- Skill (full integration guide): https://pusd.push.org/agents/skill/push-pusd/SKILL.md
The Skill is self-contained — addresses, both write paths, every code example, ABI fragments, common mistakes. One prompt is enough:
Read https://pusd.push.org/agents/skill/push-pusd/SKILL.md and
integrate PUSD mint + redeem into my dApp.
The source for both files lives in app/public/.
- Mint PUSD — call
PUSDManager.deposit(token, amount, recipient)after approving the reserve token. PUSD is minted 1:1 minus anysurplusHaircutBps(currently 0% on every token; cap is 1000 bps in v2). - Redeem PUSD — call
PUSDManager.redeem(pusdAmount, preferredAsset, allowBasket, recipient). PUSDManager holdsBURNER_ROLEand burns directly — no PUSD approval needed from the caller. AbaseFee(currently 5 bps) is deducted. - Basket fallback — if the preferred asset is short on liquidity and
allowBasket = true, the manager pays out a proportional basket of all reserve tokens instead of reverting. - Mint PUSD+ — call
PUSDManager.depositToPlus(tokenIn, amount, recipient).tokenInmay be PUSD (wrap path) or any enabled reserve (direct path). Under v2.1, the direct path forwards reserves straight to the vault (no intermediate PUSD mint); the wrap path basket-redeems caller's PUSD into vault inventory. PUSD+ is minted at pre-deposit NAV; quote withPUSDPlusVault.previewMintPlus. - Redeem PUSD+ — call
PUSDManager.redeemFromPlus(plusAmount, preferredAsset, allowBasket, recipient). The vault burns PUSD+ at current NAV; v2.1 drains the user's preferred asset first when sourcing PUSD. If the vault can't fulfil instantly, the residual is queued and settled byPUSDPlusVault.fulfillQueueClaim(queueId)once liquidity is available. No fees on the compose path.
Latest deployment: Deployment 6 (2026-05-18) — fresh full redeploy of all four proxies for the new 10-token reserve wrapper set; BNB pair naming migrated
.bnb→.bscin the manager registry. Latest contract-logic upgrade: V2.1 (2026-05-06, Deployment 5) — PUSDManager.depositToPlus rewritten to send reserves directly to the vault instead of round-tripping through the manager, and PUSDPlusVault.rebalance made permissionless after a cooldown (1h default, capped at 24h; KEEPER bypasses). See ADR 0006 for the full rationale.
Cross-chain mints and redeems (user holds the stablecoin on an external chain) are handled by the Push Chain universal transaction layer — see app/README.md for the SDK call shapes.
# Contracts
cd contracts
forge build
forge test
# dApp
cd app
yarn install
yarn dev # http://localhost:5173MIT