Telegram RegisterThe public register of Telegram
Telegram profile photo for Security21

Channel

Security21

@bitcoin21sec

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

100subscribers

+0 since we began measuring on 4 November 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004335651901
TypeChannel
Username@bitcoin21sec
CreatedBetween 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 November 2026
Last confirmed live4 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/bitcoin21sec

Growth

1004 Nov 2026, 01:22 — 100 subscribers4 Nov 2026, 19:31 — 100 subscribers4 Nov 2026, 01:224 Nov 2026, 19:31
2 measurements taken within a single day. 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 99–101 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 19:31100no change
4 Nov 2026, 01:22100first reading

Engagement

20 posts held, back to 30 October 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
61.5%
avg views ÷ 100 subscribers
Avg views / post
61.5
20 posts measured
Reaction rate
1.90%
reactions ÷ views · ER floor
Posts in window
20
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 16 of 20 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 3 November 2026
Posts held20 (30 October 2026 – 3 November 2026)
Views total1,230
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 01:22 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

19 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 47.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😱947.4%
🥰736.8%
❤210.5%
👍15.26%

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 16 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 19 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 30 October 2026 to 3 November 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

Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 18:11 UTC32 views1 reactionsread 4 November 2026

Liana 16.0: выпущено исправление RBF-атаки со стороны вредоносных Electrum-серверов Вендор объявил релиз Liana v16.0 и среди изменений указал исправление RBF-атаки, которую мог провести вредоносный Electrum-сервер. Подробности дефекта вендор вынес в блог-пост, ссылка в посте; механика атаки в самом объявлении не раскрыта. Релиз также приносит зашифрованные резервные копии дескриптора (BIP138), Taproot по умолчанию, …

😱1

3 Nov 2026, 16:01 UTC41 views1 reactionsread 4 November 2026

Blink 3.0.46: смена email/телефона и отключение 2FA теперь требуют кода аутентификатора, исправлены блокировка приложения и PIN В выпуске Blink 3.0.46 добавление email или телефона и отключение двухфакторной аутентификации теперь требуют кода аутентификатора, а сама 2FA предлагается по мере роста баланса и обязательна выше заданной суммы (альтернатива — переход в самостоятельное хранение). Релиз содержит исправления…

😱1

3 Nov 2026, 01:01 UTC55 views1 reactionsread 4 November 2026

