Skip to main content

What Is Plume pUSD? The Stablecoin Powering Real World Asset Finance

Plume pUSD is a fully-backed stablecoin for Real World Asset Finance. Learn how pUSD works, its backing, and role in RWAfi.

Written by Eco

Plume USD (pUSD) is the native settlement stablecoin of Plume Network, a Layer 1 blockchain purpose-built for real world asset finance (RWAfi). Each pUSD is backed 1:1 by USDC held in a BoringVault on Plume Chain, mints and redeems with zero protocol fees, and is non-yield-bearing by design. pUSD is not itself a tokenized real world asset. It is the dollar rail that makes tokenized real world assets tradeable on Plume.

That distinction matters. Most coverage groups pUSD with stablecoins like Ondo USDY, BlackRock BUIDL, or Mountain USDM under one "RWA stablecoin" umbrella. The mechanics are different. USDY and BUIDL are primary RWA stablecoins, collateralized by tokenized US Treasuries and pay yield to holders. pUSD is a secondary RWA stablecoin, a fiat-stablecoin wrapper that exists so the primary tokens have a neutral, non-yield, non-security medium of exchange to be priced and traded against. Plume documents pUSD as the chain's transactional dollar, not a yield product.

This article explains pUSD's mechanism, where it sits in the broader RWA stablecoin taxonomy, how it compares to USDY, BUIDL, and USDM on backing and yield, how it coexists with WLFI's USD1 on Plume, and how users mint, deploy, and redeem it inside Nest, Mystic Finance, and other Plume applications.

What is Plume pUSD?

Plume pUSD is a USD-pegged stablecoin issued on Plume Chain that is fully backed by USDC held in a BoringVault. It is non-yield-bearing in its base form, mints and redeems at parity with no protocol fees, and functions as the default unit of account for transactions across Plume's RWAfi applications. It is a wrapper, not a tokenized treasury.

Plume Network launched mainnet in 2025 as a full-stack Layer 1 focused on bringing bonds, private credit, treasuries, and alternative assets onchain. Plume raised $20 million from Brevan Howard Digital, Haun Ventures, Galaxy Ventures, and others ahead of mainnet, and the ecosystem has since attracted more than 180 building teams and an Apollo Global Management investment. pUSD was deployed as the settlement asset for that ecosystem.

The contract on Plume Chain is 0xdddd73f5df1f0dc31373357beac77545dc5a6f3f. Holders can hold pUSD without KYC for transfers, but minting goes through a compliance predicate that checks the originating wallet against OFAC and other screening lists before issuing tokens.

How does pUSD work mechanically?

pUSD mints and redeems through a single primary contract that wraps USDC at a fixed 1:1 ratio. A user bridges USDC onto Plume Chain, calls the minter, passes a compliance check, and receives pUSD. Redemption is the inverse path with no fees. There is no algorithmic supply control, no overcollateralization buffer, and no rebase. Stability is inherited entirely from USDC.

The minter contract is TellerWithMultiAssetSupportPredicateProxy. When a wallet calls mint, the predicate triggers an offchain API check before allowing issuance. That gate enforces sanctions screening at the issuance layer rather than at the transfer layer, which means secondary transfers of pUSD between non-sanctioned addresses behave like any standard ERC-20.

The collateral itself sits in a BoringVault, an audited vault pattern that custodies USDC and exposes deposit and withdrawal functions only to the minter contract. Plume's documentation describes the vault as the single backing source for circulating pUSD. There is no second collateral type and no yield-generating strategy applied to the reserves in the base product. Reserve composition risk for pUSD is therefore identical to USDC reserve risk, plus the operational risk of the vault contract itself.

Primary vs secondary RWA stablecoins: where pUSD sits

RWA stablecoins split into two functional categories. Primary RWA stablecoins are collateralized by tokenized real world assets (most commonly short-dated US Treasuries) and pay holders yield. Secondary RWA stablecoins are fiat-stablecoin wrappers that do not generate yield and exist to lubricate trading and settlement on RWA-focused chains. pUSD is a secondary RWA stablecoin. USDY, BUIDL, USDM, and OUSG are primary.

The reason both categories exist on the same chains comes down to securities treatment and medium-of-exchange utility. Primary RWA stablecoins like Ondo's USDY (currently $2.1 billion in supply per DeFiLlama) or BlackRock's BUIDL ($3.0 billion) are treated as securities under most jurisdictions. They carry KYC gates, transfer restrictions, and yield distributions that complicate their use as a routine settlement medium. You can settle a trade in USDY, but the counterparty needs to be a permitted holder, and the yield accrual creates accounting friction for short-term trading.

Secondary RWA stablecoins solve that. pUSD is permissionless to transfer post-mint, does not pay yield, and is not a security. That lets it serve as the neutral pricing leg that primary RWA tokens trade against on Plume's Nest vaults, Mystic Finance lending markets, and other onchain venues. The deck-narrative collapses to this: pUSD is not an RWA stablecoin in the collateral sense. It is the dollar rail that makes RWA stablecoins tradeable.

