Flying Tulip

ft
Rank #412•Decentralized Finance (DeFi), Lending and Borrowing, Stablecoin Protocol
CoinYQ Dossier

The refund travels with an NFT, not with FT

Flying Tulip’s most memorable promise is a perpetual exit at par. The promise is real only inside a primary-sale ftPUT position that still holds both FT and backing. Once FT is withdrawn or bought in the market, the floor disappears; the same ticker crosses the wallet boundary with fewer rights.

One address appears on five chains

CoinGecko maps Ethereum, Sonic, BSC, Base and Avalanche to the same FT address. That symmetry comes from deterministic deployment; it does not mean each chain holds a fresh 10-billion allocation.

A LayerZero OFT transfer burns units on the source and delivers a mintable representation on the destination, preserving an intended omnichain economy.

Ethereum alone showed about 1.1966B FT at review. That is one chain-local totalSupply, not the global figure. Because the default OFT burns before it mints the same amount on the destination, time-aligned local supplies can be added without double counting; messages still in flight can make the sum temporarily low, and public or buyback burns reduce it permanently below the initial 10B.

The repeated address is an identity aid, not a supply proof; the canonical mint rule and cross-chain events carry more evidentiary weight than an explorer badge.

The raise produced a position before a token

Primary participants received 10 FT per contributed dollar inside an ERC-721 ftPUT rather than as a freely spendable balance. The February 20, 2026 update put net funded capital still held across private, community and public rounds at $183,897,578.66; this was not an additional public-only raise. The public deposit cap was $1B.

Each NFT stores its collateral token, original and remaining amount, FT bought and remaining, strike and conversion reference. The right follows this stateful position, not the letters “FT.”

There was no vesting schedule for participants; liquidity is a choice. Keeping the NFT preserves the put, while withdrawing FT trades protection for a freely transferable asset.

Hold, divest and withdraw lead to different assets

Keeping the NFT leaves FT and backing paired. Divest consumes the FT portion exercised and returns the same deposited asset and amount in proportion; those FT no longer belong to the holder through that position.

Withdrawing releases FT and irrevocably erases the exit right on that portion. The corresponding backing moves from reserved capital into a protocol-controlled buyback-and-burn path.

Buying FT on a DEX therefore buys price exposure without redemption. Buying an ftPUT NFT can transfer the remaining claim, but its value depends on current collateral, remaining FT and marketplace fees.

Backing works while it waits

Docs say principal backing is never spent and stays on its source chain without leverage by default. It can still enter Aave, liquid staking or other venues to earn yield, exposing it to their contracts and exit liquidity.

Yield first pays salaries, marketing, infrastructure and operations; only surplus goes to buybacks. Product fees also buy and burn FT and can unlock Foundation, Team and Incentives allocations in a 40:40:20 ratio.

This means a protected position depends on the backing ledger and unwind capacity, while secondary FT depends on buyback execution and product revenue. They are related but not identical risk pools.

The phrase “backing is never spent” still permits deployment into external protocols. Returning principal on demand requires those positions to unwind at the needed time and denomination.

The token can stop while administrators keep a corridor

FT is non-proxy and burnable: holders can burn their own balance, while burnFrom requires sufficient allowance from the affected account. Owner or configurator can pause or resume ordinary transfers and replace the configurator; only the owner manages LayerZero peers/delegate and changes the token name/symbol.

A pause is selective. The LayerZero endpoint, configurator, and transfers from or to the configurator remain allowed; approvals and permits can still be created. This is operational recovery power, not a uniform freeze. A configurator transferFrom still requires sufficient allowance from the affected account.

OFT configuration makes bridge correctness depend on trusted peer wiring and LayerZero delivery. Identical addresses reduce user confusion but do not remove messaging or admin risk.

A product suite grew around the put

The March update dates Flying Tulip’s launch to February 23, 2026. The project subsequently reported live PUT execution, ftUSD and Sonic margin lending. On September 1 it announced Trade on Sonic for spot and leveraged spot trading; the same announcement still described the central limit order book as being hardened. Product delivery therefore has to be read feature by feature.

ftUSD targets a dollar through delta-neutral strategies and Lend supplies margin accounts. Their yield and “no liquidation” marketing do not transfer into a legal guarantee for FT or ftPUT holders.

Ordinary FT conveys token functions and implemented product access; a valid ftPUT retains an exit backed by its remaining assets. Reviewed documents do not establish company equity, insurance coverage or binding token votes over administrators. That documentary limit does not determine every legal remedy a holder might have.

How the project changed

  1. 2025-09
    Private funding announced

    Flying Tulip announced a $200M private round and a planned public allocation with onchain exit rights; later reporting distinguished commitments from capital actually retained.

  2. 2026-01-27
    PUT position controls introduced

    The project described how to hold, exercise, withdraw or transfer an ERC-721 ftPUT position.

  3. 2026-02-20
    Net capital snapshot

    The sale update reported $183,897,578.66 still funded across rounds after refunds and exits.

  4. 2026-02-23
    Protocol rollout begins

    The March update identifies this as the protocol launch date.

  5. 2026-09-01
    Trade announced live on Sonic

    The project announced spot and leveraged spot trading; its central limit order book was still being hardened.

Evidence and primary sources

Last evidence review: 2026-09-05

What is Flying Tulip?

