FLYING_TULIP_HARDCODED_PROTOCOLS

Documentation for eth_defi.erc_4626.classification.FLYING_TULIP_HARDCODED_PROTOCOLS data.

FLYING_TULIP_HARDCODED_PROTOCOLS = {'0xd1e5a86f1005f6356bd022c587de0f430cd2aeb1': {<ERC4626Feature.flying_tulip_like: 'flying_tulip_like'>, <ERC4626Feature.share_price_equivalence: 'share_price_equivalence'>}, '0xe1716796d6bf37e4049bdb6e1150cb713800feee': {<ERC4626Feature.flying_tulip_like: 'flying_tulip_like'>, <ERC4626Feature.share_price_equivalence: 'share_price_equivalence'>}, '0xeb48218a4c35c814c7678cbcae88c6ee037f7625': {<ERC4626Feature.flying_tulip_like: 'flying_tulip_like'>, <ERC4626Feature.share_price_equivalence: 'share_price_equivalence'>}}

Flying Tulip’s reviewed sftUSD proxies are a finite, chain-aware registry. The generic ERC-4626 surface deliberately cannot identify this externally rewarded fixed-price vault family safely. Do not add ABI-selector probes: only the published address list may map a vault to Flying Tulip.