Channel
@DoCryptoBred
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Stars · Posts · Polls · Citations · Cite this entry
6,961subscribers
-640 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002659592555 |
|---|---|
| Type | Channel |
| Username | @DoCryptoBred |
| Description | Vault - https://app.hyperliquid.xyz/vaults/0x654016a8c9fcf0c4cb7ed6078aba21f7f399f7b7 BredoStrategySubs (закрытый-дневник+чат) - https://forms.gle/uxoA4SZZeB6nvUGq7 https://app.hyperliquid.xyz/join/BREDOSTRATEGY - рефка HL, спасибо Ex - КриптоБред |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 19 August 2026 |
| On Telegram | t.me/DoCryptoBred |
Crypto & trading — 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 100% 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 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 |
|---|---|---|---|
| @DoCryptoBred/2099 · this entry6 Aug 2026, 16:20 UTC | @black62swan/184336 Aug 2026, 17:41 UTC | 1.00 | 82 minutes |
| @DoCryptoBred/2100 · this entry6 Aug 2026, 16:20 UTC | @black62swan/184346 Aug 2026, 17:41 UTC | 1.00 | 82 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @black62swan | 5 (5/5 hand-verifiable sample passed) | 1.00 | 82 minutes | this entry (5–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 30 comparable posts for this entry, running 3 August 2026 to 7 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.
Across the whole group of 2, the earliest publisher we hold is @DoCryptoBred — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key 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 1 other registered channel, 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 |
|---|---|---|
| 19 Aug 2026, 14:43 | 6,961 | -8 |
| 16 Aug 2026, 16:58 | 6,969 | -268 |
| 12 Aug 2026, 21:54 | 7,237 | -14 |
| 9 Aug 2026, 13:21 | 7,251 | -350 |
| 6 Aug 2026, 03:06 | 7,601 | no change |
| 6 Aug 2026, 02:17 | 7,601 | first reading |
83 posts held, back to 3 August 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 12 pagesof 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. It is computed over the 11 of 83 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 19 August 2026 |
|---|---|
| Posts held | 83 (3 August 2026 – 19 August 2026) |
| Views total | 108,028 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Aug 2026, 03:14 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.
Lifetime counters from Telegram’s own channel header, read 20 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @DoCryptoBred. 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 83 most recent posts we hold for this entry, published 3 August 2026 to 19 August 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.
Nethermind уходит из верификаторов LayerZero в Chainlink Nethermind — core-контрибьютор Ethereum и один из крупнейших сторонних верификаторов LayerZero — объявил 19 августа о сворачивании своих DVN-операций и переходе в сеть Chainlink. Компания становится нод-оператором и технологическим провайдером Chainlink: будет участвовать в обеспечении кросс-чейн протокола CCIP и Data Feeds. Решение объяснено «extensive review…
Фиксирую 10% к Vault позы #Vault
это движение оч классно демонстрирует насколько мелок и не значителен ритейл, хороводом правят хороводоводы, но плюс в том что блокчейнизация и токенизация мира финансов это кажется не миф а реальность, в кратко сроки любые движения предсказывать опасно, но тренд понятен, плюс в этой игре 99% юзеров(не денег) а именно юзеров теряют свои деньги об комиссии и плечи, цикличность заставляет ритейл приходить на хаях и про…
Всё только начинается
Фиксирую 10% к Vault позы #Vault
Фиксирую 5% к Vault позы #Vault
ChainLink единственный токен на встрече в белом доме
Апдейт по Белому дому: встреча в официальном расписании, пресс-пул на ремарках — а prediction markets сняли со списка Встреча вышла из анонимных сорсов в официальное расписание президента: 14:30 ET / 21:30 MSK, «Remarks with Technology Leaders», Roosevelt Room, статус — White House Press Pool. Значит, будут кадры и стенограмма ремарок, а не полностью закрытый формат (ранее источники называли EEOB без прессы). Рядом …
HSBC и Standard Chartered провели первую живую транзакцию на блокчейн-леджере Swift — токенизированные депозиты впервые сработали между банками Сегодня HSBC и Standard Chartered объявили о первой живой кросс-бордер транзакции на blockchain-леджере Swift. Банки обменялись платёжными сообщениями через леджер, обязательства записаны токенизированными депозитами на собственных системах каждого (у HSBC — Tokenised Deposi…
Neuberger-фонд просят в залог на Aave: первый high-yield коллатерал для Horizon 18 августа Securitize и Neuberger Berman запустили токенизированный фонд HINC (high yield корпоративные бонды, CLO-транши, банковские займы; sub-advisor — Neuberger, группа с ~$567 млрд AUM) на Ethereum, Solana, Avalanche и Sui. В тот же день Securitize опубликовали ARFC в governance Aave: онбординг HINC как supply-only залога на Aave Ho…
VanEck ChainCheck: горят 8 из 12 сигналов капитуляции BTC — но внутри 6 месяцев эджа это исторически не даёт В свежем Bitcoin ChainCheck (18.08, данные на 12.08) у VanEck активны 8 из 12 сигналов капитуляции, а все 12 заходили в экстремальную зону за последние 3 месяца. Рекорды: put/call premium ratio 2,30 — исторический максимум (99-й перцентиль при норме 0,71); в прибыли лишь 51,9% supply (6-й перцентиль); сложнос…
Вайоминг перевёл государственный стейблкоин FRNT с LayerZero на Chainlink CCIP — «исход» на ~$15 млрд получил первый госактив Wyoming Stable Token Commission объявила 18 августа: Frontier Stable Token (FRNT) полностью мигрировал на Chainlink CCIP — эксклюзивная кроссчейн-инфраструктура по многолетнему контракту. LayerZero-имплементацию, на которой токен был задеплоен изначально (стандарт OFT), деприкейтят после «дет…
Showing the 12 most recent of 83 posts we hold for @DoCryptoBred. 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
сегодня 15-16 МСК отчёт Strategy по BTC...что думаете сделали? напомню уже 7 полных недель без покупок BTC
Shares as published. No per-option vote count is published by Telegram, so none is shown.
через 1-2 часа(15-16 МСК) отчёт Strategy по BTC...что думаете сделали? напомню уже 6 полных недель без покупок BTC
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 83 most recent posts we hold, published 3 August 2026 to 19 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 19,283 of 1,584,142entries 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.
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 13 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.
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 19 August 2026 — this entry's latest reading, not the date you are reading this.
“BredoStrategy” (@DoCryptoBred), 6,961 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/DoCryptoBred.
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.