Events - Dionysus

Everything the app shows you in a statement is a rendering of contract events. This page groups them by meaning; exact signatures are in the verified source on the explorer.

Capital

Event family	Emitted when
Deposit / injection events	Capital enters the vault (standard or non-base token) and is booked into contributed capital
Withdrawal events	Value leaves through any exit mode — full, partial, in-kind, rewards, loose balances

Strategy activity (operator)

Event family	Emitted when
Mint / plant	New positions are opened
Rebalance	A range is re-centred
Reward claims and sales	Emissions and fees are harvested and converted
Dust absorption / compound	Loose balances are folded back into positions
Rotation	Liquidity moves between venues

Fees

Event family	Emitted when
Fee charged	The gate charges on new profit at an outbound transfer
Fee waived	A stale feed made honest pricing impossible — fee zeroed, reason recorded
Fee accrued / pushed	The treasury leg failed and was deferred; a retry later succeeds
Fee funded	An owner tops up loose balances to cover an in-kind exit’s fee

Safety and administration

Event family	Emitted when
Operator granted / revoked	The agent is hired or fired
Pause / unpause	The guardian stops or resumes automation
Feed proposed / accepted / rejected	A price feed changes by the two-step process
State repair events	An explicit, logged administrative correction — repairs are never silent

For indexers

The event surface is designed to be a complete record: vault value history, fee accounting, and agent activity are all reconstructable from events alone, without contract-state polling. If you’re building on top of Dionysus vault data, the Manager API serves the indexed form of exactly these events.