Channel
@HubbleProtocol
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
724subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001636502416 |
|---|---|
| Type | Channel |
| Username | @HubbleProtocol |
| Created | Between 1 December 2021 and 8 August 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/HubbleProtocol |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 14:53 | 724 | no change |
| 7 Aug 2026, 00:18 | 724 | first reading |
20 posts held, back to 8 August 2022 — 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 6 June 2023. An engagement rate over an empty window would be a number about nothing.
156 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 45.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 71 | 45.5% | |
| 💩 | 29 | 18.6% | |
| 🔥 | 15 | 9.62% | |
| 🖕 | 15 | 9.62% | |
| ❤ | 11 | 7.05% | |
| 👎 | 5 | 3.21% | |
| 😢 | 2 | 1.28% | |
| 😱 | 2 | 1.28% | |
| 🤬 | 2 | 1.28% | |
| 🍾 | 1 | 0.641% | |
| 🤡 | 1 | 0.641% | |
| 🤩 | 1 | 0.641% | |
| 🥰 | 1 | 0.641% |
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 19 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 156reactions 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 8 August 2022 to 6 June 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Attention @everyone. Stability Fee Update The Stability Fee will be set to 2% on June 13 at 14:00 UTC. Here’s a quick refresher on Hubble’s Stability Fees: 👉 The Stability Fee helps maintain the $USDH peg. A fee increase encourages users to acquire USDH from the market and repay their loans, creating upward pressure on the peg. 👉 All fees contribute to the Hubble Native Yield (HNY), which is earned by users provi…
👍20💩17❤4🖕3😱2🤡1🤬1
We are thrilled to announce the launch of another Hubble vault, this time with Helium. $HNT - $USDH is now live, with 200 weekly $HNT incentives! The vault enables Helium & Hubble users to earn, while supporting liquidity for both tokens 🫡 Enjoooy @everyone Vault link: https://app.kamino.finance/liquidity/hnt-usdh-orca/CJhyKExm1sqFkcRnemEQj847TgqEsPEgE5GbiHFqntkH
❤3🔥3🖕3
Our Monthly Town Hall is coming up on Wednesday, May 3rd - It's gonna be a good one Join us in the Hubble Portals room for some juicy alpha on what's in store for vault enjoyooors🫡 ...ohh and one more thing DRip is leveraging the power of compressed NFTs and hooked us up with some of their codes....so there might be a few of those to be had See you there Folks: https://theportal.to/?room=2d16d1a8-3ccc-4e28-be2f-…
👍4🖕2
Hi @everyone , quick announcement on upcoming community events. At the top of the server you can see that we currently have 3 events lined up. Please signal your interest if you can, this helps us plan ahead of time. Monthly community townhall - April 5th Our monthly townhall is up again on Wednesday, 5 April @ 17:00 (GMT), make sure to join in to get the chance to get updates from the core contributors. We will b…
💩5❤3👍3🖕2
We have some exciting news: Hubble is live once again, with USDH minting enabled on all pools!🚀 The devs have spent the past two weeks preparing the platform to get back up and running, with numerous points that have been addressed. Amongst many others, these include: - Clearing up the final, under-collateralized loan - Reevaluating collateral assets following the FTX crash - Increasing the robustness of oracles &…
👍7🔥6💩3🖕2
An official Hubble Retrospective on the FTX Crash The article (V2): https://bit.ly/Hubble-Stress-Test-FTX The retrospective gets into the details of Hubble's decision making throughout the crash, which measures were already in place that allowed users additional safety, and what lessons were learnt on how to build the system even more resilient. There was a lot to cover, and it's strongly encouraged that you read…
👍5❤1
Just a checkin in real time of what we are doing. We are aware that the SRM and soBTC positions pose an existential risk to Hubble and as such we are working on a solution which would have Hubble assuming the bad debt and with none passed to any of our users. Technically, we have enabled redemptions (an old feature that was never enabled due to bad UX), so we can redeem SRM and BTC at the currently trading price on …
👍7😢2
Due to the high assumption of risk for Solana on-chain BTC, we've decided to protect the Stability Pool from taking BTC risk and allow liquidators to take on the risk instead. If loans are becoming undercollateralized, the mechanism of redistribution will take place and debt will be redistributed across all loans
👍5💩4🖕3🤬1
It's Part 2 of the Curve 4Pool Drama! Buckle up, and take a trip down memory lane to a time when DAI got death threats, 20% APY attracted $20 billion, and the Degenbox was cranking leverage on that 20%. The partnership between Terra and Abracadabra takes center stage here, and then things go very wrong--before they go very very wrong: https://blog.hubbleprotocol.io/curve-wars-and-4pool-drama-part-2/?utm_source=tele…
👍3🔥2
Looking for some good lending strategies to up your DeFi game? We've got a few from the Solana lending community for your yielding pleasure: https://blog.hubbleprotocol.io/best-lending-strategies-on-solana/?utm_source=telegram&utm_medium=social&utm_campaign=blog_internal
👎4👍2
Latest blog post covers the Curve Wars and the dramatics that was the 4Pool. The belligerents: Curve, MakerDAO, Terra, Frax, and even Abracadabra. Part 1: https://blog.hubbleprotocol.io/curve-wars-4pool-part1/?utm_source=telegram&utm_medium=social&utm_campaign=blog_internal
🔥3👍1👎1
Heads up! We’ve got our first ever metaverse AMA kicking off right now, hosted in Portals, by the Portals team🔥 Jump in now👇 https://theportal.to/?room=963f644b-ba2b-4589-862d-459ba25f611e
🍾1🤩1
Showing the 12 most recent of 20 posts we hold for @HubbleProtocol. 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 — 192,164 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 8 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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Hubble Protocol Announcements” (@HubbleProtocol), 724 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/HubbleProtocol.
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.