Channel
@HypurrFi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
67subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002633802648 |
|---|---|
| Type | Channel |
| Username | @HypurrFi |
| Description | Stake for yield borrow USDXL for leverage. Accelerated yield go purr. |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/HypurrFi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 01:30 | 67 | no change |
| 7 Aug 2026, 06:17 | 67 | first reading |
20 posts held, back to 16 March 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 pageof 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 15 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
3 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 33.3% | |
| 👎 | 1 | 33.3% | |
| 🤝 | 1 | 33.3% |
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 2 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 3reactions 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 16 March 2026 to 15 May 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.
HypurrFi is winding down and closing. Euler is taking over the Euler markets contract stack on Hyperliquid, and Clearstar will continue to curate the markets and vaults. There are no security issues or exploits, this is purely a business decision. We will announce today and Pooled will begin the wind down process over the next few weeks to ease the transition for users. We are gracefully winding down the HypurrFi P…
👎1🤝1
New borrows and new lending for USDH in the Pooled Market has been frozen. With the sunset of USDH, we encourage users to begin the process of unwinding positions and repaying USDH. To check your positions in pooled please connect to: https://app.hypurrfi.com/dashboard/pooled
https://x.com/HypurrFi/status/2054905963019108689?s=20
https://x.com/hypurrfi/status/2049571871994323396?s=46
The HypurrFi landing page has been restored at https://hypurrfi.com. The app is still at https://app.hypurrfi.com. This is a courtesy message to let you know this is an intended change to return back to the normal flow. There are additional slight updates to the app coming later today for those with an eye out for updates.
USDe bridging has resumed. HypurrFi Governance has unfrozen USDe in pooled.
HypurrFi Borrowers: Please monitor your USDe position in Pooled. USDe is not enabled as collateral, so there is no danger of bad debt to HypurrFi. However, the USDe OFT is currently paused on Hyperliquid EVM. The HypurrFi Pooled market for USDe is frozen, so no additional USDe can be deposited to ease rates at present. The market will be unfrozen when we have clarity around the path of the USDe redemption flow in th…
USDT0 bridging has resumed. HypurrFi Governance has unfrozen USDT0 in pooled. Mewler configurations will be restored shortly by Clearstar.
The cmETH asset is paused at the contract level by the Mantle team, this prevents normal operations of the asset, and as a result prevents you from being able to call removeCollateral out of the isolated legacy vault, Governance has temporarily stopped interest on this market while the situation is being reviewed by Mantle.
Due to today's KelpDAO rsETH exploit via LayerZero: • HypurrFi is unaffected • However, out of an abundance of caution and following the lead of the USDe and USDT0 teams taking action to pause their bridges, we’ve frozen the USDT0 and USDe markets on Pooled temporarily • Withdrawals and repays still function normally • If you need to withdraw/repay or manage your position, those positions are visible on your Dashboar…
https://x.com/HypurrFi/status/2042674325006979164
The Swype.fun Card and the HypurrFi beta card program have officially concluded and all cards have been deactivated. Season Mew Points based on card usage associated with HypurrFi positions will be distributed once the new product is live in the coming days. To all Season Mew participants: Thank you! Your usage and feedback directly informed the product. To prepare for the full card launch, previous Swype Card user…
Showing the 12 most recent of 20 posts we hold for @HypurrFi. 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.
Citation-graph rank — 815,572 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 3 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“HypurrFi Announcements” (@HypurrFi), 67 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/HypurrFi.
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.