Nutshell 0.22.0: выпущены исправления безопасности в учёте минта, аутентификации и работе с seed Релиз Cashu Nutshell 0.22.0 содержит, по словам выпуска, исправления и усиление безопасности в учёте минта, аутентификации, обработке seed, логировании и валидации запросов; подробности дефектов и их эксплуатируемость в заметках не раскрыты. Выпуск также несёт миграции базы данных минта, поддержку BIP-39 seed минта (MINT…

😱1

3 Nov 2026, 00:50 UTC53 views1 reactionsread 4 November 2026

Обновление по инциденту myNode уточнил состав v0.3.52: ещё два CVE и объяснение ошибки на Raspberry Pi По сообщению myNode, релиз v0.3.52 помимо смягчения CVE-2026-98432 включает обновление NodeJS для CVE-2026-111497 и обновление Bitcoin для CVE-2026-117349, а также новые правила файрвола; вендор говорит, что исправления нужны, чтобы предотвратить возможный неавторизованный доступ и управление устройством. На Raspb…

😱1

2 Nov 2026, 16:21 UTC57 viewsread 4 November 2026

Blink Wallet: предрелиз мобильного приложения восстанавливает защиту PIN и экранов с seed-фразой В заметках к предрелизу мобильного Blink заявлены изменения защиты доступа: блокировка приложения теперь сохраняется на всём протяжении вызванного ей выхода из аккаунта, возвращена нарастающая задержка при неверном PIN (продолжает расти и после исчерпания лимита попыток), а экраны с seed-фразой закрыты screen guard по пр…

2 Nov 2026, 14:42 UTC57 viewsread 4 November 2026

BTCPay Server: кражи из горячих кошельков на 2.4.1 и старше — одного обновления недостаточно, вендор советует переезд на чистый сервер 1 ноября 2026 вендор получил сообщения о краже биткоина и лайткоина из горячих кошельков BTCPay Server; по его расследованию атаки были направлены на серверы с версией 2.4.1 (выпуск 23 июля 2026) или старше, а злоумышленники использовали другой способ эксплуатации уязвимости, закрыто…

2 Nov 2026, 04:12 UTC56 viewsread 4 November 2026

BTCPay Server: атака нацелена на инстансы версии 2.4.1 и старше, часть серверов у хостеров отключена автоматически По итогам разбора инцидента команда BTCPay Server сообщает, что найденный вектор атаки нацелен на инстансы версий 2.4.1 (23 июля 2026) и старше; достоверных сообщений о списании средств с горячих кошельков у тех, кто работает на последнем релизе 2.4.7, у вендора нет. Вендор снова призывает держать BTCPa…

2 Nov 2026, 01:22 UTC61 viewsread 4 November 2026

BTCPay Server: злоумышленник входил как администратор на инстансы версий до 2.4.2, способ ещё выясняют Разработчик BTCPay Server сообщает, что на затронутых инстансах злоумышленник смог войти под администратором; как именно — команда всё ещё разбирается. По его словам, сообщения об атаках касаются установок до 2.4.2, а публичные серверы проекта, работающие на 2.4.7, не атаковали. Причина и полный перечень затронутых…

1 Nov 2026, 09:31 UTC64 views2 reactionsread 4 November 2026

umbrelOS 2.0.1 закрывает уязвимость ядра Linux в обработке входящих сетевых соединений Umbrel выпустил umbrelOS 2.0.1 как важное обновление безопасности: на Umbrel Home, Umbrel Pro и других x86-устройствах оно приносит ядро Linux с исправлением недавно раскрытой уязвимости CVE-2026-98432, а на Raspberry Pi, где исправленного ядра пока нет, umbrelOS блокирует сетевой трафик, нужный для её срабатывания. В тот же релиз…

❤1😱1

31 Oct 2026, 20:31 UTC69 views1 reactionsread 4 November 2026

Обновление по инциденту RoboSats v0.8.8-alpha: исправлен XSS в логах ордеров, добавлены проверки выплат у координаторов, старый Android-клиент больше не подключается Релиз закрывает XSS (данные, контролируемые пользователем, экранируются, логи ордеров хранятся как JSON), добавляет координаторам проверку источников наград и выплат покупателю по данным Lightning-ноды с необязательным лимитом выводов, чинит повторное …

😱1

31 Oct 2026, 06:02 UTC70 views2 reactionsread 4 November 2026

Start9 выпустила StartOS 0.4.1 с важными обновлениями безопасности Start9 сообщает, что версия StartOS 0.4.1 опубликована и содержит важные обновления безопасности, и просит обновиться как можно скорее. Характер исправленных проблем в сообщении вендора не назван. Что делать: Если ваш Bitcoin-узел работает на StartOS и эти исправления ещё не установлены — обновитесь до 0.4.1 как можно скорее, как советует Start9; те…

❤1🥰1

31 Oct 2026, 03:01 UTC67 views1 reactionsread 4 November 2026

myNode выпустил v0.3.52 с исправлением CVE-2026-98432 и мерами против MPTCP По сообщению myNode, релиз v0.3.52 закрывает CVE-2026-98432 и содержит другие security-исправления и смягчения: обновление ядра с фиксом для PC-платформ, LND v0.21.6 со смягчением по MPTCP и отключение MPTCP на Raspberry Pi. Детали дефектов в сообщении не раскрыты. Что делать: Если вы держите узел на myNode: обновитесь до v0.3.52 — вендор с…

🥰1

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

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

“Security21” (@bitcoin21sec), 100 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/bitcoin21sec.

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.