Ethena's USDtb plays a similar secondary role on other chains, sitting alongside USDe and yield products. The pattern repeats wherever an ecosystem hosts primary RWA assets: a non-yield, non-security wrapper is needed underneath to keep markets liquid.

How does pUSD compare to USDY, BUIDL, and USDM?

pUSD, USDY, BUIDL, and USDM all carry USD pegs and operate in the RWA segment, but they differ on the four dimensions that actually drive usage: what backs them, whether they pay yield, whether transfers are KYC-gated, and which chain they natively settle on. The table below summarizes the contrast. Numbers reflect DeFiLlama and CoinGecko snapshots as of Q2 2026.

Stablecoin

Backing

Yield to holder

KYC to hold

Primary chain

Redemption

pUSD

USDC (1:1, BoringVault)

No

KYC to mint, permissionless to transfer

Plume

Burn for USDC, no fee

USDY (Ondo)

Short-dated US Treasuries + bank deposits

Yes, accrues via price

Yes, non-US permitted holders

Ethereum, plus multi-chain deployments

Burn for USD via Ondo, with cutoff windows

BUIDL (BlackRock)

Cash, US Treasuries, repo

Yes, rebases daily

Yes, qualified purchasers via Securitize

Ethereum, plus multi-chain via Wormhole

Redemption through Securitize transfer agent

USDM (Mountain)

Short-dated US Treasuries

Yes, rebases daily

Yes, non-US permitted holders

Ethereum, plus L2 deployments

Burn for USD via Mountain

The functional read is straightforward. USDY, BUIDL, and USDM are securities-flagged income products. pUSD is a transactional wrapper. A user holding USDY earns roughly the SOFR-linked yield of the underlying Treasury portfolio. A user holding pUSD earns nothing in the base token and is expected to deploy it into an application like Nest to access yield. The two categories complement each other and routinely sit on the same chain.

What does pUSD do inside the Plume ecosystem?

Inside Plume, pUSD functions as the default settlement asset for tokenized real world asset transactions, lending markets, and yield vaults. Users mint pUSD by wrapping USDC, deposit it into applications like Nest or Mystic Finance, and receive yield-bearing positions backed by tokenized treasuries, private credit, or alternative assets. pUSD is the neutral leg. The yield-bearing leg is the product the user receives in return.

The clearest example is the Nest vault flow. A user bridges USDC from Ethereum to Plume Chain, mints pUSD at parity, then deposits pUSD into a Nest vault. The vault routes that pUSD into a tokenized treasury strategy and issues the depositor a position token (for example, nTBILL or nALPHA) representing exposure to the underlying RWA. That position token is the primary RWA stablecoin in the chain. pUSD was the intermediate dollar rail that made the handoff possible. To exit, the user redeems the position token back into pUSD, then burns pUSD for USDC, then bridges USDC back to Ethereum.

Beyond Nest, applications like Mystic Finance, Solera, Cultivate, and Osprey use pUSD as the quote currency in lending and trading markets. The common thread is that pUSD lets each application denominate balances and prices in dollars without inheriting the securities treatment of the yield-bearing assets the user is actually buying.

How does pUSD coexist with Plume's USD1 partnership?

pUSD and USD1 serve different roles on Plume. pUSD is the native chain-settlement asset, fully backed by USDC and deployed only on Plume. USD1 is World Liberty Financial's multichain stablecoin, currently around $4.6 billion in circulating supply per DeFiLlama, that was announced as a strategic stablecoin on Plume for cross-chain liquidity. They are complements: pUSD handles in-chain settlement, USD1 handles external liquidity routing.

The split mirrors how other RWA chains are layering stablecoins. A chain-native wrapper (pUSD) gives applications a single canonical dollar to denominate in. A multichain partner stablecoin (USD1) gives external liquidity providers a familiar asset to hold across networks. When a Plume application needs to source liquidity from Ethereum or BSC pools, USD1 can route in without first being converted to USDC and re-minted as pUSD. WLFI's USD1 documentation describes the asset as a fully reserved fiat-backed stablecoin available on multiple chains.

For an end user, the practical distinction is usually invisible. Wallets and aggregators on Plume route between pUSD and USD1 automatically based on which application is being used. For an integrator, the rule is simpler: settle inside Plume in pUSD, bridge in or out using USD1 or USDC depending on which network the counterparty is on.

What are the risks of holding or using pUSD?

pUSD's risk profile is dominated by USDC dependency, smart contract risk in the BoringVault and minter, and concentration of liquidity on a single chain. It does not carry the duration, credit, or redemption-cutoff risks that primary RWA stablecoins carry, but it does inherit Circle's reserve risk and any operational risk specific to the Plume issuance contracts.

