Channel
@flyingtulipann
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
441subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003564629128 |
|---|---|
| Type | Channel |
| Username | @flyingtulipann |
| Created | Between 1 December 2025 and 24 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 12 September 2026 |
| On Telegram | t.me/flyingtulipann |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 11:16 | 441 | -4 |
| 28 Aug 2026, 06:07 | 445 | +5 |
| 14 Aug 2026, 22:44 | 440 | -1 |
| 6 Aug 2026, 19:18 | 441 | no change |
| 6 Aug 2026, 06:33 | 441 | first reading |
20 posts held, back to 24 February 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
262 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 74.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 195 | 74.4% | |
| ❤ | 41 | 15.6% | |
| 👍 | 6 | 2.29% | |
| 👏 | 6 | 2.29% | |
| 😁 | 6 | 2.29% | |
| 💯 | 3 | 1.15% | |
| 🫡 | 3 | 1.15% | |
| 🤯 | 2 | 0.763% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 262 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 24 February 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Flying Tulip July Update In July, Flying Tulip moved closer to an integrated on-chain financial system. — Lend TVL reached $13.4M, with active loans at $1.3M — ftUSD supply grew to $4.5M, while Ethereum ftUSD APY stayed above 7% for a third month, without liquidity mining or token incentives — PUT backing generated $1.2M in all-time yield We also burned 8.8B FT, approximately 88% of total supply, reducing FDV to ~…
❤10
We just burned ~$900m of FT, reducing FDV to ~$100m. ➡️ Read about it in the blog post: https://blog.flyingtulip.com/ft-burned-900m ➡️ The new Statistics page now includes a full FT supply breakdown, tracking protocol buybacks and showing the burn: https://flyingtulip.com/statistics/ft-supply
🔥13👏1
Curve DAO Proposal #1455 has passed with 100% support. The FT/ftUSD gauge has been approved, making the pool eligible to receive CRV emissions based on gauge weight. ➡️ Add liquidity to the /ftUSD pool here: https://www.curve.finance/dex/ethereum/pools/0x68102ff5406475881462880a8da3c9bc9181ad6c/deposit ➡️ Tweet: https://x.com/flyingtulip_/status/2082069813736755376
🔥7
Your weekend listen 🎧 “If you can place a limit order on our spot system, that limit order is earning yield because it’s in the margin account being lent out on the other side. So there’s never a point where your capital isn’t put to work.” Andre Cronje joined The Rollup to discuss security vs UX, curated-vault risk, immutability and composability, equity margin accounts, RFQ liquidations, ftUSD, the shift from De…
🔥4
The Flying Tulip community is now open to everyone. Join us on Telegram or Discord for community discussion and product updates: ➡️ Telegram https://t.me/flyingtulipgroup ➡️ Discord https://discord.gg/flyingtulip Discord also offers ticket-based technical support, community roles, dedicated groups for Marketplace PUT deals and product feedback, and private groups for contributors.
🔥8❤4
Two new Flying Tulip dashboard are live. The ftUSD dashboard breaks down the APY earned by staked ftUSD into stablecoin collateral yield and delta-neutral strategy yield. It also shows leverage, borrowing and staking APYs, together with a profitability analysis of the delta-neutral leg. ➡️ https://flyingtulip.com/ftusd/dashboard/#strategy-breakdown The Statistics page tracks protocol fees and shows how cash flows …
🔥9😁1
Flying Tulip June Update In June, we expanded ftUSD’s fully on-chain delta-neutral architecture to Ethereum, launched a new version of the Flying Tulip PUT Marketplace, and continued pre-launch work on Spot, leverage, and TRS. Lend TVL grew to $9.55M, doubling over the past 30 days. ftUSD supply increased from $2.07M to $3.94M, with current APYs of 13.27% on Ethereum and 5.53% on Sonic — stake with no lockups and i…
🔥11👍4
The new Flying Tulip PUT Marketplace is live. The Marketplace lets users buy and sell Perpetual PUTs: NFT-represented on-chain positions issued during the primary sale that give holders the right to redeem the original backing capital or withdraw the associated FT. The Marketplace has already generated over $1.4M in trading volume, with more than 250 completed sales and 130 active listings. This version improves t…
🔥9❤2
Flying Tulip May Update In May, we focused on optimizing, hardening, and scaling ftUSD, margin-based Lend, and the infrastructure needed for Spot, Leverage Trading, and TRS. ftUSD supply grew from $1.49M to $2.07M, with activity-based APY of 29.36% on Sonic and 8.02% on Ethereum. Margin-based Lend expanded to Ethereum, and total Lend TVL reached $4.90M — all without incentives or points. Read the full update: http…
🔥9❤3😁1
ftUSD is now available as collateral on Lend. Also, BTC borrow costs were reduced on Sonic and Ethereum through interest rate model optimization. Sonic Lend parameters were updated to make borrowing more accessible: ▸ minimum margin equity reduced: $250 → $10 ▸ minimum repayment amount reduced: $10 → $2 ➡️ Deposit in Lend: https://flyingtulip.com/lend ➡️ Lend Docs: https://docs.flyingtulip.com/product-suite/ft-len…
🔥12❤4
USSD is now available on Flying Tulip. Sonic’s native stablecoin can be used as collateral in Margin Lending, and to mint ftUSD and earn. ➡️ Deposit in Lend: https://flyingtulip.com/lend ➡️ Deposit to mint ftUSD and earn: https://flyingtulip.com/ftusd ➡️ Lend Docs: https://docs.flyingtulip.com/product-suite/ft-lend ➡️ ftUSD Docs: https://docs.flyingtulip.com/product-suite/ft-usd Questions? Join our Discord: disco…
🔥12💯2❤1👏1
Margin Lending is now LIVE on Ethereum This is a key building block for Flying Tulip, extending the capital-efficiency layer by allowing users to supply assets to earn yield or borrow against collateral on Ethereum. It also enables delta-neutral strategies needed to scale ftUSD, while establishing the margin infrastructure for Spot, leveraged trading, and TRS. Margin Lending is initially launching on Ethereum in a…
🔥9❤4
Showing the 12 most recent of 20 posts we hold for @flyingtulipann. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 4 September 2026 — this entry's latest reading, not the date you are reading this.
“Flying Tulip Announcements” (@flyingtulipann), 441 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/flyingtulipann.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.