Telegram RegisterThe public register of Telegram

Channel

DeDust.io – TON DEX

@dedust_en

Verified by Telegram2 usernames

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Domains linked from posts · Cite this entry

70,224subscribers

-349 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001556132596
TypeChannel
Usernames@dedust @dedust_en
DescriptionDEX: dedust.io Chat: t.me/dedust_en_chat Bot: @dedustBot X: x.com/dedust_io На русском: @dedust_ru Partnership: contact@dedust.io
CreatedBetween 1 July 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/dedust_en

Growth

70,22470,57370,398.55 August 2026 — 70,573 subscribers5 August 2026 — 70,573 subscribers6 August 2026 — 70,573 subscribers6 August 2026 — 70,567 subscribers6 August 2026 — 70,547 subscribers7 August 2026 — 70,513 subscribers7 August 2026 — 70,487 subscribers8 August 2026 — 70,481 subscribers8 August 2026 — 70,453 subscribers9 August 2026 — 70,434 subscribers9 August 2026 — 70,404 subscribers10 August 2026 — 70,383 subscribers10 August 2026 — 70,346 subscribers11 August 2026 — 70,279 subscribers11 August 2026 — 70,274 subscribers12 August 2026 — 70,224 subscribers12 August 2026 — 70,224 subscribers5 August 202612 August 2026
17 measurements spanning 7 days, net -349. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 70,172–70,625 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:3870,224no change
12 Aug 2026, 11:5470,224-50
11 Aug 2026, 13:3970,274-5
11 Aug 2026, 08:3770,279-67
10 Aug 2026, 16:3870,346-37
10 Aug 2026, 05:1170,383-21
9 Aug 2026, 16:2270,404-30
9 Aug 2026, 05:5070,434-19
8 Aug 2026, 13:4470,453-28
8 Aug 2026, 06:2270,481-6
7 Aug 2026, 16:5070,487-26
7 Aug 2026, 06:2770,513-34
6 Aug 2026, 17:2070,547-20
6 Aug 2026, 03:5070,567-6
6 Aug 2026, 01:3570,573no change
5 Aug 2026, 22:0370,573no change
5 Aug 2026, 22:0170,573first reading

Engagement

20 posts held, back to 20 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 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 15 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
90
Videos
8
Links
116

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
30s
Average length
30s

Measured directly from 1 video 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.

Reaction mix

1,014 reactions across 20 posts, in 21 distinct kinds. The most used accounts for 32.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
33132.6%
🔥14013.8%
👍13813.6%
custom 530080456176884715412212.0%
❤‍🔥706.90%
🍾595.82%
custom 5249336899214007015484.73%
💯201.97%
171.68%
😈151.48%
👌121.18%
🦄111.08%
🤣60.592%
🥰60.592%
👏50.493%
😁40.394%
🌚30.296%
🎉30.296%
🍌20.197%
🌭10.099%
1 further kind10.099%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 20 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 1,014reactions 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 20 November 2025 to 15 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.

Recent posts

15 Jun 2026, 15:43 UTC≈4,200 views72 reactionsread 12 August 2026
Forwarded from @x1000_enPhoto

🌚 DEX Screener update costs $0 To support deployers who choose Uranus, we're covering the DEX Screener "Token Info" upgrade for the next 10 migrated tokens. 👍 Requirements: • Launch and bond your token through Uranus • Disable "Creator rewards" using the CTO-ready launch type • Exceed $50,000 in total trading volume Once your token migrates and hits the volume requirement, send us a DM in the Deploy Channel. Only

custom 53008045617688471543714❤‍🔥10🍾9😈2

10 Jun 2026, 16:43 UTC≈4,190 views40 reactionsread 12 August 2026
Forwarded from @x1000_enPhoto

🚀 Ready, steady, CTO! A new launch format on Uranus: CTO-ready. No "Creator rewards" after the bonding, and trading fee is just 0.25% We've also updated the bonding threshold: now it requires 2550 GRAM instead of 1050. Uranus v3 architecture provides unprecedented flexibility, so expect even more custom settings for launches in future updates. Launch on Uranus⚡️ Terminal | Chat | Depoys 🟢

custom 530080456176884715417❤‍🔥13🍾73

2 Jun 2026, 10:40 UTC≈4,120 views41 reactionsread 12 August 2026
Photo

🔄 Toncoin leaves the chat Following recent upgrades, The Open Network has become significantly faster and cheaper. Reflecting this new stage of development, Telegram has proposed renaming Toncoin (TON) to Gram (GRAM), and the decision is now up to the community. The blockchain itself keeps its previous name. The polls are now live on TON Vote. Have your say and shape the future of our ecosystem. 🛎️ Important: No

custom 530080456176884715418❤‍🔥98🍾4😈2

28 May 2026, 09:55 UTC≈4,270 views36 reactionsread 12 August 2026
Photo

🔒 Don’t burn it — lock it Launching a token is always about trust. Traders want guarantees that the dev won’t rug pull on day one. Usually, creators either burn LP tokens or rely on third-party lockers. But why burn something that can keep generating revenue? 💡 On the liquidity deposit page for CPMM v2 pools, there’s a native locking feature available. You can find it under the Advanced section when adding liquidi

custom 53008045617688471542011❤‍🔥5

