Channel
@NovostiNft
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
4,057subscribers
+312 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001117163487 |
|---|---|
| Type | Channel |
| Username | @NovostiNft |
| Created | Between 1 February 2017 and 31 October 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/NovostiNft |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 44% 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.
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 word for word on 2 other registered channels. They sit inside a group of 6 channels that share the same post bodies with each other. 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 |
|---|---|---|---|
| @NFTNovosti/155415 Jun 2026, 07:38 UTC | @NovostiNft/1285 · this entry15 Jun 2026, 12:12 UTC | 1.00 | 4.6 hours |
| @NFTNovosti/15583 Jul 2026, 06:45 UTC | @NovostiNft/1291 · this entry3 Jul 2026, 06:45 UTC | 1.00 | under a minute |
| @NFTNovosti/156420 Jul 2026, 14:05 UTC | @NovostiNft/1297 · this entry20 Jul 2026, 14:06 UTC | 1.00 | under a minute |
| @NovostiNft/1298 · this entry23 Jul 2026, 04:05 UTC | @NFTNovosti/156523 Jul 2026, 04:05 UTC | 1.00 | under a minute |
| @NFTNovosti/156630 Jul 2026, 06:18 UTC | @NovostiNft/1299 · this entry30 Jul 2026, 06:18 UTC | 1.00 | under a minute |
| @NovostiNft/1300 · this entry31 Jul 2026, 05:41 UTC | @NFTNovosti/156731 Jul 2026, 05:41 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @NFTNovosti | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | @NFTNovosti (4–2) |
| @AnnouncementsIDO | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–1) |
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 5 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 14 comparable posts for this entry, running 29 May 2026 to 31 July 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.
Across the whole group of 6, the earliest publisher we hold is @tokensal. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 7 August 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’s posts match, word for word or near enough, posts on 5 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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 |
|---|---|---|
| 2 Sept 2026, 07:35 | 4,057 | -134 |
| 30 Aug 2026, 08:25 | 4,191 | -43 |
| 27 Aug 2026, 03:45 | 4,234 | +538 |
| 23 Aug 2026, 19:09 | 3,696 | -4 |
| 20 Aug 2026, 01:27 | 3,700 | -7 |
| 16 Aug 2026, 17:59 | 3,707 | -11 |
| 13 Aug 2026, 04:57 | 3,718 | -17 |
| 10 Aug 2026, 00:01 | 3,735 | -10 |
| 7 Aug 2026, 04:15 | 3,745 | no change |
| 7 Aug 2026, 04:09 | 3,745 | first reading |
20 posts held, back to 28 May 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 4 pages 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Solana Pay интегрируют в южнокорейскую платежную сеть KSNET KSNET – один из крупнейших платежных операторов страны. Компания обслуживает более 330,000 торговых точек и ежемесячно проводит платежи на $4b. В рамках партнерского соглашения продавцам из сети KSNET хотят открыть доступ к платежам на Solana.
👍 Claude Mythos ослабила постквантовый алгоритм HAWK за 60 часов AI нашёл скрытую математическую симметрию: сложность восстановления секретного ключа для тестовой HAWK-256 упала, ключ удалось получить за несколько часов на одном сервере. Более защищённые HAWK-512 и HAWK-1024 пока практически недоступны для взлома, хотя их расчётная надёжность тоже снизилась. HAWK нигде не используется, AES-128 не взломан, BTC и ET…
Pump.fun запускает режим BOOST, новый механизм, который автоматически преобразует "мертвую ликвидность" в выкуп токенов и их сжигание. Цель данного механизма - укрепить новые мемкоины после их миграции с помощью рециклинга ликвидности.
FTX проведет пятый раунд выплат кредиторам 31 июля FTX начнет пятый этап компенсаций кредиторам. Выплаты получат пользователи, которые выполнили все необходимые требования до 16 июня. С момента запуска программы биржа уже вернула клиентам более $10 млрд за четыре предыдущих раунда. После новой выплаты общий объем компенсаций превысит $10,1 млрд. По данным одного из кредиторов FTX Сунила Кавури, в пятом раунде выпл…
Tradable планирует вывести активы частного кредитования на сумму до 1 млрд долларов на Stellar.
Тысячи ИИ-агентов провели стресс-тест блокчейнов с квантовой защитой. По итогам тестирования Starknet выделился среди остальных сетей. Независимые исследования продолжают приходить к одному и тому же выводу: Starknet обладает уникальными возможностями, чтобы стать первым блокчейном с полной (end-to-end) защитой от квантовых компьютеров.
Bitmine Тома Ли приобрела $50 миллионов в Ethereum. Теперь общий объём активов Bitmine составляет 55.77 миллиона $ETH на сумму $10.2 миллиардов.
Гонконг теперь предлагает 0% налог на прирост капитала при торговле криптовалютой биткоин.
Circle (эмитент стейблкоина #USDC) получила лицензию банка в США
Elfin Kingdom ликвидируется - ещё один GameFi проект закрывается Инвесторам пришли письма от ликвидаторов: компания официально вошла в процедуру ликвидации 18 июня. Кредиторам предложено подать претензии. В своё время проект собрал $9,3 млн от Binance Labs, Jump Trading, Alameda Research, Polygon и других - на волне GameFi-хайпа 2021–2022 годов.
NEAR Protocol планирует переход к фиксированной эмиссии токенов
✋ Venice AI привлек $65 млн от Dragonfly, Coinbase Ventures и North Island Ventures Стартап привлёк $65 млн в раунде Series A при оценке в $1 млрд, став «единорогом» всего за два года после запуска.
Showing the 12 most recent of 20 posts we hold for @NovostiNft. 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.
Named by 3 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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“NFT Новости | Минт NFT🐋” (@NovostiNft), 4,057 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/NovostiNft.
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.