Telegram RegisterThe public register of Telegram

Channel

DeDust Developer News

@dedust_dev

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

524subscribers

+8 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002184665851
TypeChannel
Username@dedust_dev
Created21 July 2024measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/dedust_dev

Growth

515524519.56 August 2026 — 516 subscribers6 August 2026 — 515 subscribers6 August 2026 — 515 subscribers12 August 2026 — 524 subscribers6 August 202612 August 2026
4 measurements spanning 7 days, net +8. 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 514–525 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 14:56524+9
6 Aug 2026, 18:33515no change
6 Aug 2026, 03:00515-1
6 Aug 2026, 01:36516first reading

Engagement

13 posts held, back to 21 July 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 13 posts for this entry, the most recent from 13 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

249 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 50.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍12550.2%
🔥9538.2%
🤡124.82%
🏆62.41%
52.01%
31.20%
👎31.20%

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 12 of the 13 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 249reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 21 July 2024 to 13 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

13 Jun 2026, 13:39 UTC401 views9 reactionsread 6 August 2026

🚀 Uranus v3.1 Released We have deployed Uranus v3.1, which includes a fix for an issue affecting partner fee tracking when partnerFeeBPS was configured above 20%. Impact • Affected only Uranus v3 memes with partnerFeeBPS > 20%. • No impact on deployments using partner fees at or below 20%. • Meme Wallet is unaffected and remains unchanged. Updated Contracts Factory v3.1: EQAmkd4Pd_xgUW4b9MLrygf0SOfR2EUVa_iCtVWGn

👍6🔥3

Signed Nick Nekilov

19 May 2026, 16:26 UTC625 views46 reactionsread 6 August 2026

Uranus Protocol Rev.3 is live - focused on builders Now anyone can build their own memepad and launch customized memes on top of Uranus via new Factory message DeployCustomizedMemeMessage. New in Rev.3: • Partner fee sharing on bonding curves • Revenue share after migration via CPMM v2 • Adjustable raise target: 800 TON → 1M TON • Supply presets: 100M / 1B / 10B • Bonding curve allocation: 60–80% • Configurable LP

👍23🔥20👎3

Signed Nick Nekilov

8 May 2026, 15:41 UTC696 views21 reactionsread 6 August 2026

We’ve just released a new revision of Uranus. What’s changed? • Collected fee distribution updated to 80/20 • 80% → creator • 20% → protocol (previously 70/30) • Added new meme deployment presets: • 1500 TON migration preset • 2500 TON migration preset • New presets migrate 25% of supply instead of 20% New Meme Factory address: EQBvhJBSxkmpAEkIoQfqztCPGRQNaCObIVuoy_Rz7oTbWBYi More details: https://hub-

🔥11👍10

Signed Nick Nekilov

6 May 2026, 18:56 UTC637 views14 reactionsread 6 August 2026

Here is documentation (very early version) for CPMM v2 pools: https://hub-beta.dedust.io/docs/cpmm-v2/overview Also, here is a package with TypeScript wrappers and examples for CPMM v2 and Uranus contracts: https://github.com/dedust-io/kit We are actively preparing documentation for Uranus. So if you have some requests - let us know in @dedust_dev_chat. Thank you.

🔥8👍6

Signed Nick Nekilov

1 May 2026, 18:30 UTC580 views7 reactionsread 6 August 2026

We’ve released a new revision of CPMM v2 pools. This update includes two changes: - Fixes wallet discovery via legacy TEP-89 contracts (with hard-coded thresholds) - Reduces the protocol fee from 30% to 20%; this change does not affect existing pools Code: b5ee9c72410101010023000842026045e67b617e73486aac445cfcad0dbead6d315ccc8f4aede3f2e23ad14da4b0b07806ea Code Hash: 5851780d2386e989b9ab956da7cec5c69a667b9e525f6

🔥5👍2

Signed Nick Nekilov

5 Apr 2026, 11:15 UTC619 views7 reactionsread 6 August 2026

Heads up for developers: The API at https://dedust.io/v1/ was a private mirror and was never intended for public use. If you’ve been using it, please migrate as soon as possible: https://dedust.io/v1/ → https://mainnet.api.dedust.io/v4/ Additionally, the following endpoints will be deprecated in the future, so we strongly recommend updating them now: https://api.dedust.io/v2/ → https://mainnet.api.dedust.io/v2/ h

👍7

Signed Nick Nekilov

5 Jan 2026, 15:13 UTC947 views23 reactionsread 6 August 2026

Sharing TVM knowledge We have strong hands-on experience with TVM and want to start publishing short technical articles and deep dives. What TVM-related topics would you like to read about? Share your ideas in our developer chat. Also, we’re close to finishing the documentation for CPMM v2 contracts - stay tuned 📘🚀

👍14🔥9

Signed Nick Nekilov

23 Jun 2025, 17:02 UTC≈3,450 views9 reactionsread 6 August 2026

Major update for tonkite/jest-tolk What is new? - A lot of helpers and assetions (API, examples) - Fuzz testing (examples) Documentation: tonkite/jest-tolk Release: 1.0.0 Happy testing 🚀

👍7🔥2

Signed Nick Nekilov

11 May 2025, 06:47 UTC≈3,600 views22 reactionsread 6 August 2026

Today, we distributed all referral fees collected over the last 3 months of the referral program (October 1, 2024 – December 31, 2024) from this wallet: https://tonscan.org/address/EQAx1McP8Fq1_gg2q2Le0l0GnnAgmMyeyZ6gzK7nmPHI_C02

👍22

Signed Nick Nekilov

21 Jan 2025, 10:33 UTC≈1,850 views17 reactionsread 6 August 2026
Forwarded from @tolk_lang

Two months of absence: what was going on? Two months have passed since the announcement of Tolk. You might be wondered, what was going on and why there we no releases yet. Throughout all November, I've been working on the vision of the future. My goal was to "visualize" what Tolk v1.0 should look like. What's the language we're all targeting to, so that it solves lots of practical problems, avoids manual cells/slic

👍9🔥53

Signed Nick Nekilov

28 Dec 2024, 09:17 UTC≈2,090 views44 reactionsread 6 August 2026

Important update: closure of built-in DeDust referral revenue sharing program We want to inform you about the discontinuation of the DeDust referral revenue-sharing (fee-sharing) program. As a reminder, swap fees on DeDust are structured as follows: - 80% of the fee is allocated to liquidity providers (LPs), enhancing the value of LP tokens by reinvesting back into the pool. - 20% is collected as protocol fees. Cu

🔥15👍12🤡125

Signed Nick Nekilov

26 Dec 2024, 17:12 UTC≈7,920 views30 reactionsread 6 August 2026
Photo

Introducing Unit-Testing in Tolk with Jest Tolk developers rejoice! Unit-testing for smart contracts just got easier. While sandbox offers E2E testing, it’s far from ideal for unit-testing. Now, with the Jest-Tolk runner, unit-testing in Tolk is a reality. Seamlessly integrate with Jest and streamline your testing workflow today. Explore the tool! GitHub: tonkite/jest-tolk NPM: @tonkite/jest-tolk Upgrade your sm

🔥17👍7🏆6

Signed Nick Nekilov

Showing the 12 most recent of 13 posts we hold for @dedust_dev. 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 — 231,376 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.

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 6 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.

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.

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 Developer News” (@dedust_dev), 524 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dedust_dev.

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.