Telegram RegisterThe public register of Telegram

Channel

Babylon Official Announcements

@BabylonAnnouncements

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

18,914subscribers

-92 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001545359122
TypeChannel
Username@BabylonAnnouncements
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/BabylonAnnouncements

Growth

18,91419,00618,9607 August 2026 — 19,006 subscribers7 August 2026 — 19,006 subscribers8 August 2026 — 18,997 subscribers9 August 2026 — 18,989 subscribers10 August 2026 — 18,965 subscribers11 August 2026 — 18,952 subscribers12 August 2026 — 18,938 subscribers12 August 2026 — 18,928 subscribers14 August 2026 — 18,914 subscribers7 August 202614 August 2026
9 measurements spanning 7 days, net -92. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 18,900–19,020 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:0418,914-14
12 Aug 2026, 22:2318,928-10
12 Aug 2026, 01:3718,938-14
11 Aug 2026, 03:1618,952-13
10 Aug 2026, 04:1118,965-24
9 Aug 2026, 02:5118,989-8
8 Aug 2026, 00:2218,997-9
7 Aug 2026, 12:0019,006no change
7 Aug 2026, 11:5019,006first reading

Engagement

20 posts held, back to 17 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof 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 2 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
153
Videos
51
Links
337

Lifetime counters from Telegram’s own channel header, read 14 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.

Video runtime
2m 42s
Average length
41s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

105 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 41.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4441.9%
🔥4038.1%
👍1110.5%
🍾87.62%
😁10.952%
🤣10.952%

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 105reactions 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 17 January 2026 to 2 June 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.

Recent posts

2 Jun 2026, 14:23 UTC504 views5 reactionsread 14 August 2026

Prefer a written guide? We’ve published a step-by-step written guide covering: wallet setup, faucet claims, vault setup, posting native Bitcoin collateral, borrowing, repayment, closing a position and troubleshooting. Read the guide👇 https://docs.babylonlabs.io/trustless-bitcoin-vault/use-for-lending/quickstart/

5

2 Jun 2026, 14:22 UTC480 views3 reactionsread 14 August 2026

Want to test native Bitcoin-backed borrowing with Aave v4 on Public Testnet? Vlad the DeFi Product Lead takes you through a step by step video guide covering: wallet setup, faucet claims, vault setup, posting native Bitcoin collateral, borrowing, repayment, closing a position and troubleshooting. Watch the guide👇 https://www.youtube.com/watch?v=ANx5GxIV1Xs

3

2 Jun 2026, 13:27 UTC402 views6 reactionsread 14 August 2026
Video

Native Bitcoin-backed borrowing is live on Public Testnet with Aave v4. Powered by Babylon Trustless Bitcoin Vaults, users can post Bitcoin as collateral and borrow on testnet without giving up custody, wrapping, or bridging. This is the latest step in building native Bitcoin-backed credit markets. This testnet allows: 1️⃣ BTC holders and integration partners, including wallets, custodians, OTC desks and others to

6

14 May 2026, 12:30 UTC478 views3 reactionsread 14 August 2026
Photo

1 hour to go until the quarterly founders call ! Join the co-founders of Babylon David Tse and Fisher Yu as they dive into: 🧮 Trustless Bitcoin Vault updates 🔍 Wins, learnings & optimizations 💬 Community Q&A 📺 X livestream Got questions? Drop them in the comments👇

🔥3

13 May 2026, 20:08 UTC434 views7 reactionsread 14 August 2026
Photo

Today we published SCRIPT - Bitcoin Collateral Risk Assessment Framework. Bitcoin holders and applications can use SCRIPT to assess the counterparty risks of any Bitcoin collateral solutions, including Babylon’s. Sovereignty: Sovereign title retention by the Bitcoin holder Clarity: Clear collateral disposition rules that are pre-committed and objective Reuse prohibited: Reuse (such as rehypothecation) of the collat

🔥43

13 May 2026, 13:33 UTC502 views5 reactionsread 14 August 2026
Photo

