Купите аппаратный кошелёк, включите двухфакторку, сид-фразу храните на бумаге в сейфе. Тогда вы потеряете деньги исключительно на трейдинге.
😁112👍14🤯5🤝4🍾2

Channel
@don_invest
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
37,447subscribers
-1,990 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001423540718 |
|---|---|
| Type | Channel |
| Username | @don_invest |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 68 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/don_invest |
Crypto & trading — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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. 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 |
|---|---|---|---|
| @don_invest/5334 · this entry2 Nov 2026, 21:16 UTC | @WEB3_AGGREGATOR/4261762 Nov 2026, 21:16 UTC | 1.00 | under a minute |
| @don_invest/5335 · this entry4 Nov 2026, 13:01 UTC | @WEB3_AGGREGATOR/4262474 Nov 2026, 13:02 UTC | 1.00 | under a minute |
| @don_invest/5338 · this entry8 Nov 2026, 22:08 UTC | @WEB3_AGGREGATOR/4264568 Nov 2026, 22:08 UTC | 1.00 | under a minute |
| @don_invest/5341 · this entry10 Nov 2026, 17:51 UTC | @WEB3_AGGREGATOR/42655310 Nov 2026, 17:51 UTC | 1.00 | under a minute |
| @don_invest/5343 · this entry13 Nov 2026, 15:02 UTC | @WEB3_AGGREGATOR/42672113 Nov 2026, 15:02 UTC | 1.00 | under a minute |
| @don_invest/5347 · this entry16 Nov 2026, 15:28 UTC | @WEB3_AGGREGATOR/42685016 Nov 2026, 15:29 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @WEB3_AGGREGATOR | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6–0) |
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 0 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 58 comparable posts for this entry, running 14 July 2026 to 16 November 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.
Recorded under the key clone_source, last confirmed 17 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 14:45 | 37,447 | +10 |
| 14 Nov 2026, 09:19 | 37,437 | -2 |
| 11 Nov 2026, 11:56 | 37,439 | +26 |
| 9 Nov 2026, 17:14 | 37,413 | -32 |
| 8 Nov 2026, 08:49 | 37,445 | -34 |
| 7 Nov 2026, 06:27 | 37,479 | -17 |
| 6 Nov 2026, 06:17 | 37,496 | -7 |
| 5 Nov 2026, 08:11 | 37,503 | -33 |
| 4 Nov 2026, 05:41 | 37,536 | -19 |
| 3 Nov 2026, 07:10 | 37,555 | -27 |
| 2 Nov 2026, 05:27 | 37,582 | -27 |
| 1 Nov 2026, 05:39 | 37,609 | -58 |
| 31 Oct 2026, 03:04 | 37,667 | -35 |
| 30 Oct 2026, 06:08 | 37,702 | -148 |
| 29 Oct 2026, 07:36 | 37,850 | -31 |
| 28 Oct 2026, 08:57 | 37,881 | -16 |
| 27 Oct 2026, 08:14 | 37,897 | -9 |
| 26 Oct 2026, 10:08 | 37,906 | -16 |
| 25 Oct 2026, 13:16 | 37,922 | -16 |
| 24 Oct 2026, 15:39 | 37,938 | first reading |
74 posts held, back to 14 July 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 194 pages of 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 16 November 2026 |
|---|---|
| Posts held | 74 (14 July 2026 – 16 November 2026) |
| Views total | 193,500 |
| Reactions total | 1,552 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 11:25 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 3 videos 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.
5,597 reactions across 74 posts, in 12 distinct kinds. The most used accounts for 49.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 2,783 | 49.7% | |
| 👍 | 1,450 | 25.9% | |
| 🔥 | 418 | 7.47% | |
| ❤ | 296 | 5.29% | |
| 😢 | 125 | 2.23% | |
| 🤔 | 120 | 2.14% | |
| 🤝 | 117 | 2.09% | |
| 🤯 | 117 | 2.09% | |
| 🍾 | 60 | 1.07% | |
| ☃ | 54 | 0.965% | |
| 🐳 | 37 | 0.661% | |
| 🙏 | 20 | 0.357% |
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 74 of the 74 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 5,597 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 74 most recent posts we hold, published 14 July 2026 to 16 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @don_invest. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 74 most recent posts we hold for this entry, published 14 July 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 6 of 24 posts held from the last 30 days (25.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).
Купите аппаратный кошелёк, включите двухфакторку, сид-фразу храните на бумаге в сейфе. Тогда вы потеряете деньги исключительно на трейдинге.
😁112👍14🤯5🤝4🍾2
Что произошло: С Lighter вывели 10.4 млн$ через паблик-пул, который хакер сам создал от имени жертвы. Контракт никто не ломал, хватило API-ключей одного участника с двумя бот-аккаунтами Ключ на Lighter по докам не выводит деньги на чужой адрес, но переводит их между своими аккаунтами, а пул считается своим, хотя доли в нём покупает кто угодно. Хакер взял в таком пуле 99.99% долей за 10k$, перегнал туда с аккаунта же…
👍19😁7❤1🤯1
Пошёл слух, что Lighter взломали #LIT
😁33😢11🤯7
В крипто-твиттере сегодня собирает лайки призыв закрыть рынки. 17 лет гордились тем, что их нельзя выключить
😁118🍾10❤5🔥3☃1
Возможно сейчас стоит немного пересмотреть безопасность своей крипты!🔐 За последние несколько недель произошло несколько взломов и я, почему-то, склонен думать, что это не предел. Все началось в 20-х числах октября, когда крупную уязвимость обнаружили в Railway. В открытый доступ или в руки атакующих потенциально попали API-ключи, токены доступа к сервисам, приватные ключи реестров и пароли от баз данных (PostgreSQL…
👍82😁10🤝6🐳5
🎁 На Predict кто лудил, можно чекать дроп predict.fun/points/airdrop Клейм откроется 18 ноября. До этого времение надо выбрать, либо забираете 35% сразу, либо 100% равными частями ежемесячно в течение года. ❕Если ничего не выбрать, автоматически получаете второй вариант.
👍23😁6🍾4🤝4
Увидел, как самого крупного сэндвич-бота эфира jaredfromsubway раздели на сумму до 15 млн$, и решил разобраться, реально ли сейчас зайти в эту тему самому Бот делал около 70% всех сэндвичей в эфире, и в июне его поймали на фейковом рынке. Атакующий завел 66 поддельных токенов с пулами, давал боту выигрывать по мелочи, пока тот раздавал аппрувы, а потом вынес всё одной транзой Сэндвич это когда бот покупает прямо пе…
👍30😁19❤9🐳3
Продолжается история. Срочно обновите iOS, удалите не офф приложения, крадут деньги уже и с актуальных версий. Каждый день вижу сообщения от пострадавших.
❤23🤯16😁8
Глава NVIDIA изменил жене с китайской шпионкой. Началось расследование, — NYT Миллиардер Дженсен Хуанг признался в измене жене после 40 лет брака. Его любовницей оказалась Элис Хуанг. За два года компания женщины закупила чипов Nvidia на $4,8 млрд. "Я был неверен своей жене. Мои поступки причинили боль ей и нашим детям. Этому нет оправдания", – написал Хуанг сотрудникам Nvidia. Совет директоров компании начал рассле…
😁80🤔10👍4❤3☃2
Трамп: операция «Iron Gate» против Ирана «в полной силе», плюс «величайшая морская блокада в истории». —— Ранее: Киты на Hyperliquid нарастили рекордные SHORT-позиции по Биткоину – максимум с октября 2025 года! Объем: ~$900m
👍32☃8🤝6😁4❤1
Проверьте балансы на МЕXC, лучше вывести всё оттуда.
🤔30😁20👍12
Posted without readable text
😁40👍15🤝4☃3❤1
Showing the 12 most recent of 74 posts we hold for @don_invest. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@don_invest edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Named by 8 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 31 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 98 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Don | Invest Blog” (@don_invest), 37,447 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/don_invest.
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.