Changelog

v2.0.23 (18.10.2024)

🔄 Changes:

EnrichedWNFT and EnrichedDNFT:

• more info about DHW added

🆕 Additions:

views.vaultInfo.getVaultActivityForUsers():

• returns user deposit, withdraw and fastWithdraw info as record

views.vaultInfo.getVaultDailyYieldInSvts():

• returns daily yield in SVTs for a vault

views.metaVault.getMetaVaultUserClaimableFlushes():

• returns claimable flush indexes for a metavault user and their shares

views.getSubgraphSyncBlock():

• gets the block up to which the Subgraph is synced

v2.0.15 (4.10.2024)

🔄 Changes:

views.userInfo.getUsersDNFTsForVaults():

• added optional `fromBlock` parameter

views.userInfo.getUsersWNFTsForVaults():

• added optional `fromBlock` parameter

v2.0.14 (2.10.2024)

🔄 Changes:

views.metaVault.getUserMetaVaults():

• added userData.pendingDepositsAssetAmount and userData.pendingWithdrawalsAssetAmount fields to the reposnse object

v2.0.9 (6.9.2024) - Metavaults

🐛 Bug Fixes:

docs:

• fix addresses in the contractAddresses object in the setup example for Tenderly

🆕 Additions:

views.metaVault.getMetaVaultSmartVaults():

• fetches the addresses of all smart vaults that are part of the specified meta vault

views.metaVault.getMetaVaultSmartVaultAllocation():

• fetches the allocation of a specific smart vault within a meta vault

views.metaVault.getCreateMetaVaultVaults():

• fetches all smart vaults that are eligible to be included in a new meta vault

views.metaVault.getMetaVaults():

• fetches all the meta vaults that have been created

views.metaVault.getMetaVaultsUsers():

• fetches the users of a one or more specified meta vaults

views.metaVault.getIsMetaVaultDeployer():

• checks if the specified address is eligible to deploy meta vaults

mutations.metaVault.createMetaVault():

• creates a new meta vault with the specified parameters

mutations.metaVault.setMetaVaultAllocations():

• sets new allocations of the existing smart vaults within a meta vault

mutations.metaVault.setMetaVaultMaxReallocationSlippage():

• sets the maximum reallocation slippage for the meta vault

mutations.metaVault.manageMetaVaultSmartVaults():

• sets new smart vaults and their allocations for the meta vault

mutations.metaVault.metaVaultDeposit():

• deposits assets into the meta vault

mutations.metaVault.metaVaultSwapAndDeposit():

• swaps and deposits assets into the meta vault

mutations.metaVault.metaVaultClaimMVTs():

• claims the MVTs from the meta vault

mutations.metaVault.metaVaultMulticall():

• executes multiple meta vault transactions in a single call

mutations.metaVault.metaVaultRedeem():

• redeems assets from the meta vault

mutations.metaVault.metaVaultWithdraw():

• claims the redeemed assets from the meta vault

🔄 Changes:

contractAddresses:

• contractAddresses now optionally accepts a new key ISpoolAccessControl for the Spool Access Control contract address

views.vaultInfo.getVaultAPY():

• the property rewardsApy in the return objects is now of type RewardsApy: {totalRewardsApy: number, tokenRewardApys: {tokenAddresses: string[], tokenApys: string[]}})

🚫 Breaking changes:

contractAddresses:

• contractAddresses now requires a new key IMetaVaultFactory for the Metavault factory contract address

---

v1.0.27 (9.8.2024)

🐛 Bug Fixes:

mutations.rewards.recalculateOffchainRewards():

• fix invalid signature error when calling as owner

---

v1.0.26 (8.8.2024)

🔄 Changes:

views.userInfo.getUserVaults():

• added owner address to the return object

---

v1.0.25 (5.8.2024)

🐛 Bug Fixes:

views.userInfo.getMaxRedeemBag():

• does not included unprocessed deposits

• throws error if no dNFTs found for provided user and vault combination

🆕 Additions:

views.vaultInfo.getVaultOwner():

• retrieves the owner address of a specified vault.

🔄 Changes:

views.userInfo.getUserBalanceBreakdown():

• added claimableWNFTs

• withdrawnAssets now of type Record<string, number>;

🚫 Breaking changes:

none