AML проверка одного из адресов, так что возможно бинанс не принял крипту.
🔥4

Channel
@gfoundinshit
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
2,327subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001139417793 |
|---|---|
| Type | Channel |
| Username | @gfoundinshit |
| Created | Between 1 June 2017 and 31 August 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 12 August 2026 |
| On Telegram | t.me/gfoundinshit |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 03:54 | 2,327 | -1 |
| 6 Aug 2026, 05:50 | 2,328 | no change |
| 6 Aug 2026, 04:01 | 2,328 | first reading |
16 posts held, back to 5 May 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 2 pagesof 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 16 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.
60 reactions across 10 posts, in 2 distinct kinds. The most used accounts for 55.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 33 | 55.0% | |
| 👍 | 27 | 45.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 10 of the 16 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 60reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 5 May 2025 to 29 June 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.
AML проверка одного из адресов, так что возможно бинанс не принял крипту.
🔥4
Крипта с Grinex полетела прямиком на Binance! 😀 С одного из адресов, куда 26 июня раскидали краденые активы, хакер начал слив. Он кинул TRON на три уже прогретых и активных адреса. За сутки до этого на них завели чистые USDT, а потом с них TRON улетел на Binance. Первые тестовые ~45k$ успешно тю-тю. Если схема окажется 100% рабочей, то скоро начнёт сливать основное.
👍2
Зашевелилась крипта, украденная у биржи Grinex! С кошельков, куда в апреле вывели ~13-15 млн долларов в украденных активах, начались активные движения.
🔥8
4 июля 2025 года, когда Америка праздновала День независимости, в сети Биткойн произошло нечто необъяснимое. Восемь «спящих» кошельков, каждый с ровно 10 000 BTC (в сумме — 80 000 BTC или $8,6 млрд), активировались после 14 лет молчания. Но самое странное — за несколько дней до списания все проснувшиеся кошельки получили маленькие входящие переводы с помощью транзакций, в поле OP_RETURN которых содержались загадочные…
👍12🔥5
Крипто-регуляторы жмут, а криптоманы оживают! 😴 Из-за закручивания гаек народ снова вспомнил про анонимные монетки, и Monero (XMR) рванул вверх. Рост, похоже, продолжится, несмотря на попытки Европы забанить приватную крипту. На надо же,как то,взрослым дядям прятать свои грязные денюжки. 🤔 ➡️Но не всё так радужно: анонимность XMR - не панацея. Помним, как в 2016 раскопали транзы Monero Лихтенштейна по делу Bitfine…
⚠️В сети всплыла инфа: правоохранители нарыли кошельки, которые, принадлежат партнеру Владислава Бакальчука Сергею Ануфриеву. Эти суммы совпадают с озвученными в обвинениях в адрес Бакальчука и Ануфриева, которые через стройки складов Wildberries похитили несколько десятков миллиардов рублей и вывели их на личные счета. На них припарковано 5142 BTC - это, $564.946M! ➡️Два кошелька зарядили битками в 2022, а третий,…
🔥9
Ещё 650 BTC из кошелька, где в 2013 собрали 2343 BTC ($221.7M), прилетели на тот же депозитный адрес Gemini, что светился 9 мая. 🧐 Остальные 1693 монетки BTC-e раскидали по разным кошелькам - ждут своей очереди, но, чую, долго не пролежат! #BTC_E
👍2
🧐 Ох, вот это заруба с BTC-e битками! 🧐 🟢Все знают: на бирже тебе дают постоянный адрес для пополнений, пока сам не сменишь. Вот я и покопался в том адресе Gemini, куда зашли эти мутные монетки. 🤔 И чё? Нашёл всего три пополнения до сегодня: 20, 10 и 60 BTC. Маловато, но пахнет жареным! 👀 Погрузился глубже - все три транзы ведут к кошельку. И тут понеслось: транзакции - сплошь CoinJoin, как в той движухе с 2343 B…
👍6
Ну и хрена мелочиться?🤔 Все оставшиеся 1077 BTC из старого клада BTC-e улетели прямиком на Gemini.⚠️ Вместе с тем одним BTC, что ушёл раньше. Тест, похоже, пройден с жирным плюсом! #BTC_E
👍1
Битки BTC-E пошли на вывод! 👀 Час назад из 1078 BTC ($102.54M), что в 2012 слили с биржи, 1 BTC шмыгнул прямиком на Gemini. 😉 Видимо для теста! Проверка так сказать биржи , тормознут или нет. Остальные 1077 улетели на новый кошелёк (bc1qnxl5y52gq26ntk2wawn6me25cg9pfvlq3g36j7). #BTC_E
https://t.me/PrimeBlock/10364 Данные из архива тут.
Как раз, Black mirror, накидал много интересного чтива на вечер, касаемо Малафеева, Винника, BTC-e, WEX и иже с ними. https://t.me/black8mirror/10820
Showing the 12 most recent of 16 posts we hold for @gfoundinshit. 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.
Citation-graph rank — 296,840 of 1,189,255entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 2 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.
@gfoundinshit named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“Goldfoundinshit ТМ” (@gfoundinshit), 2,327 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/gfoundinshit.
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.