Channel
@generalbytes
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
429subscribers
-10 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001234297544 |
|---|---|
| Type | Channel |
| Username | @generalbytes |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/generalbytes |
Hacking & security — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 23:45 | 429 | -3 |
| 26 Oct 2026, 05:37 | 432 | +1 |
| 12 Oct 2026, 16:51 | 431 | -1 |
| 2 Oct 2026, 23:36 | 432 | +1 |
| 18 Sept 2026, 11:16 | 431 | -3 |
| 10 Sept 2026, 14:37 | 434 | -1 |
| 2 Sept 2026, 00:34 | 435 | -2 |
| 20 Aug 2026, 12:56 | 437 | -3 |
| 12 Aug 2026, 22:36 | 440 | +1 |
| 6 Aug 2026, 19:18 | 439 | no change |
| 6 Aug 2026, 05:15 | 439 | first reading |
20 posts held, back to 12 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 30 July 2026. An engagement rate over an empty window would be a number about nothing.
129 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 46.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 60 | 46.5% | |
| ❤ | 34 | 26.4% | |
| 🔥 | 15 | 11.6% | |
| 🎉 | 10 | 7.75% | |
| 👏 | 10 | 7.75% |
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 18 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 129 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 12 March 2025 to 30 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.
🚨Dear Customers and Operators, Based on the post-incident investigation results we recommend you to upgrade to the newest release made available today. Patch releases are: 20250901.49, 20251001.62, 20260201.35, 20260401.26, 20260601.25. They include additional hardening of master service which we created as a one week-long follow up after the quick emergency fix delivered previous week. Please read the information be…
👍4
🚨Dear Customers and Operators, There is a security incident that needs your immediate attention. Please read the information bellow as we need you to protect yourself and stay informed: https://generalbytes.atlassian.net/wiki/x/AQCSKwE
👍4❤2🎉1
New version 20260601 has been released today. More details can be found here. Release 20260601 contains high number of bug fixes and improvements while adding one optional but important feature - a support for S3 storage that enables operators to save costs on the cloud storage for storing image data such as identity images.
❤4👍4
📢 Product release: Printer Upgrade Kit for BATMTwo and BATMTwoPro Dear Operators, we have released a new Printer Upgrade Kit that adds a paper-receipt printer to existing BATMTwo and BATMTwoPro terminals. The kit was developed in response to changing legislation — notably in the US — where a printed paper receipt is increasingly required and SMS or e-mail confirmation is no longer accepted. As many units were sold…
❤3🔥2👍1
New version 20260401 has been released today. More details can be found here. Release 20260401 (apart from bug fixes and improvements) notably contains support for: 1. Dynamic Profit that allows operators to set different fees for end customers based on how much cash is being inserted into the machine. Different fees can be also set based on combination of direction(BUY/SELL) and payment method. 2. BATMSeven and BA…
👏4❤3👍3
Dear Operators, Due to the latest Litecoin core software update the 3rd party library Litecoinj used in our products stopped being compatible with the current Litecoin network protocol. Problem is manifested by master service being stopped in 30 minutes after start. In this article you will find root cause, workaround and solution.
Dear Operators, If you are operating in the United States, you may be interested in an initiative led by Merle, Brown & Nakamura, P.C., represented by Scott McClain. At GENERAL BYTES, we believe that governments should focus on regulation rather than outright bans. To ensure the industry's voice is heard, we encourage you to contact Mr. Scott McClain [email protected] to join this collective effort. A Message fr…
❤4
Dear Operators, Please note that effective from 1st of May 2026 GB will not be releasing patch releases for versions that are marked as End Of Life.
New version 20260201 has been released today. More details can be found here. Release 20260201 (apart from bug fixes and improvements) notably contains support for: 1. External payments. A customer can now choose at the ATM to pay for coins with an external payment provider (instead of cash). An external payment provider can be connected to CAS via Open Extensions, and the customer (at the ATM) is redirected to the …
👍8❤2
New version 20251001 has been released today. More details can be found here. Release 20251001 apart from bug fixes and improvements notably contains support for: 1. New CAS UI - In 2024 we rewritten CAS UI into ReactJS. This year we redesigned tables and widgets to be up to date with today’s UX standard. In the same time we are keeping an old CAS UI also available for those who want to stay a bit longer using legac…
❤6
New patch releases 20250901.35, 20250601.48, 20250301.54 are now available. In these patch releases only bitcoinj library has been upgraded from 0.16.3 to version 0.16.5. If you need any further assistance please contact our [email protected]
👍6❤4🔥1
Dear Operators, Please be aware of current production issue: Bitcoin block 928896, mined on 2025-12-21 22:28:26 UTC, was the first block to require more than 96 bits to store chain work value. The third party library /batm/app/master/lib/bitcoinj-core-0.16.3.jar that CAS utilizes uses only 12 bytes(96 bits) to store the chain work value. We are currently working on new CAS software patches for versions 20250301, 2025…
👍5👏3🔥1
Showing the 12 most recent of 20 posts we hold for @generalbytes. 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.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“generalbytes.com” (@generalbytes), 429 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/generalbytes.
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.