Channel
@DigitalRublesBot
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
54subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002115762043 |
|---|---|
| Type | Channel |
| Username | @DigitalRublesBot |
| Description | Цифровой рубль (CBDC) — это цифровая валюта, выпускаемая Центробанком (ЦБ) РФ. 💸 Она обеспечивает быстрые, безопасные и дешевые транзакции. 🔒 В отличие от криптовалют, цифровой рубль централизован и полностью контролируется ЦБ. |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/DigitalRublesBot |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 11 November 2026 and assigned it the closest of 31 fixed categories, at 66% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @wallet_Ton_BTC_ETF_USDT/161525 Mar 2026, 01:40 UTC | @DigitalRublesBot/291 · this entry25 Mar 2026, 01:40 UTC | 1.00 | under a minute |
| @DigitalRublesBot/292 · this entry9 Apr 2026, 07:20 UTC | @wallet_Ton_BTC_ETF_USDT/16189 Apr 2026, 14:24 UTC | 1.00 | 7.1 hours |
| @wallet_Ton_BTC_ETF_USDT/162118 Jun 2026, 02:40 UTC | @DigitalRublesBot/295 · this entry18 Jun 2026, 02:40 UTC | 1.00 | under a minute |
| @wallet_Ton_BTC_ETF_USDT/162223 Jun 2026, 03:48 UTC | @DigitalRublesBot/296 · this entry23 Jun 2026, 03:48 UTC | 1.00 | under a minute |
| @wallet_Ton_BTC_ETF_USDT/162522 Jul 2026, 06:05 UTC | @DigitalRublesBot/302 · this entry22 Jul 2026, 06:05 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @wallet_Ton_BTC_ETF_USDT | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | @wallet_Ton_BTC_ETF_USDT (4–3) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 15 February 2026 to 4 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @wallet_Ton_BTC_ETF_USDT. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 09:01 | 54 | no change |
| 8 Aug 2026, 17:15 | 54 | first reading |
20 posts held, back to 11 February 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.
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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 👀 | 1 | 50.0% |
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 2 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 2 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 11 February 2026 to 4 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.
🇷🇺 ФСБ хочет обязатьработающие в России криптобиржи и игровые платформы подключить СОРМ — систему оперативно-разыскных мероприятий для удалённого доступа к данным пользователей, трафику и сообщениям.
❤1
🚨 ЦБ описал схему обмена крипты на ценные бумаги 🪙 Криптовалюту, включая USDT и USDC, потенциально можно будет обменивать на российские: ▫️ акции ▫️ облигации ▫️ паи фондов 🔄 Обмен — через брокеров/посредников и депозитарную инфраструктуру. ⚠️ Публично предлагать такие сделки запрещается. #криптовалюта #USDT #USDC #ЦБРФ #инвестиции #крипта
⚖️ Госдума приняла закон о регулировании крипторынка 🇷🇺 Госдума окончательно приняла закон «О цифровых валютах и цифровых правах» — теперь крипторынок в России впервые будут регулировать более системно. 📅 Основные положения начнут действовать 1 сентября 2026 года. 🔹 Что меняется: • появится регулирование криптобирж, брокеров, обменников и депозитариев; • введут требования к участникам рынка и лицензии для них; • и…
В России хотят официально открыть доступ к USDT и USDC — с 1 сентября 2026 года квалифицированные инвесторы смогут покупать их через российскую инфраструктуру. При этом стейблкоины предлагают юридически считать не криптовалютой, а иностранными цифровыми инструментами — из-за обязательства эмитентов погашать токены.
Стейблкоины быстрее SWIFT, а крипта — уже внутри правовой системы: новая логика регулирования РФ Сегодняшняя логика регулирования крипты в России становится всё более прозрачной: если государство прописывает детальные правила игры, значит, её не вычёркивают, а встраивают в финансовую систему. Да, внутри страны по-прежнему действует жёсткий запрет на расчёты в криптовалютах. Но параллельно ЦБ выносит на обсуждение д…
Крипта выходит из тени. А тень переходит под контроль ЦБ Купить криптовалюту в России через легальных посредников станет проще, а вот анонимность в таких операциях не предусмотрена. Законопроект о регулировании крипторынка уже прошёл первое чтение в Госдуме. После принятия документа с 1 июля граждане и компании смогут покупать криптовалюту через лицензированных посредников: обменники из реестра ЦБ, брокеров и довери…
⚖️ Цифровой рубль получит платформу коммерческих смарт-контрактов 🏦 ЦБ рассматривает создание отдельного сервиса в инфраструктуре цифрового рубля — платформы коммерческих смарт-контрактов (ПКСК). 🤖 Что это даст: ✅ Компании смогут создавать собственные «умные контракты» ✅ Клиенты смогут выбирать новые цифровые сервисы ✅ Сделки будут автоматически выполняться при наступлении заданных условий 🔹 Сейчас смарт-контракт…
🇷🇺 Криптовалютное регулирование в России: больше свободы, но больше контроля ⚖️ Во втором чтении законопроект о криптовалютах стал мягче: ✅ P2P-обмен между физическими лицами фактически остаётся в правовом поле ✅ Небольшие обменные операции могут вывести из-под жёсткого контроля ✅ Иностранные токены и стейблкоины получают отдельное место в системе регулирования 🔍 Но вместе с послаблениями усиливается надзор: ⏳ Для кр…
🚀 Россия готовит особый режим обращения криптовалюты в условиях санкций В законопроект о цифровой валюте и цифровых правах внесли новую норму: правительство сможет устанавливать особый режим обращения цифровых валют в отдельных случаях. 📌 Поправки расширяют полномочия правительства и Центрального банка для быстрого принятия решений, связанных с защитой интересов страны. Также законопроект уточняет правила работы крип…
👀1
🇨🇳 Китай создаёт единую систему для расчётов в цифровом юане (e-CNY), чтобы ускорить его использование за пределами страны — по сути, Пекин готовит инфраструктуру для глобального продвижения своего цифрового аналога наличных.
В конце февраля, руководство проекта A7A5 выступило на форуме FINCORE и представило ключевые показатели рублёвого стейблкойна. Основные тезисы из выступления: - А7А5 занимает до 10% расчетов во внешней торговле РФ - А7А5 покрыл 44% сегмента недолларовых стейблкойнов и стал крупнейшим участником этого рынка - капитализация состаляет свыше $535 млн. - привязка 1:1 к рублю - развёрнут в сетях Tron и Ethereum (как USDT)…
Стейблкоины активно вытесняют банковскую инфраструктуру: в феврале 2026 их месячный оборот впервые превысил ACH — систему банковских безналичных переводов в США — $7.2 трлн против $6.8 трлн.
Showing the 12 most recent of 20 posts we hold for @DigitalRublesBot. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Цифровой Рубль CBDC, Центробанк ЦБ, Стейблкоины, Криптовалюта Платежная система.” (@DigitalRublesBot), 54 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/DigitalRublesBot.
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.