[patcito]

Please review the following token assets:

📑 Description

• Token Name: Flying Tulip (FT) and Flying Tulip USD (ftUSD), plus the two Curve factory pools and yVaults built on them
• Project Website: https://flyingtulip.com (token addresses listed in https://flyingtulip.com/address-book/flying-tulip-address-book-prod.csv)
• Explorer URI: https://etherscan.io/token/0x5dd1a7a369e8273371d2dbf9d83356057088082c and https://etherscan.io/token/0xf7d85ec4e7710f71992752eac2111312e73e9c9c

I created two Curve factory yVaults on mainnet and they have no logos yet. This adds the FT and ftUSD logos we use in our own app, and composite logos for the pools and vaults in the same layout as the pmUSD factory logos from #52 (main token, Curve badge top right, paired token bottom right).

FT and ftUSD have the same address on Ethereum, Sonic and BNB, so I added them on 1, 146 and 56.

Chain 1:

• tokens/1/0x5dd1a7a369e8273371d2dbf9d83356057088082c/ FT
• tokens/1/0xf7d85ec4e7710f71992752eac2111312e73e9c9c/ ftUSD
• tokens/1/0x68102ff5406475881462880a8da3c9bc9181ad6c/ Curve FT/ftUSD pool (LP)
• tokens/1/0x63658f6bc7f6bec9868584cebcb0e0dec449c33a/ Curve FT/ftUSD Factory yVault
• tokens/1/0xafec61e7a604f8f81f7cab64ec75bfa07c542630/ Curve ftUSD/USDC pool (LP)
• tokens/1/0x2434ccb738f4260a71c41eea641a77936ac1bbe0/ Curve ftUSD-USDC Factory yVault

Chains 146 and 56:

• tokens/146/0x5dd1a7a369e8273371d2dbf9d83356057088082c/ and tokens/56/0x5dd1a7a369e8273371d2dbf9d83356057088082c/ FT
• tokens/146/0xf7d85ec4e7710f71992752eac2111312e73e9c9c/ and tokens/56/0xf7d85ec4e7710f71992752eac2111312e73e9c9c/ ftUSD

Sample: https://cdn.jsdelivr.net/gh/yearn/tokenassets@main/tokens/1/0x68102ff5406475881462880a8da3c9bc9181ad6c/logo-128.png

The vaults are listed in yearn/cms#172 and yearn/ydaemon#570.

---

✅ Checks

• I created a new folder with the token address (all in lowercase for EVM chains, case sensitive for Solana)
• I added the token's logo as a 32x32 PNG file, named logo-32.png
• I added the token's logo as a 128x128 PNG file, named logo-128.png
• I added the token's logo as a SVG file, named logo.svg
• My SVG logo is a proper SVG and does not contain base64 encoded elements
• My documentation/website clearly display the token address