Skip to main content
Nest runs a family of tokenized RWA vaults, each backed by a different strategy, deployed in parallel on Ethereum and on Plume. Every vault shares the same mechanics: entry and exit both route through Nest’s own actions API, which checks wallet compliance before building a transaction, and exit settles standard (request plus cooldown plus claim), instant (subject to available liquidity), or auto-claimed (a one-time operator authorization that removes the manual claim step).
Nest also lists a Perena vault on both networks. It carries deprecated: true in the yield’s metadata: existing holders can still exit, but it no longer accepts new deposits and is not covered on this page.

​
Availability

Every vault is KYC-gated (kycRequired: true, kycMode: external_redirect). Eligibility is a blocked-country list rather than an allow-list (defaultPolicy: allow, usPersonAllowed: false), IP-enforced; on top of that, every wallet is screened on-chain by Plume’s AML and Predicate policy on every action, so a non-compliant wallet cannot get a transaction built at all. See RWA KYC for the generic verification flow. On Ethereum, every vault accepts USDC except BlackOpal LiquidStone II and the BlackRock iShares AAA CLO Active ETF vault, which also accept USDT. On Plume, every vault accepts USDC or pUSD, and AXI additionally accepts XUPL. List the Nest yields enabled for your project with GET /v1/yields filtered by providers=nest. A vault with only one input asset keys its yield ID to that asset, for example ethereum-usdc-nest-ntbill-vault; a vault with more than one input asset (BlackOpal LiquidStone II and BlackRock iShares AAA CLO Active ETF on Ethereum, every vault on Plume) keys its id to the network and share token instead, for example plume-nest-ntbill-vault.

​
Entering

The enter argument is amount, in the input token. Vaults with more than one accepted input asset also require inputToken to select which one; single-asset vaults omit it. The yield’s status.enter is false only for the deprecated Perena vault; every live vault keeps entry open.

​
Exiting

The exit argument is amount, in the position token; vaults with more than one input asset also require outputToken to select the redemption asset.
Standard exit is a request, not an instant payout. It queues a redemption that settles after the vault’s cooldown, then exposes a CLAIM_UNSTAKED pending action; running it is the transaction that returns the output token to your wallet.
Two optional exit arguments change this: useInstantExecution (boolean) redeems immediately against the vault’s available on-chain liquidity when Nest reports enough for your output asset, skipping the cooldown and claim entirely. useAutoClaim (boolean) opts into a one-time operator authorization on the first request that uses it, so that vault’s future redemptions no longer need a manual CLAIM_UNSTAKED step. status.exit is always true, including for the deprecated Perena vault, so existing holders can redeem out.

​
Rewards and position

Yield accrues in the position token’s price per share; reward claiming is automatic. Which fee types you can configure on this yield is listed in mechanics.possibleFeeTakingMechanisms; see Monetization. The public balance types you see across the exit lifecycle are active (held shares), exiting (redemption request pending settlement), and withdrawable (settled, awaiting CLAIM_UNSTAKED).

​
Next steps

RWA KYC

Discover KYC requirements and route users through issuer onboarding.

Action lifecycle

Request, sign, and submit enter and exit actions, and run pending actions like CLAIM_UNSTAKED.