The collateral chain is the most direct exposure. Every pUSD is backed by one USDC. If USDC depegs, loses redemption, or faces a reserve issue, pUSD inherits that exposure one-for-one with no buffer. Circle's monthly reserve attestations are the relevant primary source for USDC backing composition. There is no second collateral type and no overcollateralization to absorb a USDC shock.

Smart contract risk sits at the BoringVault, the minter predicate, and the offchain compliance API that gates issuance. Multiple audits have been completed on the BoringVault pattern, but audits reduce rather than eliminate this risk. If the predicate API is unavailable, minting pauses, though existing pUSD continues to trade normally.

Liquidity concentration is the third factor. pUSD circulating supply is in the tens of millions of tokens, orders of magnitude smaller than USDC ($75.6 billion per DeFiLlama as of Q2 2026) or USDT ($187.2 billion). Most of that liquidity sits in Plume DEXs and lending markets. Large redemptions outside the official mint/burn path can move price meaningfully on secondary venues, even though the official redemption is always available at par.

How do you mint, use, and redeem pUSD?

Minting pUSD requires bridging USDC to Plume Chain, connecting a Web3 wallet, and calling the official minter through Plume's interface. The wallet passes a compliance check, and pUSD is issued at 1:1 with no protocol fee. From there, the token can be deposited into Nest, Mystic Finance, or any other Plume application. Redemption is the reverse path and is also fee-free.

The standard end-to-end flow looks like this:

  1. Acquire USDC on Ethereum, Base, or another network where USDC is native.

  2. Bridge USDC to Plume Chain using a supported bridge route.

  3. Connect a wallet to the Plume mint interface and call mint. The compliance predicate runs an OFAC and sanctions check on the wallet.

  4. Receive pUSD at 1:1. Use it inside Nest, Mystic Finance, Cultivate, or other Plume applications, or hold it as a passive dollar position.

  5. To exit, burn pUSD for USDC through the same interface, then bridge USDC back to the destination network.

Adding pUSD to a wallet requires importing the contract address 0xdddd73f5df1f0dc31373357beac77545dc5a6f3f. Most Plume-aware wallets and explorers offer one-click import. Network gas on Plume is paid in the chain's native gas token, not in pUSD.

For users moving stablecoin liquidity across multiple chains rather than into a single ecosystem, intent-based bridging infrastructure is the relevant primitive. Eco Routes provides intent-based stablecoin transfers across major networks. That sits one layer below pUSD: Eco Routes moves the underlying USDC, and pUSD is then minted on the destination chain through Plume's contracts.

Frequently asked questions about pUSD

The questions below cover the points users most often ask when first encountering pUSD: how it differs from USDC, whether it earns yield, whether it works outside Plume, what its security model looks like, and what it costs to use. Each answer is short and self-contained.

What makes pUSD different from USDC?

pUSD is a Plume-native wrapper around USDC. The backing is identical (one USDC per pUSD held in a BoringVault), but pUSD adds an onchain compliance check at mint time and is denominated as the native dollar inside Plume applications. USDC itself can also be bridged to Plume, but pUSD is the asset most Plume applications quote and settle in.

Does pUSD pay yield?

No. Base pUSD is non-yield-bearing. Holders earn nothing on idle balances. To earn yield on Plume, a user deposits pUSD into an application like Nest and receives a yield-bearing position token (such as nTBILL) backed by tokenized treasuries. That position token is the primary RWA stablecoin in the chain. pUSD is the dollar rail that makes the deposit possible.

Can pUSD be used outside Plume?

pUSD is deployed on Plume Chain and is not natively multichain. Cross-chain liquidity into and out of Plume is generally handled through USDC bridging or through WLFI's USD1, which is multichain. A user wanting dollar liquidity on Ethereum, Base, or another network typically redeems pUSD for USDC on Plume, then bridges USDC out.

How is pUSD secured?

Security rests on three layers: the BoringVault custody contract holding the USDC backing, the minter and compliance predicate that gate issuance, and Circle's underlying USDC reserves. The BoringVault pattern has been audited multiple times. Holders should treat pUSD's risk as Circle reserve risk plus Plume contract risk, with no overcollateralization buffer between them.

Are there fees to mint or redeem pUSD?

Plume charges no protocol fee for minting or redeeming pUSD. Users pay only the network gas required to execute the mint or burn transaction on Plume Chain. The fee-free design is intentional: pUSD is meant to be the frictionless dollar rail underneath Plume's RWAfi applications, not a revenue product in its own right.

Related reading

Stablecoin supplies and market caps in this article are sourced from DeFiLlama and CoinGecko snapshots as of Q2 2026. Plume protocol mechanics are sourced from Plume's official documentation. Figures and contract details may change as Plume updates pUSD or expands deployments.

Did this answer your question?