erc_4626.vault_protocol.yuzu_money.vault
Documentation for eth_defi.erc_4626.vault_protocol.yuzu_money.vault Python module.
Yuzu Money protocol vault support.
Yuzu Money is a DeFi protocol that packages high-yield strategies into an overcollateralised stablecoin (yzUSD). The protocol is deployed on the Plasma chain and offers multiple products including yzUSD, syzUSD (staked yzUSD), and yzPP (Yuzu Protection Pool).
Key features:
yzUSD: Overcollateralised stablecoin targeting $1 USD, backed 1:1 by USDC
syzUSD: Yield-bearing token received when staking yzUSD (ERC-4626 vault)
yzPP: Junior tranche / insurance liquidity pool providing first-loss capital
No performance fees - uses yield-smoothing mechanism instead
Two-step redemption process with delay period
The yzPP vault (Yuzu Protection Pool) is the insurance liquidity pool that:
Accrues yield from protocol strategies
Bears first-loss risk on underlying strategies
Uses time-delayed redemptions for risk management
Fee structure:
Yuzu Money does not charge traditional performance fees. Instead, they employ a yield-smoothing mechanism where a consistent weekly yield target is distributed, backed by a Reserve Fund that acts as a buffer. See: https://yuzu-money.gitbook.io/yuzu-money/faq-1/performance-fee
Security:
Audited by Pashov Audit Group (August 2025)
Hypernative threat monitoring
Nexus Mutual smart contract insurance
3/5 multisig with 48-hour timelock
Homepage: https://yuzu.money/
Documentation: https://yuzu-money.gitbook.io/yuzu-money/
Fee documentation: https://yuzu-money.gitbook.io/yuzu-money/faq-1/performance-fee
Audit report: https://github.com/pashov/audits/blob/master/team/pdf/YuzuUSD-security-review_2025-08-28.pdf
DefiLlama: https://defillama.com/protocol/yuzu-money
Twitter: https://x.com/YuzuMoneyX
Contract (yzPP): https://plasmascan.to/address/0xebfc8c2fe73c431ef2a371aea9132110aab50dca
Classes
Yuzu Money protocol vault support. |
- class YuzuMoneyVault
Bases:
eth_defi.erc_4626.vault.ERC4626VaultYuzu Money protocol vault support.
Yuzu Money yzPP (Protection Pool) vault is the junior tranche of the protocol that provides first-loss capital and earns higher yields in return.
Key characteristics:
ERC-4626 compliant vault
Time-delayed redemptions (not instant)
No performance fees (yield-smoothing mechanism)
Bears first-loss risk for protocol strategies
Fee structure:
Yuzu Money does not charge traditional performance fees. Instead, they employ a yield-smoothing mechanism. See: https://yuzu-money.gitbook.io/yuzu-money/faq-1/performance-fee
Homepage: https://yuzu.money/
Documentation: https://yuzu-money.gitbook.io/yuzu-money/
Contract (yzPP): https://plasmascan.to/address/0xebfc8c2fe73c431ef2a371aea9132110aab50dca
- Parameters
web3 – Connection we bind this instance to
spec – Chain, address tuple
token_cache –
Cache used with
fetch_erc20_details()to avoid multiple calls to the same token.Reduces the number of RPC calls when scanning multiple vaults.
features – Pass vault feature flags along, externally detected.
default_block_identifier –
Override block identifier for on-chain metadata reads.
When
None, useget_safe_cached_latest_block_number()(the default, safe for broken RPCs). Set to"latest"for freshly deployed vaults whose contracts do not exist at the safe-cached block.
- has_custom_fees()
Whether this vault has deposit/withdrawal fees.
Yuzu Money does not charge performance fees. They use a yield-smoothing mechanism instead. See: https://yuzu-money.gitbook.io/yuzu-money/faq-1/performance-fee
- Return type
- get_management_fee(block_identifier)
Get the current management fee as a percent.
Yuzu Money does not charge management fees.
- get_performance_fee(block_identifier)
Get the current performance fee as a percent.
Yuzu Money does not charge traditional performance fees. Instead, they employ a yield-smoothing mechanism where a consistent weekly yield target is distributed, backed by a Reserve Fund.
See: https://yuzu-money.gitbook.io/yuzu-money/faq-1/performance-fee
- get_estimated_lock_up()
Get estimated lock-up period if any.
Yuzu Money yzPP vault uses time-delayed redemptions. Users must initiate a redeem order and wait for the delay period before finalising the redemption.
The exact delay period is configurable by the protocol admin.
- Return type
datetime.timedelta | None
- get_link(referral=None)
Get the vault’s web UI link.
- __init__(web3, spec, token_cache=None, features=None, default_block_identifier=None)
- Parameters
web3 (web3.main.Web3) – Connection we bind this instance to
spec (eth_defi.vault.base.VaultSpec) – Chain, address tuple
token_cache (dict | None) –
Cache used with
fetch_erc20_details()to avoid multiple calls to the same token.Reduces the number of RPC calls when scanning multiple vaults.
features (set[eth_defi.erc_4626.core.ERC4626Feature] | None) – Pass vault feature flags along, externally detected.
default_block_identifier (Optional[Union[Literal['latest', 'earliest', 'pending', 'safe', 'finalized'], eth_typing.evm.BlockNumber, eth_typing.evm.Hash32, eth_typing.encoding.HexStr, hexbytes.main.HexBytes, int]]) –
Override block identifier for on-chain metadata reads.
When
None, useget_safe_cached_latest_block_number()(the default, safe for broken RPCs). Set to"latest"for freshly deployed vaults whose contracts do not exist at the safe-cached block.
- property address: eth_typing.evm.HexAddress
Get the vault smart contract address.
- property denomination_token: eth_defi.token.TokenDetails | None
Get the token which denominates the vault valuation
Used in deposits and redemptions
Used in NAV calculation
Used in profit benchmarks
Usually USDC
- Returns
Token wrapper instance.
Maybe None for broken vaults like https://arbiscan.io/address/0x9d0fbc852deccb7dcdd6cb224fa7561efda74411#code
- property deposit_manager: eth_defi.vault.deposit_redeem.VaultDepositManager
Deposit manager assocaited with this vault
- property erc_7540: bool
Is this ERC-7540 vault with asynchronous deposits.
For example
previewDeposit()function and other functions will revert
- fetch_denomination_token()
Read denomination token from onchain.
Use
denomination_token()for cached access.- Return type
eth_defi.token.TokenDetails | None
- fetch_denomination_token_address()
Get the address for the denomination token.
Triggers RCP call
- Return type
Fetch the most recent onchain NAV value.
In the case of Lagoon, this is the last value written in the contract with updateNewTotalAssets() and ` settleDeposit()`
TODO: updateNewTotalAssets() there is no way to read pending asset update on chain
- Returns
Vault NAV, denominated in
denomination_token()- Return type
- fetch_portfolio(universe, block_identifier=None, allow_fallback=True)
Read the current token balances of a vault.
SHould be supported by all implementations
- Parameters
universe (eth_defi.vault.base.TradingUniverse) –
block_identifier (Optional[Union[Literal['latest', 'earliest', 'pending', 'safe', 'finalized'], eth_typing.evm.BlockNumber, eth_typing.evm.Hash32, eth_typing.encoding.HexStr, hexbytes.main.HexBytes, int]]) –
allow_fallback (bool) –
- Return type
Get the current share price.
Read share token details onchain.
Use
share_token()for cached access.- Return type
Get share token of this vault.
Vault itself (ERC-4626)
share() accessor (ERc-7575)
- fetch_total_assets(block_identifier)
What is the total NAV of the vault.
Example:
assert vault.denomination_token.symbol == "USDC" assert vault.share_token.symbol == "ipUSDCfusion" assert vault.fetch_total_assets(block_identifier=test_block_number) == Decimal("1437072.77357") assert vault.fetch_total_supply(block_identifier=test_block_number) == Decimal("1390401.22652875")
- Parameters
block_identifier (Union[Literal['latest', 'earliest', 'pending', 'safe', 'finalized'], eth_typing.evm.BlockNumber, eth_typing.evm.Hash32, eth_typing.encoding.HexStr, hexbytes.main.HexBytes, int]) –
Block number to read.
Use web3.eth.block_number for the last block.
- Returns
The vault value in underlyinh token
- Return type
decimal.Decimal | None
- fetch_total_supply(block_identifier)
What is the current outstanding shares.
Example:
- Parameters
block_identifier (Union[Literal['latest', 'earliest', 'pending', 'safe', 'finalized'], eth_typing.evm.BlockNumber, eth_typing.evm.Hash32, eth_typing.encoding.HexStr, hexbytes.main.HexBytes, int]) –
Block number to read.
Use web3.eth.block_number for the last block.
- Returns
The vault value in underlyinh token
- Return type
- fetch_vault_info()
Get all information we can extract from the vault smart contracts.
- Return type
- property flow_manager: eth_defi.vault.base.VaultFlowManager
Flow manager associated with this vault
- get_deposit_fee(block_identifier)
Deposit fee is set to zero by default as vaults usually do not have deposit fees.
Internal: Use
get_fee_data().
- get_deposit_manager()
Get deposit manager to deposit/redeem from the vault.
- get_fee_data()
Get fee data structure for this vault.
- Raises
ValueError – In the case of broken or unimplemented fee reading methods in the smart contract
- Return type
- get_fee_mode()
Get how this vault accounts its fees.
- Return type
- get_flags()
Get various vault state flags from the smart contract.
Override to add status flags
Also add flags from our manual flag list in
eth_defi.vault.flag
- Returns
Flag set.
Do not modify in place.
- Return type
set[eth_defi.vault.flag.VaultFlag]
- get_flow_manager()
Get flow manager to read indiviaul settle events.
Only supported if
has_block_range_event_support()is True
- Return type
- get_historical_reader(stateful)
Get share price reader to fetch historical returns.
- Parameters
stateful – If True, use a stateful reading strategy.
- Returns
None if unsupported
- Return type
- get_notes()
Get a human readable message if we know somethign special is going on with this vault.
- Return type
str | None
- get_risk()
Get risk profile of this vault.
- Return type
- get_withdraw_fee(block_identifier)
Withdraw fee is set to zero by default as vaults usually do not have withdraw fees.
Internal: Use
get_fee_data().
- has_block_range_event_support()
Does this vault support block range-based event queries for deposits and redemptions.
If not we use chain balance polling-based approach
- has_deposit_distribution_to_all_positions()
Deposits go automatically to all open positions.
Deposits do not land into the vault as cash
Instead, smart contracts automatically increase all open positions
The behaviour of Velvet Capital
- property info: eth_defi.vault.base.VaultInfo
Get info dictionary related to this vault deployment.
Get cached data on the various vault parameters
- Returns
Vault protocol specific information dictionary
- is_valid()
Check if this vault is valid.
Call a known smart contract function to verify the function exists
- Return type
ERC-20 that presents vault shares.
User gets shares on deposit and burns them on redemption
- property underlying_token: eth_defi.token.TokenDetails
Alias for
denomination_token()
- property vault_contract: web3.contract.contract.Contract
Get vault deployment.