Babylon Labs' Quarterly Founders Call is tomorrow. Join David Tse and Fisher Yu as they dive into: 🧮 Trustless Bitcoin Vault updates 🔍 Wins, learnings & optimizations 💬 Community Q&A 🗓 Thursday, May 14, 2026 ⏰ 6:30 AM PT | 1:30 PM UTC | 9:30 PM HKT 📺 X livestream Got questions? Drop them in the comments👇

5

10 Apr 2026, 14:27 UTC682 views14 reactionsread 14 August 2026
Video

It’s been 1 year since Babylon mainnet launch. Over the past year, billions in TVL have been activated through Trustless Bitcoin Staking, demonstrating the value of productive native BTC. Trustless Bitcoin Vaults are next, bringing native Bitcoin collateral into on-chain finance. Thank you to everyone who has supported, contributed and helped shape Babylon with us over the past year.

🍾64🔥3😁1

8 Apr 2026, 19:16 UTC545 views3 reactionsread 14 August 2026

Babylon Foundation shared an update highlighting the progress of TBV, Babylon's journey over the past year and amendments to the BABY unlock schedule. Read the update on X - https://x.com/bbn_foundation/status/2041903981723525216

3

26 Mar 2026, 07:18 UTC704 views7 reactionsread 14 August 2026
Video

Trustless Bitcoin Vaults Private Alpha Testnet is live. Alpha tests the deployment of the full TBV ecosystem in a live environment across Bitcoin Signet and Ethereum Sepolia. Users can post BTC collateral and borrow against it through a dedicated Aave v4 spoke. BTC stays on Bitcoin while the borrowing logic runs on Ethereum. Several partners are already testing and contributing in this phase. After Alpha Testnet

🔥4👍3

20 Mar 2026, 13:49 UTC528 views4 reactionsread 14 August 2026
Photo

New episode of The Vault goes live today at 1 pm ET with Clayton Menzel, Foundations Business Development Director at Ledger, Tristan and Diogo! We’ll unpack the real state of BTCFi: How Bitcoin holders think about self-custody How Ledger sees its users evolving What's next for Ledger And whether BTCFi is actually reaching adoption beyond the usual narrative

🍾2👍2

10 Mar 2026, 13:34 UTC673 views9 reactionsread 14 August 2026

Hey everyone, we just shared a new update. Babylon is expanding access to Trustless Bitcoin Vaults through an integration with Ledger. Once the integration is live in H2 this year, BTCVault transactions can be authorized directly from a Ledger device using Clear Signing, allowing 8 million ledger signers to review and confirm vault operations on a secure hardware screen before signing. Trustless Bitcoin Vaults are

🔥62🤣1

12 Feb 2026, 14:57 UTC636 views3 reactionsread 14 August 2026

Big moment at Consensus Hong Kong! When Bitcoin is a $1.4T asset, and Ethereum holds deep onchain liquidity, the real question is not if they should connect. It is how. Native Bitcoin as collateral. Minimal additional trust. No wrapping. No custody handoffs. That unlock changes what Bitcoin can do in digital finance. We are building towards that unlock. https://twitter.com/babylonlabs_io/status/20219453944865550

🔥3

Showing the 12 most recent of 20 posts we hold for @BabylonAnnouncements. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

VERONA Announcements
@verona_announcements · 121,575
Telegram ranks this channel #23 of 92 here — alongside 91 others — read 14 August 2026
Galxe
@galxe · 169,849
Telegram ranks this channel #26 of 95 here — alongside 94 others — read 14 August 2026
Aethir Announcements
@Aethir_Official · 138,031
Telegram ranks this channel #62 of 92 here — alongside 91 others — read 13 August 2026
Plume
@PlumeNetwork · 183,547
Telegram ranks this channel #66 of 88 here — alongside 87 others — read 13 August 2026
Self Chain
@selfchainxyz · 111,107
Telegram ranks this channel #74 of 91 here — alongside 90 others — read 14 August 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“Babylon Official Announcements” (@BabylonAnnouncements), 18,914 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/BabylonAnnouncements.

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.