FT is the omnichain token of Flying Tulip, deployed at the same CREATE2 address 0x5dd1a7a369e8273371d2dbf9d83356057088082c on Ethereum, Sonic, BSC, Base and Avalanche. The design minted 10,000,000,000 FT on Sonic and uses LayerZero OFT burn/mint messaging to move economic supply among chains. Each explorer reports only its chain-local outstanding supply; a global figure requires a time-aligned sum across deployments, adjusted for messages still in flight and permanent burns.

Flying Tulip combines capital allocation, an ERC-721 ftPUT marketplace, ftUSD, lending and, by September 2026, live trading on Sonic. The token and products are distinct: FT can move freely, whereas the right to recover primary contributed assets remains encoded in a particular ftPUT position.

What problem does Flying Tulip solve?

The project funds development without forcing early contributors to surrender all downside protection. A primary contributor receives 10 FT per contributed dollar inside an ftPUT. The NFT records the contributed token, remaining amount, FT amount and strike reference, allowing partial or full return of the same asset and amount.

Backing is deployed in liquid, described low-risk onchain strategies; its yield first funds operations and surplus funds buybacks. This creates dependencies on smart contracts, external venues, liquidity and administrators. “Capital protection” is a mechanism backed by remaining assets, not a sovereign guarantee or insurance policy.

How does Flying Tulip work?

A holder can keep the ftPUT, divest FT to recover proportional original collateral, or withdraw FT. Withdrawal permanently cancels the put for that portion and releases backing for protocol-directed buyback and burn. A secondary FT buyer receives no put; a marketplace buyer of the entire ftPUT NFT acquires its remaining collateral-linked position.

FT itself is a non-proxy OFT. Only Sonic mints the initial 10B at deployment; cross-chain sends burn on one chain and mint via LayerZero delivery on another. Owner or configurator can pause or resume transfers and replace the configurator. Only the owner controls LayerZero peers/delegate and changes the token name/symbol. During pause, endpoint and configurator paths retain transfer exceptions.

Key facts

  • FT uses 0x5dd1a7a369e8273371d2dbf9d83356057088082c on Ethereum, Sonic, BSC, Base and Avalanche.
  • The token is a LayerZero OFT; same-address chain supplies are representations of one omnichain economy.
  • Constructor permits mainnet initial mint only on Sonic chain 146 and mints 10,000,000,000 FT once.
  • Blockscout showed 1,196,632,933.933558476523365592 FT and 736 holders on Ethereum at review; this is not global supply.
  • Primary allocation is 10 FT per $1 contributed. The 10B pre-mint is the supply cap, while public and protocol-directed burns can reduce outstanding global supply.
  • The February 20, 2026 update put net funded capital still held across private, community and public rounds at $183,897,578.66; this was not an additional public-only raise. The public deposit cap was $1B.
  • Primary FT is locked in an ERC-721 ftPUT holding collateral denomination, remaining backing and remaining FT.
  • Divest returns the same contributed token and amount pro rata; withdraw unlocks FT and permanently destroys that portion’s put.
  • Open-market FT does not include a put. A transferred ftPUT NFT can carry the remaining protected position.
  • Backing capital is described as unspent, unlevered and unbridged by default, but can be deployed to third-party onchain yield venues.
  • Backing yield pays ecosystem costs first; surplus and product revenue may fund buyback/burn. Revenue-funded burns unlock Foundation/Team/Incentives in a 40:40:20 split.
  • Holders can burn their own FT; burnFrom requires sufficient allowance from the affected account. Owner or configurator can pause or resume transfers, with movement exceptions for the configurator and LayerZero endpoint while paused.
  • Owner/configurator can rotate configurator; owner controls LayerZero peers/delegate and can change name/symbol.
  • FT supports token transfer, burning and implemented product functions; it does not automatically include a put. Reviewed materials do not establish company equity, guaranteed yield, insurance coverage or binding token control over administrators.

Official links

Categories

Decentralized Finance (DeFi)Lending and BorrowingStablecoin ProtocolOn-chain TradingDerivativesOmnichain Token

Related coins

Frequently asked questions

Does every FT have a $0.10 floor?

No. Only FT still attached to a funded primary-sale ftPUT has the exit mechanism. It returns the original contributed asset according to the position, not a guaranteed future dollar value. Market FT alone has no put.

What does divest return?

The same contributed asset and amount, pro rata to FT exercised, subject to the position’s remaining backing and contract operation.

What happens if I withdraw FT?

You receive transferable FT and permanently invalidate the put on that portion; released backing can fund protocol buyback and burn.

Can I sell the protection?

The ftPUT is an ERC-721 and may be transferred or traded as a whole position. Buyers must assess remaining collateral, FT and marketplace fees.

Is total supply 10 billion on every chain?

No. The 10B cap was minted initially on Sonic. A default OFT transfer burns on the source before minting the same amount on the destination, so synchronized chain-local totalSupply values can be summed without double counting. Messages in flight and explorer snapshots taken at different times can make that sum temporarily low or inconsistent, and permanent burns reduce it below 10B.

Can administrators freeze transfers?

Owner or configurator can pause or resume ordinary transfers and replace the configurator. While paused, endpoint/configurator exceptions remain, as do approvals and permits; configurator transferFrom still needs sufficient allowance from the affected account. Only the owner controls LayerZero peers/delegate.

Is backing risk-free?

No. It faces contract, external venue, liquidity, oracle, operator and synchronized-exit risks even under conservative policies.

Do FT holders govern Flying Tulip?

Reviewed materials did not establish binding token voting over admins, treasury or the operating organization. FT and a valid ftPUT convey different onchain rights.

External trackers

Choose a tracking site for Flying Tulip: