Channel
@blockbee_news
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
72subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001549981002 |
|---|---|
| Type | Channel |
| Username | @blockbee_news |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 10 October 2026 |
| On Telegram | t.me/blockbee_news |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 74% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Sept 2026, 15:39 | 72 | +2 |
| 30 Aug 2026, 13:55 | 70 | +1 |
| 10 Aug 2026, 00:31 | 69 | no change |
| 7 Aug 2026, 20:26 | 69 | first reading |
20 posts held, back to 6 March 2025 — 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 page of 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 9 July 2026. An engagement rate over an empty window would be a number about nothing.
33 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 54.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 18 | 54.5% | |
| 🔥 | 8 | 24.2% | |
| 👍 | 5 | 15.2% | |
| ❤🔥 | 1 | 3.03% | |
| 🤝 | 1 | 3.03% |
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 14 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 33 reactions 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 6 March 2025 to 9 July 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.
BlockBee WHMCS Plugin is here! 🔌 Accept crypto payments directly in WHMCS 🌐 Powered by BlockBee's hosted checkout 🔒 Funds settle straight to your wallet 🛠️ Setup takes minutes: install, paste your API key, done Read more 👇 https://blockbee.io/blog/post/blockbee-whmcs-plugin-1-0-0
❤1
🪙 Zcash (ZEC) is live on BlockBee! You can now accept ZEC payments through your Dashboard or API. ⏳ Live since 2016, a proven network 💎 Fixed 21M supply, like Bitcoin ⚙️ Activate in the Dashboard or via the Create endpoint Read more 👇 https://blockbee.io/blog/post/blockbee-adds-support-for-zcash-zec
🔥3❤🔥1🤝1
🔔 Payout Webhooks are now live on BlockBee! 📡 Get notified the moment a payout confirms or fails — no polling needed 🔐 Every request is RSA-signed so you can verify it came from us 🔄 Automatic retries with exponential back-off if your endpoint is unavailable 📋 Full delivery logs per payout, right in the Dashboard 🧪 Test your endpoint before going live with a single click Read more 👇 https://blockbee.io/blog/post/pa…
❤1
🆕 Berachain is now live on BlockBee! You can now accept payments on Berachain with the following assets: • BERA • WETH • WBTC • USD₮0 Activate them from your Dashboard or use the API tickers bera_bera, bera_weth, bera_wbtc, bera_usdt0 to get started. Read more 👇 https://blockbee.io/blog/post/blockbee-adds-support-for-berachain
❤2🔥2👍1
🚀 BlockBee PrestaShop Plugin 2.0.0 is out! We simplified the plugin and improved the checkout experience. Customers are now redirected to pay.blockbee.io to complete their payment. 🔒 Webhook signature verification 🛒 PrestaShop 8 and 9 compatibility ❌ Cronjob no longer needed Read more 👇 https://blockbee.io/blog/post/blockbee-prestashop-plugin-2-0-0
❤1
New checkout feature released 🚀 We’ve added Checkout Payment Tolerance to prevent payments from getting stuck in a partial state due to small underpayments caused by fees, rounding, or exchange withdrawals. You can now define a small tolerance so near-complete payments are accepted automatically, while webhooks still report the exact amount paid. Available now in Payment Settings. Read more 👇 https://blockbee.io/…
❤3
🚀 New blockchains live on BlockBee! We’ve added Monad and Linea support. 🔹 Monad: MON, USDT0, USDC 🔹 Linea: ETH, USDT, USDC Read more 👇 https://blockbee.io/blog/post/blockbee-adds-support-for-monad-and-linea-blockchains Faster payments. More choice. Same platform.
🔥2❤1
Photo, posted without a caption
❤1🔥1
New Feature: Dynamic Output Addresses Are Live Starting now, payment requests that rely on your dashboard configured address will automatically use the latest address you have set at processing time. This applies to: • API requests without an address parameter • Checkout • Subscriptions • Payment Links • Storefront API requests that include an explicit address stay fixed as before. 🔎 Important: • Requests c…
New Release: BlockBee Odoo Plugin 1.3.0 Our Odoo plugin has just been updated. Version 1.3.0 now supports Odoo 19 and includes updated FIAT currencies plus some codebase improvements. If you are using Odoo for your crypto payments, we recommend updating to this version for better compatibility and performance. If you need help during the upgrade, reach out in support. Read more 👇 https://blockbee.io/blog/post/blo…
❤1
🎉 BlockBee is attending Web Summit 2025! We’re excited to share that BlockBee will be at Web Summit 2025 in Lisbon this November. You’ll be able to meet our team on Tuesday, November 11 at our booth, and learn more about how we’re making crypto payments simple, fast, and secure for businesses. 📍 Booth details will be announced soon. If you’ll be there too, let’s connect! 💬 Message us 📧 Email us at [email protected]…
❤2👍1
BlockBee is the sponsor and official payment processor for the Bitcoin Conference Amsterdam 2025! All Bitcoin Lightning payments at the event will be powered by BlockBee ⚡️⚡️⚡️ 🎟️ We’re also giving you the possibility to win one of 9 tickets to Bitcoin Amsterdam 2025! To enter: 1️⃣ Comment and repost this post: https://x.com/blockbee_io/status/1983477831192481846 2️⃣ Follow @blockbee_io on X/Twitter 🕛 Giveaway e…
❤2
Showing the 12 most recent of 20 posts we hold for @blockbee_news. 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.
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.
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 30 September 2026 — this entry's latest reading, not the date you are reading this.
“BlockBee” (@blockbee_news), 72 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/blockbee_news.
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.