A former Robinhood engineer pleaded guilty to insider‑trading charges tied to crypto platform Hyperliquid, Coindesk reported.
🤔5👎2🤬2😢2

Channel
@bingx1
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
103,378subscribers
-818 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002747250336 |
|---|---|
| Type | Channel |
| Username | @bingx1 |
| Description | 🌐 Your portal to the crypto and financial world. Breaking news, insights, and analysis from BingX and crypto market. |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/bingx1 |
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 10 August 2026 and assigned it the closest of 31 fixed categories, at 78% 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 9 other registered channels. 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 |
|---|---|---|---|
| @crypto_tradings/107734 Sept 2026, 18:37 UTC | @bingx1/10929 · this entry4 Sept 2026, 18:39 UTC | 1.00 | 2 minutes |
| @crypto_tradings/107744 Sept 2026, 18:37 UTC | @bingx1/10930 · this entry4 Sept 2026, 18:39 UTC | 1.00 | 2 minutes |
| @bingx1/11004 · this entry9 Sept 2026, 13:32 UTC | @crypto_tradings/108489 Sept 2026, 13:33 UTC | 1.00 | under a minute |
| @crypto_tradings/1085710 Sept 2026, 10:40 UTC | @bingx1/11013 · this entry10 Sept 2026, 10:47 UTC | 1.00 | 7 minutes |
| @bingx1/11746 · this entry1 Oct 2026, 16:25 UTC | @crypto_tradings/115901 Oct 2026, 16:25 UTC | 1.00 | under a minute |
| @bingx1/11749 · this entry2 Oct 2026, 11:47 UTC | @crypto_tradings/115932 Oct 2026, 11:47 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @crypto_tradings | 20 (8/8 hand-verifiable sample passed) | 0.99 | 7 minutes | this entry (14–6) |
| @markets1 | 17 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | @markets1 (15–2) |
| @trading1 | 15 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | this entry (13–2) |
| @bitcoinv | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (14–0) |
| @stocks0 | 11 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (10–1) |
| @airdrop6 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 7 minutes | @airdrop6 (5–2) |
| @sharesx | 6 (6/6 hand-verifiable sample passed) | 1.00 | 28 minutes | this entry (6–0) |
| @signalx | 6 (6/6 hand-verifiable sample passed) | 1.00 | 34 minutes | this entry (6–0) |
| @investmentsz | 5 (5/5 hand-verifiable sample passed) | 0.97 | 22 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. 29 of the 29 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 1,279 comparable posts for this entry, running 5 August 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 keys clone_copy · 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 |
|---|---|---|
| 16 Nov 2026, 06:37 | 103,378 | -12 |
| 12 Nov 2026, 17:55 | 103,390 | -14 |
| 10 Nov 2026, 12:06 | 103,404 | -4 |
| 8 Nov 2026, 20:26 | 103,408 | -1 |
| 7 Nov 2026, 09:56 | 103,409 | -6 |
| 6 Nov 2026, 08:26 | 103,415 | -5 |
| 5 Nov 2026, 07:08 | 103,420 | -3 |
| 4 Nov 2026, 07:56 | 103,423 | -2 |
| 3 Nov 2026, 07:17 | 103,425 | -1 |
| 2 Nov 2026, 08:10 | 103,426 | -5 |
| 1 Nov 2026, 05:19 | 103,431 | -4 |
| 31 Oct 2026, 06:20 | 103,435 | -5 |
| 30 Oct 2026, 07:27 | 103,440 | -12 |
| 29 Oct 2026, 06:18 | 103,452 | -3 |
| 28 Oct 2026, 04:11 | 103,455 | -1 |
| 27 Oct 2026, 03:41 | 103,456 | -6 |
| 26 Oct 2026, 05:16 | 103,462 | -7 |
| 25 Oct 2026, 07:16 | 103,469 | -6 |
| 24 Oct 2026, 04:26 | 103,475 | -4 |
| 23 Oct 2026, 07:05 | 103,479 | first reading |
1,951 posts held, back to 5 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 206 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. It is computed over the 419 of 421 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 1,951 (5 August 2026 – 17 November 2026) |
| Views total | 2,040,336 |
| Reactions total | 33,371 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 05:39 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 17 November 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.
Measured directly from 96 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.
66,112 reactions across 998 posts, in 73 distinct kinds. The most used accounts for 25.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤔 | 16,903 | 25.6% | |
| 👍 | 15,934 | 24.1% | |
| 🎉 | 4,144 | 6.27% | |
| 👏 | 3,818 | 5.78% | |
| 😱 | 3,369 | 5.10% | |
| 🤯 | 3,157 | 4.78% | |
| 👎 | 2,660 | 4.02% | |
| 😢 | 2,581 | 3.90% | |
| 🔥 | 2,208 | 3.34% | |
| 🤬 | 1,240 | 1.88% | |
| 💯 | 1,153 | 1.74% | |
| 🤨 | 1,153 | 1.74% | |
| 😐 | 1,046 | 1.58% | |
| 🤩 | 661 | 1% | |
| ❤ | 591 | 0.894% | |
| 😁 | 486 | 0.735% | |
| 😡 | 280 | 0.424% | |
| 👨💻 | 266 | 0.402% | |
| 💔 | 233 | 0.352% | |
| 😎 | 231 | 0.349% | |
| 53 further kinds | 3,998 | 6.05% |
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 998 of the 1,000 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 66,112 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 22 September 2026 to 17 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.
Telegram’s own ‘edited’ marker: 101 of 421 posts held from the last 30 days (24.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).
A former Robinhood engineer pleaded guilty to insider‑trading charges tied to crypto platform Hyperliquid, Coindesk reported.
🤔5👎2🤬2😢2
Wintermute said in a market note that the Bitcoin bear market remains intact, warning prices could fall to $50,000. The firm added it would only reassess the outlook if Bitcoin climbed back to $68,000 and ETF inflows rebounded.
🤔17😢5👎4😐4🤨1
Berlin — Germany’s parliament approved a law that allows customs officials to seize cryptocurrencies suspected of links to illegal activity without first opening a criminal investigation, according to Cointelegraph.
🤔18👍7👎7😱4🤨3
Trezor said its partner Skladon suffered a security breach that exposed personal information for about 27,000 orders placed between Aug. 9 and Nov. 7.
😱12😢7🤯4👎2
Backpack has received approval from the Commodity Futures Trading Commission to launch the first blockchain-based derivatives exchange in the U.S., featuring a global unified liquidity system, Wublockchain reported. https://www.wublockchain.xyz/news/news-21694
😎17👍9🎉7👏3🤔2
SEOUL — South Korea will allow technology firms to issue won‑backed stablecoins provided banks hold the majority stake.
👍12🤔4👏3😁2
U.S. equities lost about $1.4 trillion in market value today, trimming the total capitalization of the stock market.
😱29😢12🤯9🤔5
Markets — Today's summary and tomorrow's events: https://t.me/bingx1/2147483647
👍44❤15🔥13🤔8👏5
A judge acquitted two MIT brothers, ruling that the alleged $25 million MEV theft did not amount to wire fraud because it took place outside a regulated market.
🤔27🤨13🤯7👎4👏2
Lighter said approximately 5 million USDC belonging to a victim it described as a "trader" has been returned and withdrawals are back online. The company said it has imposed wallet-signature requirements for transfers to the public pool and disabled public access to API-key signing. It also plans to implement IP permission lists, introduce permissions and restrictions for each key, and will actively monitor and revok…
👍48👏17🤔12🎉7😐2
Cypherpunk said it has resumed open‑market purchases of Zcash, buying 3,775 ZEC since the end of the quarter at an average price of $920.40. The additions bring the firm's treasury to more than 341,858 ZEC, representing just over 2% of the total supply, the CEO said.
👍48🤝20🤔15🤓10👏4
Nvidia Corp. (NVDA) said its board of directors is not contemplating a return by Chief Executive Officer Jensen Huang.
🤔45👍16🤨12😐6🤷♂3
Showing the 12 most recent of 1,951 posts we hold for @bingx1. 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.
@bingx1 edited 2 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.
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.
@bingx1 named 2 handles 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“BingX Crypto & Financial News” (@bingx1), 103,378 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/bingx1.
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.