Channel
@bidask
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
2,529subscribers
-13 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002115970711 |
|---|---|
| Type | Channel |
| Usernames | @bidask @bidask_protocol |
| Created | Between 1 November 2023 and 31 May 2024— 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 | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/bidask |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:17 | 2,529 | -2 |
| 9 Aug 2026, 23:41 | 2,531 | -3 |
| 8 Aug 2026, 21:46 | 2,534 | -7 |
| 6 Aug 2026, 15:25 | 2,541 | no change |
| 6 Aug 2026, 07:30 | 2,541 | -1 |
| 6 Aug 2026, 05:32 | 2,542 | no change |
| 6 Aug 2026, 01:31 | 2,542 | no change |
| 6 Aug 2026, 00:42 | 2,542 | first reading |
20 posts held, back to 25 February 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 3 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 20 posts for this entry, the most recent from 9 June 2026. An engagement rate over an empty window would be a number about nothing.
72 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 48.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 35 | 48.6% | |
| ❤ | 17 | 23.6% | |
| 🔥 | 11 | 15.3% | |
| 😁 | 3 | 4.17% | |
| 🤯 | 3 | 4.17% | |
| 💯 | 2 | 2.78% | |
| 🥰 | 1 | 1.39% |
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 18 of the 20 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 72reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 25 February 2026 to 9 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bidask. 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 20 most recent posts we hold for this entry, published 25 February 2026 to 9 June 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.
💱 HYDRA Farming: A Legendary Year Comes to a Close! Exactly one year ago, on June 8, 2025, we launched the massive HYDRA token farming campaign on Bidask Protocol. Today, on June 9, 2026, this epic chapter officially wraps up. 🏴☠️ The final farming participation rewards: https://tonviewer.com/transaction/87428dca223b295fe627538d989654a195d071bebbb2796c05c87c857b59efa7 It has been an incredible 366 days, filled w…
❤6🥰1😁1
💱 Safety First! The cryptocurrency market attracts not only honest investors but also scammers who try to impersonate project representatives. To ensure your funds always remain safe, here is a reminder of our support team's basic rules: ❌ Bidask Support will NEVER send you a direct message (DM) first without purpose! If someone messages you privately pretending to be an admin, technical specialist, or Bidask empl…
❤2🔥1😁1
💱 Happy Anniversary, TON! 5 Years of Great History 🤑 Our favorite network is celebrating its first major milestone — 5 years! It was on May 26, 2021, that a truly historic event took place: the crypto community voted to rename the testnet2 testnet to mainnet, and the NewTON developer group officially announced the creation of the TON Foundation. Without TON’s unique architecture, we could never have launched Bidask…
❤2👍2
💱 How to eat pizza and keep your millions? Today, May 22nd, crypto enthusiasts around the world traditionally order pizza and remember the legendary purchase by Laszlo Hanyecz. In 2010, he paid 10,000 BTC for two family-size Papa John’s pizzas. As of today, the value of that meal is an insane ~$773.4 million! 🤯 Laszlo made history forever, but his example serves as the best lesson for each of us. There is a fundame…
💱 Trends come and go, but some things are eternal! That’s exactly how we’d describe the farming rewards in the HYDRA-TON pool. By the way, we just sent them out: https://tonviewer.com/transaction/d5d856599bfa761cda98aac27cfac3d87e482baa9d5dd7f5a44bc7f585717051 🏴☠️How much have you managed to stack since the start of farming? Community chat | DEX | X | EN Channel | CIS Channel | Website
🔥1
Posted without readable text
💱 My dad works at TON. Today he was called into an urgent meeting. He came back late and didn't explain anything. He just told us to pack our bags and go buy groceries for two weeks. Now we're driving somewhere far out of town. I don't know what's happening, but I think it has begun... What has begun is what we've all been waiting for: TON fees are dropping 6x! 🚀 A transaction now costs just 0.00039 TON (~$0.0005).…
🤯3👍2
💱 TON 2026 Roadmap: Why the calm is the time to prepare? While the charts aren't going "to the moon," TON architects are laying the groundwork for the next wave of mass adoption. The second quarter of 2026 promises to be a turning point for the entire ecosystem and for Bidask in particular. Here is how the key milestones of the Roadmap will affect our experience: 1⃣ New TON Consensus (Q2 2026) The core consensus me…
👍3🔥2😁1
💱 You’ve got a new notification... Check your wallet! It seems that in the holiday rush, we forgot to mention: the latest HYDRA farming rewards have already been sent! If you've been providing liquidity, check your balance. There might be a pleasant surprise waiting for you that you didn't know about yet. 🏴☠️ Verify the transaction here: https://tonviewer.com/transaction/8c732a0eb03c75ebdd097079f5afc4a876f1e69afb…
👍1🔥1
💱 Speeding Up with TON! The TON network has made a historic leap in performance. The validator vote for Catchain 2.0 activation was successful, and the blockchain is now operating at lightning speeds. For Bidask users, this means moving to a whole new level of convenience. The numbers behind the upgrade: 🔘 Transaction Finalization: Now takes less than a second (compared to the previous ~10 seconds). 🔘 Block Creati…
👍4
💱 Boundaries are Fading! The TON ecosystem has taken a massive leap toward global adoption—WalletConnect is now officially integrated into our network. This means Bidask Protocol is now even more accessible to millions of users worldwide! What is WalletConnect? It is the "gold standard" of connectivity in the Web3 world. As a decentralized infrastructure connecting over 700 wallets and 70,000 applications, this pow…
👍2
💱 If you had your own AI agent managing your liquidity — what would you trust it with? We’re seeing a huge surge in AI agents and custom agentic frameworks, where anyone can build their own network of bots for specific tasks. Imagine this: an agent analyzes the market, monitors volatility, manages positions, and helps you make decisions about your liquidity on Bidask. Do you think you could build an agent (or a ne…
❤3👍2
Showing the 12 most recent of 20 posts we hold for @bidask. 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.
Citation-graph rank — 1,206 of 1,151,006entries 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.
Named by 25 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Bidask Protocol” (@bidask), 2,529 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/bidask.
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.