Nest

About

Nest is Plume's RWA yield platform: each vault issues an ERC-20 share token representing a managed portfolio of tokenized real-world assets — US Treasuries, private credit, CLOs, and market-neutral strategies. Eleven vaults are exposed natively through the Yield API, spanning Treasuries (nTBILL), credit (nCREDIT, nACRDX, nLCRD, nOPAL, nFALCON, nCLOA) and diversified or strategy vaults (nALPHA, nBASIS, nWISDOM, nPERENA).

The user deposits the input token and receives the vault's share token at the current NAV. There are no separate reward tokens, no claim transactions on entry, and no compounding actions — yield accrues through NAV appreciation of the share token and is auto-compounding by construction.

Considerations

Compliance: screened, not onboarded

Nest sets kycRequired: true, but there is no user-facing onboarding flow. Every wallet is screened automatically at the compliance layer (Plume AML and the Predicate policy) for sanctions, illicit-actor, and restricted-jurisdiction exposure — no deposit transaction can be built for a non-compliant wallet. US persons are not eligible, along with FATF high-risk and sanctioned jurisdictions. Geo-blocking is enforced at the compliance layer; configure your own country/region policy via Geoblocking.

KYC status is exposed through the unified KYC interface (GET /v1/yields/:id/kyc/status): a compliant wallet returns approved without ever completing a verification flow; a non-compliant wallet returns not_started and attempts to transact are rejected with HTTP 412 Precondition Failed.

Relayed transaction construction

Deposit and redemption calldata is constructed by Nest's Actions API and returned through the standard Yield API surface as ordered, unsigned transactions — the integration model is unchanged from any other yield: sign client-side, broadcast, report the hash.

Redemption paths

Exits are dual-path, selected via the useInstantExecution flag on the exit action:

Standard redemptions are asynchronous: the request enters the vault's redemption queue and matures after the vault's cooldown. While pending, the amount surfaces as unstaking on the balance. Once matured, the position becomes claimable — the API surfaces a pending CLAIM_UNSTAKED action to complete the withdrawal. Async redemptions may require a one-time operator-authorization transaction (setOperator), which the API includes in the transaction plan when auto-claim is enabled.

Instant redemptions settle atomically against available vault liquidity; when liquidity is insufficient the action is rejected before any transaction is broadcast, so callers can fall back to the standard path.

Multi-asset vaults

nOPAL and nCLOA accept both USDC and USDT. Their yield IDs are keyed by the share token (ethereum-nest-nopal-vault, ethereum-nest-ncloa-vault) and the deposit/redemption asset is selected per action.

List of Integration IDs

All vaults are on Ethereum.