> ## 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.

# Enable Whitelisted Reserves

> Restrict your vault to allocate only into Kamino-verified reserves at the smart contract level

Whitelisted Reserves is the smart-contract-level protection that constrains where your vault can deploy capital. Once enabled, even a compromised admin key cannot direct vault funds into unvetted markets — the constraint is enforced by the program itself, not by your operational security.

For the conceptual treatment of why this exists and what each flag controls, read [Risk primitives → Whitelisted Reserves](/curators/vaults/concepts/risk-primitives#whitelisted-reserves) first.

This page is the operational walkthrough.

<Warning>
  **Enabling Whitelisted Reserves is one-way.** Both flags can only be set to `true`. Once enabled, they cannot be reverted — enforced at the smart contract level. Be deliberate.
</Warning>

## What you're enabling

Two on-chain flags — `AllowAllocationsInWhitelistedReservesOnly` (controls new allocations) and `AllowInvestInWhitelistedReservesOnly` (controls new investment) — explained in [Concepts → Risk primitives → The two flags](/curators/vaults/concepts/risk-primitives#the-two-flags). Enable both: one alone leaves a gap that the second closes. Both together is what's required for Kamino UI listing.

## Setup

<Tabs>
  <Tab title="UI">
    <Steps>
      <Step title="Open vault settings">
        Navigate to your vault on `manage.kamino.com` and open the **Settings** tab.
      </Step>

      <Step title="Enable AllowAllocationsInWhitelistedReservesOnly">
        Toggle on. Confirm the transaction. Reminder: this is irreversible.
      </Step>

      <Step title="Enable AllowInvestInWhitelistedReservesOnly">
        Toggle on. Confirm the transaction. Also irreversible.
      </Step>
    </Steps>
  </Tab>

  <Tab title="SDK">
    ```typescript theme={null}
    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.
    ```
  </Tab>

  <Tab title="CLI">
    <Info>
      Whitelisted Reserves enablement is not currently exposed via the CLI as a dedicated command. Use the UI or SDK.
    </Info>
  </Tab>
</Tabs>

## 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](/curators/vaults/guides/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](/curators/vaults/guides/set-up-insurance-pool) protects against what happens if something goes wrong. Together they represent the highest trust configuration.

## What's next

<CardGroup cols={2}>
  <Card title="Risk primitives" icon="shield" href="/curators/vaults/concepts/risk-primitives">
    The model behind both protections.
  </Card>

  <Card title="Set up the Insurance Pool" icon="shield-halved" href="/curators/vaults/guides/set-up-insurance-pool">
    Lock the loss backstop alongside Whitelisted Reserves.
  </Card>
</CardGroup>