Events & Indexing
Current Phase: Shadow Mainnet Testing
Multyr contracts are deployed on Arbitrum One. The system is currently in validation phase. Deposits are not open to the public. Behavior described on this page reflects the protocol's designed behavior; some mechanisms are active in shadow testing, others become active at public launch. See the Status page for details.
Multyr emits granular on-chain events for all state-changing operations.
These events are the primary data source for:
- frontends
- analytics dashboards
- monitoring systems
- off-chain indexers
Core Events
CoreVault
| Event | Description |
|---|---|
Deposit | Emitted when assets are deposited and shares minted |
Withdraw | Emitted when shares are burned and assets withdrawn |
Strategy Router
| Event | Description |
|---|---|
Harvested | Yield collected from a strategy |
Rebalanced | Capital redistributed across strategies |
StrategyActivated | Strategy enabled |
StrategyDeactivated | Strategy disabled |
Buffer Manager
| Event | Description |
|---|---|
BufferRebalanced | Liquidity moved between layers |
BufferTargetUpdated | Buffer configuration changed |
Fee System
| Event | Description |
|---|---|
FeesCollected | Fees accrued and distributed |
FeeRateUpdated | Fee parameters updated |
Governance / System
| Event | Description |
|---|---|
Sealed | System parameter permanently locked |
Paused / Unpaused | System state changes |
Subgraph
Multyr provides a subgraph indexing layer built on The Graph.
This enables:
- historical data queries
- user position tracking
- strategy performance analysis
- fee and yield reconstruction
Indexed Entities
Typical entities include:
-
Vault
- totalAssets
- totalSupply
- sharePrice
-
User
- share balance
- deposits / withdrawals
-
Strategy
- deployed capital
- cumulative yield
- status
-
Fee Events
-
Harvest Events
Example Queries
Vault State
{
vault(id: "0x...") {
totalAssets
totalSupply
sharePrice
}
}
User Position
{
user(id: "0xUser") {
sharesBalance
deposits {
assets
timestamp
}
}
}
Strategy Data
{
strategies(where: { active: true }) {
deployedAssets
cumulativeYield
}
}
Direct Event Access
Developers can query logs directly via RPC:
cast logs \
--address <CORE_VAULT> \
"Deposit(address,address,uint256,uint256)"
Design Principles
- events are the single source of truth for historical state
- indexing is optional but recommended
- subgraph improves performance but is not required
Summary
Multyr provides:
- full event coverage
- subgraph-based indexing
- direct log access
Designed for:
→ analytics → integrations → monitoring systems