Telegram RegisterThe public register of Telegram

Channel

GetBlock 🧊 Web3 Infra

@getblock_announcements

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,054subscribers

-16 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001787084373
TypeChannel
Username@getblock_announcements
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/getblock_announcements

Growth

2,0542,0702,0627 August 2026 — 2,070 subscribers7 August 2026 — 2,070 subscribers10 August 2026 — 2,062 subscribers13 August 2026 — 2,054 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net -16. 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 2,052–2,072 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:152,054-8
10 Aug 2026, 09:382,062-8
7 Aug 2026, 14:142,070no change
7 Aug 2026, 06:162,070first reading

Engagement

20 posts held, back to 23 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
11.1%
avg views ÷ 2,054 subscribers
Avg views / post
229
8 posts measured
Reaction rate
1.56%
reactions ÷ views · ER floor
Posts in window
8
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 7 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (23 June 20266 August 2026)
Views total1,828
Reactions total25
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

89 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 41.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3741.6%
🔥3539.3%
👏88.99%
👍44.49%
🤩22.25%
🥰22.25%
🎉11.12%

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 89reactions 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 23 June 2026 to 6 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.

Recent posts

6 Aug 2026, 08:20 UTC68 views3 reactionsread 7 August 2026

📆 Monthly Receipt Drop Everything new on GetBlock since July: 📈 Shared Nodes speed boost – up to 2.5x higher RPS on all plans. Starter's now 250 RPS. Pro – 800 RPS. ⚡Flashblocks on Base + Optimism. Same endpoint, earlier access to block data. 🟢 Robinhood Chain now on GetBlock. Shared and Dedicated Nodes. 🛠 New add-ons for Dedicated Nodes: ERC-4337 Account Abstraction stack, Overlay Methods, Beacon API. For Ether

🔥3

30 Jul 2026, 17:31 UTC222 views3 reactionsread 7 August 2026
Photo

⏳ Sim sunsets in 48 hours Dune is shutting Sim down on August 1 at 9 AM EST. If you are running it in production, requests stop resolving after that. Migrating to GetBlock is one command in your AI coding agent: get docs.getblock.io/migration/migrate-to-getblock-with-ai.md The agent pulls the runbook and works through three phases: • Assess. Scans your codebase for every endpoint, identifies the chain, interface

🔥21

29 Jul 2026, 15:27 UTC206 views3 reactionsread 7 August 2026
Photo

🚀 Three new add-ons are live on Dedicated Nodes If you run an EVM dedicated node with us, three new capabilities are now one click away. ⚡ ERC-4337 A bundler runs next to your node and serves the full account abstraction RPC. Smart contract wallets and paymasters, with no bundler of your own to maintain. 🔁 Overlay methods Replay historical blocks against modified contract bytecode and pull logs a contract never e

🔥21

27 Jul 2026, 11:55 UTC223 viewsread 7 August 2026

​​⚠️ Retiring 5 Chains from Shared Nodes We're ending Shared Node support for the following networks: • Bahamut • Tenet • Oasis • Nervos • Allora Reach out if you need migration help.

23 Jul 2026, 15:27 UTC293 views2 reactionsread 7 August 2026
Photo

🚀 Shared Node RPS limits are up across every paid plan Same prices, same compute units, more throughput. The new limits are live and already applied to active subscriptions, so there is nothing to migrate and nothing to reconfigure. What changed: ⚡️ Starter: 100 → 250 RPS ⚡️ Growth: 150 → 300 RPS ⚡️ Advanced: 300 → 450 RPS ⚡️ Scale: 400 → 600 RPS ⚡️ Pro: 500 → 800 RPS ⚡️ Premium: 700 → 800 RPS RPS is the lim

1🔥1

22 Jul 2026, 17:23 UTC269 views5 reactionsread 7 August 2026
Photo

🚀 Limitless Node is now self-serve You no longer need to talk to Sales to get one. Open your GetBlock dashboard, click Create New Node, and deploy an isolated RPC endpoint the same way you would a Dedicated Node. What you get: ⚡️ Fixed RPS with unlimited requests, no compute unit billing 🔒 Isolated capacity with dedicated routing 🌐 11 supported chains, full and archive 💸 Up to 7x cheaper than a comparable dedi

🔥41

21 Jul 2026, 11:30 UTC272 views3 reactionsread 7 August 2026

🌙 Midnight Mainnet is now supported on GetBlock. Midnight is a privacy-focused blockchain built for applications where confidentiality and compliance are as important as decentralization. 🔒 What makes Midnight different: • A hybrid ledger holding public and private data side by side • Built on Substrate with GRANDPA finality and ~6-second block times • Smart contracts in Compact, a TypeScript-based language for

🔥3

20 Jul 2026, 14:29 UTC275 views6 reactionsread 7 August 2026
Photo

🛠 GetBlock RPC Benchmark is live: test any endpoint, free We just shipped a tool the whole RPC market needed. Paste any endpoint URL and get a live speed and reliability report in about 60 seconds: ⚡ p50/p95/p99 latency and jitter 📊 success, error, and timeout rates 🧱 block freshness vs chain head 🏆 overall score out of 100, side by side with GetBlock Every run tests our production infrastructure in real time.

🔥32🎉1

15 Jul 2026, 09:47 UTC354 views4 reactionsread 7 August 2026
Photo

💚 Robinhood Chain is live on GetBlock Robinhood's new Layer 2 for tokenized stocks and ETFs opened its mainnet on July 1, and you can already build on it with GetBlock. ⚡ What's under the hood: 🔹 Arbitrum Nitro rollup, ETH for gas, settlement on Ethereum 🔹 ~100ms blocks with arrival-order sequencing 🔹 Stock Tokens: equities and ETFs as ERC-20s, tradable around the clock 🔹 ERC-4337 account abstraction out of the

2🔥2

10 Jul 2026, 15:19 UTC413 views10 reactionsread 7 August 2026
Photo

📊 The new GetBlock Status Page is live One place to see whether your endpoints are healthy, no ticket required. ✅ Every major protocol, testnet and mainnet ✅ Separate status for our SG, NY, and FRA clusters ✅ Checked every minute, current to the last 60 seconds ✅ Maintenance schedule and full incident history ✅ Client updates, migrations, and sunset notices in one feed May all your dashboards be green. This o

7🔥3

10 Jul 2026, 13:30 UTC371 views3 reactionsread 7 August 2026

​​🎙️ New GetBlock Podcast episode is live! In this episode, we speak with Vadim Makovsky, Founder & CEO of Diffuse We discuss: 🔐 How Diffuse combines ZK and TEE 📈 How Diffuse Prime works for lenders and borrowers 🛡️ DeFi security and risk management 🏦 Tokenized real-world assets 📉 The current state of DeFi yields ❄️ Building and surviving through crypto winter ▶️ Watch the full episode on YouTube: https://www.youtu

🔥3

9 Jul 2026, 11:15 UTC390 views6 reactionsread 7 August 2026

Monthly recap 🧊 We won't pretend this is a normal month. It was pretty big. June rundown: 🔒 SOC 2 Type II – done. Independently audited by Atom Assurance. 📊 More Shared Node plans: Growth ($99), Scale ($349), Premium ($699). ⚡ CU limits up to 75% higher on Shared plans. Price increase: $0. 🌐 New integrations: Tempo Mainnet & Testnet, Midnight Mainnet, Polygon gRPC. 🔷 Polygon gRPC. Now supported alongside JSON-RPC a

6

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

Citation-graph rank — 395,659 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

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

“GetBlock 🧊 Web3 Infra” (@getblock_announcements), 2,054 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/getblock_announcements.

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.