← Protocols
Plume
01Description

Public, EVM-compatible RWA-focused chain (chainId 98866) with built-in tokenization, compliance, and yield infrastructure (Nest, Boring Vaults). Ships pUSD — a 1:1 USDC-backed canonical stablecoin — and pETH (yield-bearing ETH LST) as the ecosystem's native settlement assets.

02Best for
  • 01RWA token issuance and primary distribution
  • 02permissioned yield products with on-chain compliance
  • 03pUSD as a settlement / quote stablecoin in RWAfi apps
  • 04deploying EVM-style protocols on an RWA-native L1/L2
  • 05Boring Vault / Nest-based yield routing
03Install
  • pnpm add viem wagmi
04Environment variables
VariableScopeDescription
NEXT_PUBLIC_PLUME_RPC_URLClientPlume mainnet HTTP RPC URL (default https://rpc.plume.org, chainId 98866).
NEXT_PUBLIC_PLUME_PUSD_ADDRESSClientPlume USD (pUSD) ERC-20 address on Plume mainnet — the canonical USDC-backed stablecoin.
05Prompt snippet
Use Plume for an RWA-native dApp. Configure viem/wagmi with the Plume chain (`id: 98866`, RPC `https://rpc.plume.org`, native token `PLUME`, explorer `https://explorer.plume.org`). Default the app's quote currency to pUSD (a 1:1 USDC-backed ERC-20 minted via a BoringVault) and use pETH as the yield-bearing ETH proxy. Bridge canonical USDC/ETH from Ethereum into Plume via the Plume Portal bridge before exposing balances. Plume enforces protocol-level AML screening (Chainalysis-backed) on connected addresses — gate sensitive flows on the on-chain sanctions check before submitting transactions, and surface `Compliance.isAllowed(address)` failures with a clear UX. For yield, route deposits through Nest vaults or Plume's Optimizer rather than minting wrapped representations yourself.
06Gotchas
  • Plume runs an on-chain AML/sanctions screening layer — sanctioned or unscreened addresses can have transfers reverted; always handle the revert path.
  • pUSD is backed by USDC inside a BoringVault, so its peg inherits USDC's de-peg risk (e.g. the March 2023 SVB event); a Circle issue propagates to pUSD.
  • Some RWA products on Plume (tokenized treasuries, private credit) require KYC and are jurisdiction-restricted — geofence and surface accreditation gates before showing them.
  • Plume is a young chain — RPC providers, oracle coverage, and bridge liquidity are thinner than Ethereum; build with retry logic and don't assume sub-second finality on cross-chain hops.
  • pETH and other LST/RWA wrappers depend on external oracles (Chainlink, RedStone) — a stale/bad price feed can halt redemptions or trigger bad liquidations on lending markets that quote against them.
  • Bridge representations of USDC/ETH on Plume are NOT the canonical Ethereum tokens; never assume cross-chain fungibility without going through the official bridge.
07Alternatives