Use this file to discover all available pages before exploring further.
This guide is the operational walkthrough for managing vault allocations. For the conceptual model — Standard vs. Conditional, weights, caps, priority — read Concepts → Allocations first. This page assumes you’ve already chosen the parameters you want.For fixed-rate-specific allocation patterns and a focused step-by-step, see Configure fixed-rate allocations.
Navigate to your vault on manage.kamino.com and open the Allocations tab.
2
Click Add Reserve
Opens the allocation configuration form.
3
Select market and reserve
The reserve picker shows market name and TVL, reserve type (floating or fixed-rate), supply APY, reserve TVL, and utilization. A market may contain multiple reserves for the same token (e.g. USDC floating, USDC 5% 3M, USDC 6% 6M).
4
Set parameters
Parameter
Notes
Allocation Weight
Relative integer; ignored for Conditional allocations
Allocation Cap
Hard ceiling in tokens; binding limit for Conditional
Conditional Allocation toggle
Off = Standard (immediate deployment); On = Conditional (deploy on demand)
Allocation Priority
Default 0; raise to protect this Standard allocation from being a source for Conditional fills
5
Submit
Sign with your admin wallet, or generate a Squads proposal if the vault is multisig-controlled.
To change weights across multiple reserves in a single transaction, use the batch-edit view. The UI shows real-time percentage recalculation and projected vault APY impact, including unallocated funds.
Either set the weight (Standard) or cap (Conditional) to 0, or remove the entry entirely. The removed reserve’s share is redistributed to the remaining allocations per their weights.
import { createSolanaRpc, createSolanaRpcSubscriptions, address, pipe, createTransactionMessage, setTransactionMessageFeePayerSigner, setTransactionMessageLifetimeUsingBlockhash, appendTransactionMessageInstructions, signTransactionMessageWithSigners, sendAndConfirmTransactionFactory,} from '@solana/kit';import { KaminoManager, KaminoVault, Reserve, ReserveAllocationConfig, ReserveType, getMedianSlotDurationInMsFromLastEpochs,} from '@kamino-finance/klend-sdk';import { parseKeypairFile } from '@kamino-finance/klend-sdk/dist/utils/signer.js';import { Decimal } from 'decimal.js';const adminSigner = await parseKeypairFile('/path/to/your/keypair.json');const rpc = createSolanaRpc('https://api.mainnet-beta.solana.com');const rpcSubscriptions = createSolanaRpcSubscriptions('wss://api.mainnet-beta.solana.com');const slotDuration = await getMedianSlotDurationInMsFromLastEpochs();const kaminoManager = new KaminoManager(rpc, slotDuration);const vault = new KaminoVault(rpc, address('<VAULT_ADDRESS>'));const reserveAddress = address('<RESERVE_ADDRESS>');const reserveState = await Reserve.fetch(rpc, reserveAddress);const reserveWithAddress = { address: reserveAddress, state: reserveState! };// Standard allocationconst standardConfig = new ReserveAllocationConfig( reserveWithAddress, 100000, // weight new Decimal('18446744073709551615'), // u64 max = no cap new ReserveType.Standard(), 0, // priority);// OR — Conditional allocation (typically for fixed-rate reserves)const conditionalConfig = new ReserveAllocationConfig( reserveWithAddress, 0, // weight ignored for Conditional new Decimal('10000000'), // 10M token cap new ReserveType.Conditional(), 0, // priority);const { updateReserveAllocationIx } = await kaminoManager.updateVaultReserveAllocationIxs(vault, standardConfig, adminSigner);const { value: blockhash } = await rpc.getLatestBlockhash({ commitment: 'finalized' }).send();const signed = await signTransactionMessageWithSigners( pipe( createTransactionMessage({ version: 0 }), tx => setTransactionMessageFeePayerSigner(adminSigner, tx), tx => setTransactionMessageLifetimeUsingBlockhash(blockhash, tx), tx => appendTransactionMessageInstructions([updateReserveAllocationIx], tx), ),);await sendAndConfirmTransactionFactory({ rpc, rpcSubscriptions })(signed, { commitment: 'confirmed', skipPreflight: true,});
The same updateVaultReserveAllocationIxs method handles both adding a new reserve and updating an existing one — the SDK detects whether the allocation already exists.
const removeIx = await kaminoManager.removeReserveFromAllocationIx( vault, address('<RESERVE_ADDRESS>'), adminSigner,);// Build and send using the same pattern as above
If the underlying reserve has insufficient liquidity to deallocate fully, the deallocation queues through the withdrawal queue.
For multisig-controlled vaults, append --mode multisig --multisig <MULTISIG_PUBKEY>. The CLI emits a Base58-encoded transaction string that you import into Squads for proposal and approval.
Allocations are targets. After updating an allocation, the vault doesn’t immediately rebalance — a permissionless sync brings actual allocation toward target. The sync bot runs every ~15 minutes; you can also trigger it manually via the UI’s “Sync Allocations” action or the SDK’s investAllReservesIxs / investSingleReserveIxs methods.Sync may not reach the exact target if a source reserve has insufficient available liquidity to deallocate from. In that case, the deallocation routes through the withdrawal queue.
