Channel
@bitok_global
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
283subscribers
+11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001568739176 |
|---|---|
| Type | Channel |
| Username | @bitok_global |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/bitok_global |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 12:37 | 283 | +13 |
| 22 Aug 2026, 17:45 | 270 | +1 |
| 14 Aug 2026, 14:57 | 269 | -3 |
| 6 Aug 2026, 23:33 | 272 | no change |
| 6 Aug 2026, 03:32 | 272 | first reading |
17 posts held, back to 3 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 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 17 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
283 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 39.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 111 | 39.2% | |
| 🔥 | 90 | 31.8% | |
| 👍 | 82 | 29.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 17 of the 17 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 283 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 3 July 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.
🔞 From 500 Wallets to $114M: Three More Waves of COLDCARD Attacks In our previous investigation, we covered the first wave of mass BTC theft, where 594.477 BTC was drained from 500 Bitcoin wallets. BitOK analysts traced the complete flow of the stolen funds. Further investigation revealed that this was not an isolated incident. BitOK identified three additional waves of coordinated wallet drains that took place be…
❤6👍5🔥4
💵 500 Wallets Drained in 15 Minutes: Where Did 594 BTC Go? On July 30, attackers drained 594.477 BTC from 500 Bitcoin wallets in a coordinated operation. The funds were first consolidated into a single address before 562.019 BTC were moved to a second wallet. BitOK traced the entire flow of funds. ⚙️ How the Funds Were Moved All 500 transactions were executed within just 15 minutes. BitOK analysts identified seve…
🔥6❤5👍4
✔️ BitOK's "Clean or Dirty" KYT Trainer is now available on Telegram We've launched a Telegram mini-game where you make KYT decisions under time pressure. 🧠 Every transaction gives you 2–6 seconds to decide whether to allow or block it. Run out of time, and the transaction is processed automatically. There are 9 shifts in total, each introducing new screening rules and a faster transaction flow. Cases include exch…
🔥6❤5👍3
🐾 "Sign here." That became the most expensive lesson in Triple-A's history Between July 24–25, an attacker drained more than $9M from wallets publicly linked to the project. This wasn't a smart contract exploit. It wasn't a blockchain hack. Every transaction was valid because it was signed with legitimate keys. The attacker didn't break the protocol — they compromised the wallet signing infrastructure. The BitOK …
👍5🔥5❤3
🔞 Why is July 23 being called crypto's unofficial Hacker Day? Let's break it down with BitOK On July 23, the crypto industry was hit by three major exploits within just a few hours. B² Network, Verus Bridge, and AFX Bridge were all compromised, with combined losses exceeding $35 million. What makes these incidents stand out is that none of them relied on a conventional hack. Each exploit followed a different att…
❤6👍4🔥4
🚀 AML has become one of the fastest-growing areas of the crypto industry Just a few years ago, AML was a specialized discipline within the digital asset market. Today, it is a core part of the industry’s infrastructure. 💻 As the market continues to develop, demand is growing for tools that help organizations assess crypto risk and meet evolving compliance requirements. BitOK is growing too, and we are expanding ou…
❤7🔥6👍5
🧠 Coincidence or a new trend? Breaking down the B² Network exploit Another multi-million dollar exploit where the root cause wasn't a traditional smart contract vulnerability. In the B² Network incident, the attacker gained control of the staking contract's upgrade authority. Using the legitimate upgrade mechanism, they replaced the contract implementation, allowing B2 to be withdrawn to an attacker-controlled addr…
❤8🔥6👍5
📊 It has been a rough week for cross-chain bridges First, AFX Bridge lost $24M without a smart contract vulnerability. Then came Verus, where an attacker drained another $7.5M by submitting a proof that the bridge accepted as valid, even though no corresponding assets had actually been locked on the other chain. 🧠 Different attacks, different attack vectors. But they point to the same trend: multi-million dollar lo…
❤7🔥5👍4
🐾 An Attack Without an Exploit: How AFX Bridge Lost $24M On July 22, $24.15 million in USDC was withdrawn from AFX Bridge. No smart contract vulnerability was involved. Instead, the attacker obtained 5 of the 7 validator signatures required to authorize withdrawals, and the protocol approved the transactions as legitimate. 📊 The funds moved within minutes: • nearly all liquidity was drained in 3.5 minutes; • the …
❤6🔥4👍3
🔞 $1M Stolen Without Hacking: How 42DAO Was Exploited On July 22, Balance Coin (BLC), the stablecoin of the 42DAO ecosystem, lost its dollar peg and crashed by more than 99% within hours. No private keys were stolen. No smart contract was exploited. The weakness was in the protocol's economic logic. A manipulated BTCB price was accepted without sanity checks. The protocol triggered liquidations and sold collateral…
❤7👍4🔥4
🐾 One transaction. $1.65M drained. How the Allbridge Core attacker laundered the funds On July 19–20, the attacker used a Kamino flash loan to execute a series of transactions against the Allbridge Core liquidity pool on Solana. By manipulating the pool's internal accounting and pricing logic, the attacker withdrew more assets than should have been available. The flash loan was repaid within the same transaction, w…
❤7👍6🔥4
🤑 $290M in Seized Crypto. Two Days. One Route to Coinbase Prime On July 13–14, the U.S. government transferred a large batch of seized digital assets into the Coinbase Prime infrastructure. 🔍 BitOK analysts reconstructed the complete on-chain flow, tracing the funds from government-controlled wallets to Coinbase Prime deposit addresses. Over two days, 3,800.42 BTC (about $235M) and 30,006.75 ETH (about $53M) were …
❤7👍4🔥4
Showing the 12 most recent of 17 posts we hold for @bitok_global. 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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“BitOK” (@bitok_global), 283 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/bitok_global.
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.