Channel
@blockstream
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,564subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001222265879 |
|---|---|
| Type | Channel |
| Username | @blockstream |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/blockstream |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 10:25 | 1,564 | -3 |
| 10 Aug 2026, 00:41 | 1,567 | +3 |
| 7 Aug 2026, 07:02 | 1,564 | +2 |
| 6 Aug 2026, 20:45 | 1,562 | first reading |
21 posts held, back to 13 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 2 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 21 (13 March 2026 – 7 August 2026) |
| Views total | 2,816 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 18:05 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.
Measured directly from 1 video 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.
Post-quantum signatures aren't one-size-fits-all, and now developers can find the SHRINCS setup that fits theirs. Blockstream Research's explorer lets you tune signature size, signing cost, and verification cost to match your wallet, node, or miner. Their sweep of 25,935 candidates found a fallback signature about 2 KB smaller than NIST's SLH-DSA, and 28% cheaper to verify. https://blog.blockstream.com/searching-f…
https://x.com/Blockstream/status/2084340794660388895
Jade is unaffected by the recently disclosed RNG vulnerability affecting other hardware wallets. Every Blockstream Jade recovery phrase comes from multiple independent entropy sources. On an affected device? Here's how to migrate calmly, step by step: https://blog.blockstream.com/jade-unaffected-coldcard-vulnerability/
The Blockstream Jade lineup (Jade Classic, Jade Core, and Jade Plus) is unaffected by the recently reported RNG issue with another company. We are preparing a blog post outlining best practices for anyone moving bitcoin to a new wallet, including how to generate fresh keys, verify addresses, conduct a test transaction and securely retire an old recovery phrase. Frontier LLMs are uncovering previously overlooked vul…
Simplicity has been live on Liquid mainnet for nearly a year. Now the full developer toolchain is here. Build high-assurance Bitcoin contracts in a zero-friction environment with autocomplete, instant testing, post-quantum signatures, and a finalized lending template. Here's what builders can ship today and what's coming next. https://blog.blockstream.com/building-on-simplicity-what-ships-today-what-is-coming-next…
New 0-conf infrastructure for Liquid and other Elements-based deployments is here. Swap services, exchanges and applications that accept Liquid payments now have access to near-instant transfer times. Details in the technical explainer below. https://blog.blockstream.com/0-conf-for-elements-and-liquid-a-technical-explainer/
Simplicity's site just got a full redesign. Simplicity lets you prove exactly how a contract behaves before it goes live. No surprise fees, no transactions failing mid-execution. The security guarantees are part of the language, not bolted on after. Live on Liquid mainnet, running real financial contracts, and built for the developers and institutions building high-assurance Bitcoin applications. https://blog.bloc…
When you run a Bitcoin node, you can prove the 21 million cap yourself. Every block. No trust required. The Zcash Orchard bug, undetected for four years, is a reminder of what you give up when supply verifiability is traded for privacy. The Liquid Network shows there is another way. Strong privacy with publicly verifiable supply. https://blog.blockstream.com/what-the-zcash-orchard-bug-reveals-about-verifiable-supp…
Core Lightning 26.06 "Quantum-Resistant Lightning Channel" has shipped. Graceful shutdowns, precise send amounts, smarter payment retries, and enhanced payment privacy. Your Lightning node runs cleaner and your payments stay harder to observe. ⚡ The big architectural shift in this release is bwatch, a new block-watching plugin that fundamentally changes how CLN interacts with the Bitcoin blockchain. No more 30-sec…
The results are in from the Blockstream Turin Simplicity Hackathon! 20 developers spent a weekend building real smart contracts on Simplicity covenant DEXs, inheritance tools, post-quantum wallets, and more. First place goes to: PQ Liquid Wallet, taking home $3,000 in bitcoin: PQ Liquid Wallet is the first wallet to test Blockstream's research on protecting Bitcoin from future quantum computers. Second and third pl…
There is no concrete post-quantum signature scheme for Bitcoin today. But over the last year Blockstream Research has been working on exactly this. Director Jonas Nick lays out the proposal: OP_CHECKSHRINCS, a hash-based signature opcode for post-quantum Bitcoin. SHRINCS reaches up to 3 TPS on the compact path. 580-byte signatures from a dedicated signing device. A stateless fallback always available. Already demo…
As the Liquid Network’s technical provider, Blockstream is sharing an updated roadmap for the core development workstreams it leads. 0-conf payments, quantum readiness, BitVM bridge exploration, institutional custody, Simplicity-based DeFi infrastructure, and much more are in development. Details. 👇 https://blog.blockstream.com/liquid-network-roadmap-0-conf-quantum-readiness-and-bitvm/
Showing the 12 most recent of 21 posts we hold for @blockstream. 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 — 307,044 of 1,169,250entries 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 4 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Blockstream” (@blockstream), 1,564 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/blockstream.
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.