Enable Whitelisted Reserves

Documentation Index

Fetch the complete documentation index at: https://kamino.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​

What you’re enabling

​

Setup

import { createSolanaRpc, address } from '@solana/kit';
import { KaminoManager, KaminoVault } from '@kamino-finance/klend-sdk';

const rpc = createSolanaRpc('https://api.mainnet-beta.solana.com');
const vault = new KaminoVault(rpc, address('<VAULT_ADDRESS>'));
const kaminoManager = new KaminoManager(rpc);

// Enable allocation whitelisting
const allocIx = await kaminoManager.updateVaultAllowAllocationsInWhitelistedReservesOnlyIxs(
  vault,
  true,
);

// Enable investment whitelisting
const investIx = await kaminoManager.updateVaultAllowInvestInWhitelistedReservesOnlyIxs(
  vault,
  true,
);

// Build and send each as a separate transaction with the standard @solana/kit pipe.
// Multisig vaults: route through Squads.

​

What stays unchanged

• Withdrawals are always permitted. You can de-allocate from any reserve at any time, and depositors can enter or exit the vault at any time subject to available liquidity.
• The whitelist itself is managed by Kamino at the protocol level. Curators activate enforcement on their vault but cannot add or remove reserves from the whitelist.
• Existing allocations to non-whitelisted reserves are not removed by enabling the flags. They remain in your allocation list but new investment is blocked. Plan to remove them via Configure allocations before enabling if you want a clean state.

​

Best practices

• Enable both flags. One alone leaves a gap. Both together is the supported configuration.
• Enable during vault setup. Before depositors enter — strongest signal and a prerequisite for UI listing.
• Pair with the Insurance Pool. Whitelisted Reserves protects against where capital goes; the Insurance Pool protects against what happens if something goes wrong. Together they represent the highest trust configuration.

​

What’s next