erc_4626.vault_protocol.flying_tulip.constants
Documentation for eth_defi.erc_4626.vault_protocol.flying_tulip.constants Python module.
Reviewed Flying Tulip sftUSD deployment metadata.
The official registry is a maintenance cross-check, not a runtime dependency: https://api.flyingtulip.com/ftusd/contracts/all
Module Attributes
ftUSD uses CREATE2 and therefore has the same address on reviewed chains. |
|
FT token on the Ethereum chain which supplies the canonical FT/ftUSD price. |
|
Curve FT/ftUSD market on Ethereum. |
|
Ethereum deployment block of the canonical FT/ftUSD Curve market. |
|
Naive UTC Unix timestamp of |
|
Maximum accepted age of the canonical Curve EMA observation. |
|
Initial price equivalence at the first post-Curve settlement. |
|
Epoch reward formula denominator. |
|
Official sftUSD proxies keyed by EVM chain ID. |
|
FT reward-token addresses for the reviewed sftUSD proxy registry. |
|
Reviewed deployment with no epoch or supply events at the research snapshot. |
|
Proxy deployment blocks and naive UTC timestamps, determined by archive |
|
Human-readable scanner description. |
|
USDC |
|
Protocol-owned note surfaced in vault metadata. |
- FLYING_TULIP_FTUSD: eth_typing.evm.HexAddress = '0xF7D85EC4E7710f71992752eac2111312e73E9C9C'
ftUSD uses CREATE2 and therefore has the same address on reviewed chains.
- FLYING_TULIP_FT_ETHEREUM: eth_typing.evm.HexAddress = '0x5DD1A7A369e8273371d2DBf9d83356057088082c'
FT token on the Ethereum chain which supplies the canonical FT/ftUSD price.
- FLYING_TULIP_FT_FTUSD_CURVE_POOL: eth_typing.evm.HexAddress = '0x68102ff5406475881462880a8dA3C9Bc9181aD6c'
Curve FT/ftUSD market on Ethereum.
coins(0)is FT andcoins(1)is ftUSD.price_oracle()returns FT per ftUSD, scaled by 1e18; the reward reader records its reciprocal.
- FLYING_TULIP_CURVE_CANONICAL_START_BLOCK = 25531725
Ethereum deployment block of the canonical FT/ftUSD Curve market.
Determined by an archive
eth_getCodebinary search on 2026-08-24.
- FLYING_TULIP_CURVE_CANONICAL_START_TIMESTAMP = 1784042255
Naive UTC Unix timestamp of
FLYING_TULIP_CURVE_CANONICAL_START_BLOCK.Cross-chain reward tracking excludes settlements before this timestamp.
- FLYING_TULIP_MAX_ORACLE_AGE_SECONDS = 604800
Maximum accepted age of the canonical Curve EMA observation.
The first complete real backfill observed a maximum 4.7-day no-update interval, so seven days accommodates the market’s actual trading cadence while still preventing an indefinitely old price from bridging a gap.
- FLYING_TULIP_INITIAL_SHARE_PRICE_EQUIVALENCE = 1
Initial price equivalence at the first post-Curve settlement.
- FLYING_TULIP_RATE_RAY = 1000000000000000000000000000
Epoch reward formula denominator.
- FLYING_TULIP_SFTUSD_BY_CHAIN: dict[int, eth_typing.evm.HexAddress] = {1: '0xeb48218a4c35C814C7678cBcae88C6Ee037F7625', 56: '0xe1716796d6Bf37e4049bdb6e1150Cb713800FeEe', 146: '0xD1E5A86f1005F6356Bd022C587dE0f430CD2aeb1'}
Official sftUSD proxies keyed by EVM chain ID.
- FLYING_TULIP_FT_BY_CHAIN: dict[int, eth_typing.evm.HexAddress] = {1: '0x5DD1A7A369e8273371d2DBf9d83356057088082c', 56: '0x5DD1A7A369e8273371d2DBf9d83356057088082c', 146: '0x5DD1A7A369e8273371d2DBf9d83356057088082c'}
FT reward-token addresses for the reviewed sftUSD proxy registry.
Flying Tulip currently uses the same CREATE2 FT address on every reviewed chain. This address map, together with
FLYING_TULIP_SFTUSD_BY_CHAIN, is the sole authority for routing Flying Tulip vault equivalents: do not add ABI-selector probing to discover or classify further deployments.
- FLYING_TULIP_DORMANT_CHAIN_IDS = frozenset({56})
Reviewed deployment with no epoch or supply events at the research snapshot. Its empty source history is valid and must not fail the structural examiner.
- FLYING_TULIP_HARDCODED_LEADS = ((1, '0xeb48218a4c35C814C7678cBcae88C6Ee037F7625', 24501008, datetime.datetime(2026, 2, 20, 22, 19, 11)), (56, '0xe1716796d6Bf37e4049bdb6e1150Cb713800FeEe', 108860159, datetime.datetime(2026, 7, 8, 21, 31, 12)), (146, '0xD1E5A86f1005F6356Bd022C587dE0f430CD2aeb1', 64888390, datetime.datetime(2026, 3, 10, 17, 7, 25)))
Proxy deployment blocks and naive UTC timestamps, determined by archive
eth_getCodebinary search on 2026-08-24. The dormant BNB deployment is included so lead discovery materialises it before it emits an ERC-4626 deposit event.
- FLYING_TULIP_SHORT_DESCRIPTION = 'ftUSD staking vault with externally distributed FT rewards and conditional queued redemptions. See the [Flying Tulip strategy documentation](https://docs.flyingtulip.com/product-suite/ft-usd/) for its yield sources and strategy design.'
Human-readable scanner description.
- FLYING_TULIP_USDC_MINT_REDEEM_FEE_BY_CHAIN: dict[int, float] = {1: 0.0007, 56: 0.001, 146: 0.0007}
USDC
MintAndRedeemfees used to model Flying Tulip vault equivalents.The fee is configured per collateral in the MintAndRedeem engine. At the reviewed USDC configurations, Ethereum and Sonic charge seven basis points while BNB Chain charges ten basis points, in both directions. The sftUSD wrapping step has no separate fee in this model.
- FLYING_TULIP_NOTES = 'Performance assumes entry and exit fees USDC -> ftUSD -> sftUSD.\n\nPerformance includes FT rewards valued through the [Ethereum FT/ftUSD Curve pool](https://etherscan.io/address/0x68102ff5406475881462880a8da3c9bc9181ad6c#code). At each reward settlement, distributed FT is converted to ftUSD using the latest available Curve oracle price, divided by the average amount staked during the period, and compounded into the displayed returns. See the [Flying Tulip integration documentation](https://web3-ethereum-defi.readthedocs.io/vaults/flying_tulip/index.html) for details.\n\nWithdrawals may be subject to a variable exit delay or cooldown; see the [Flying Tulip ftUSD documentation](https://docs.flyingtulip.com/product-suite/ft-usd/).\n\nSee the [official deployment registry](https://api.flyingtulip.com/ftusd/contracts/all) for contract addresses.'
Protocol-owned note surfaced in vault metadata.