18 May 2026, 10:28 UTC≈3,750 views35 reactionsread 12 August 2026
Forwarded from @x1000_enPhoto

🌚 Uranus is now on DEX Screener Track all deploys, monitor bonding progress and catch migrations to DeDust. https://dexscreener.com/ton/uranus Terminal | Chat | Depoys 🟢

19😈8custom 53008045617688471545❤‍🔥3

7 May 2026, 09:53 UTC≈4,880 views70 reactionsread 12 August 2026
Photo

🔥 100 million dollars on DeDust Router This is the total volume our DEX aggregator has processed so far - in fact, even a few million more. This is an important milestone for us and for the entire TON ecosystem. Huge thanks to all traders, LPs, and partners. Want to integrate it into your product? Find us in @dedust_dev_chat. More to come, DeDust team 🔸 TMA | Web | Twitter | Community

28custom 530080456176884715425❤‍🔥13😈3🍾1

21 Apr 2026, 12:05 UTC≈4,950 views34 reactionsread 12 August 2026
Photo

They stayed up all night just for you ❤️ In our previous post, we explained how scammers impersonate DeDust team members and other protocols to trick you into giving them access to your funds. “Damn, they’re sneaky,” you might think. “That’s just the beginning,” we’d say. 🔒 Sometimes they go as far as creating entire fake group chats, complete with fake admins and users who deliberately chat with each other, disc

custom 524933689921400701513👍1143🔥3

11 Apr 2026, 09:19 UTC≈4,220 views40 reactionsread 12 August 2026
Photo

Your pool — your rules 🔒 With the launch of CPMM v2 on DeDust, it’s now possible to create pools with custom settings. When creating a pool, you can choose both the fee size and the asset in which the fees are collected. 🔍 Fees are pretty straightforward: From 0.1% to 5% of each swap is charged to traders. Out of that, 70% of all fees are distributed to liquidity providers. 💸 Fee token works like this: Let’s say y

18🔥12💯7🍾3

9 Apr 2026, 13:58 UTC≈3,420 views43 reactionsread 12 August 2026
Photo

🔥 Speeeeeed Today, network validators approved the Catchain 2.0 upgrade, increasing block production speed by roughly 6x. This means swaps on DeDust now execute in ~1 second. Congratulations to TON Core and the entire ecosystem on this upgrade. TMA | Web | Twitter | Community

🔥22👍129

6 Apr 2026, 16:04 UTC≈3,810 views43 reactionsread 12 August 2026
Photo

Less talk — more integrations ⚙️ Since March 2025, the DeDust router has processed nearly $86M in volume. But the numbers aren’t the main point — what matters is that teams across the ecosystem trust us to handle swap routing for their users. 🔄 Our router is already used by: MyTonWallet — one of the most popular TON wallets GroypFi — an all-in-one platform on TON EdChess — a Telegram Mini App chess game with cryp

👍14🔥13🍾76custom 52493368992140070152👏1

4 Apr 2026, 14:22 UTC≈2,990 views33 reactionsread 12 August 2026
Forwarded from @x1000_enPhoto

Missed green candles? 🐸 Last week, Groypad launched — a meme pad by the same team of hype-generating enthusiasts. Under the hood, it’s powered by our Uranus smart contracts — which means no issues with token compatibility, blacklists, or swaps disappearing into TVM black holes. ⚡️ Notable features: Migration happens directly to DeDust CPMM v2 pools 10% of fees go toward buybacks of leaderboard tokens via the NGL

🔥11👍108👏4

28 Mar 2026, 08:05 UTC≈6,900 views39 reactionsread 12 August 2026
Photo

WalletConnect × TON ⚙️ It’s no secret that both EVM degens and major players — including large funds — are used to relying on battle-tested infrastructure to keep their assets secure. Until now, entering the TON ecosystem meant creating separate wallets and adapting to a new flow, which was a significant barrier for many. With yesterday’s update, interacting with TON dApps has become seamless and intuitive — users

👍14🔥1211🦄2

Showing the 12 most recent of 20 posts we hold for @dedust_en. 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

Citation-graph rank — 91,570 of 1,160,990entries 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.

Forward network

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.

Mentions

Named by 37 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.

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.

Domains linked from posts

12 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

dedust.io12 posts · 20 November 2025 – 2 June 2026 · example post
x1000.finance12 posts · 7 December 2025 – 15 June 2026 · example post
x.com11 posts · 31 December 2025 – 2 June 2026 · example post
groypfi.io4 posts · 4 April 2026 – 11 April 2026 · example post
help.dedust.ioregistrable domain: dedust.io1 post · 22 March 2026 – 22 March 2026 · example post
love.dedust.ioregistrable domain: dedust.io1 post · 14 February 2026 – 14 February 2026 · example post
dexscreener.com1 post · 18 May 2026 – 18 May 2026 · example post
dune.com1 post · 7 May 2026 – 7 May 2026 · example post
dyor.io1 post · 6 April 2026 – 6 April 2026 · example post
split.tg1 post · 6 April 2026 – 6 April 2026 · example post
blog.ton.orgregistrable domain: ton.org1 post · 31 December 2025 – 31 December 2025 · example post
ton.vote1 post · 2 June 2026 – 2 June 2026 · example post

Cite this entry

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.

“DeDust.io – TON DEX” (@dedust_en), 70,224 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dedust_en.

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.