Skip to main content
The vault program emits Anchor events in program logs. Indexers can use these events to track user liquidity, strategy movements, rewards, performance fees, losses, and simulated unlocked amount reads.

Event Delivery

Unlike newer event-CPI programs, Dynamic Vault events are emitted as Anchor logs rather than through a separate event authority account.

Liquidity Events

RemoveLiquidity.lp_unmint_amount is the amount of LP burned. In a direct strategy withdrawal, the handler may refine the burn amount when the strategy cannot return the full desired amount.

Strategy Events

For remove_strategy, estimated_token_amount is the actual increase in the vault token account after withdrawing all strategy collateral. For normal strategy withdrawal, it is the requested underlying amount.

Reward And Fee Events

The performance fee is calculated only when a rebalance reports gain. The program mints LP tokens to the configured fee_vault and adjusts locked profit so the fee accounting does not immediately change virtual price.

Read Events

The Rust client uses get_unlocked_amount by simulating the instruction and parsing TotalAmount from logs. Off-chain clients can also compute withdrawable amount locally from vault state and sysvar clock data.

Indexing Notes

Events do not include the vault address in their payloads. Indexers should join the event to the transaction instruction accounts, especially the vault, strategy, and token accounts, when building vault-level analytics.

Payload Reference