Telegram RegisterThe public register of Telegram

Channel

swap.coffee Developers

@swapcoffee_dev

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

159subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002365021808
TypeChannel
Username@swapcoffee_dev
Created7 October 2024measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/swapcoffee_dev

Growth

1597 Aug 2026, 23:44 — 159 subscribers8 Aug 2026, 17:31 — 159 subscribers7 Aug 2026, 23:448 Aug 2026, 17:31
2 measurements taken within a single day. 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 158–160 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 17:31159no change
7 Aug 2026, 23:44159first reading

Engagement

19 posts held, back to 7 October 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 19 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
8
Links
17

Lifetime counters from Telegram’s own channel header, read 8 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.

Reaction mix

39 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 41.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1641.0%
1333.3%
👍717.9%
👏25.13%
12.56%

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

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

3 Jul 2026, 10:54 UTC135 views4 reactionsread 8 August 2026

⚡️Attention! swap.coffee npm package migration!⚡️ Hey everyone 👋 We have an important housekeeping update for those of you integrating with our TypeScript/JavaScript SDKs. We're migrating all of our npm packages to a new organization scope: @swap-coffee/* → @swapcoffee/* Why? 🔨 Due to an internal reorganization of our npm account, we were no longer able to publish under the original swap-coffee scope. Rather th

🔥31

20 Oct 2025, 23:21 UTC514 viewsread 8 August 2026

⚡️Attention! swap.coffee API usage policy update!⚡️ In light of the growing number of projects actively integrating with our public Rest API — which is awesome, by the way 🥰 — we’ve recently noticed that load distribution across our endpoints became highly unbalanced. Most developers use our API primarily for route construction, which is totally fine. However, we noticed that some projects were excessively using cer

23 Sept 2025, 13:51 UTC367 views2 reactionsread 8 August 2026

Heads up, @thermos developers! We are starting to add on-chain gifts from getgems.io (which also includes gifts from Fragment) to the Gift search endpoint. As a transitional measure for the next two weeks (until October 7, 2025), requests with an empty markets array will default to searching [TONNEL, PORTALS, MRKT]. To receive gifts from getgems.io, you must explicitly include GETGEMS in the markets array. This is

🔥2

1 Sept 2025, 17:35 UTC363 views4 reactionsread 8 August 2026
Photo

UI Widget Update 🎁 🌎 We’ve significantly upgraded the UI Widget Kit. The new version comes with improvements that make integration smoother, expand functionality, and unlock even more use cases: — Smart Mode; — Multiswap with custom fee support; — New token list; — New liquidity providers; — Community tokens with display settings. 🎁 The updated documentation is already available. If you have any questions, feel fr

3🔥1

29 Aug 2025, 15:25 UTC308 viewsread 8 August 2026
Photo

swap.coffee Grant Program 🔥 🫢 We’re opening the swap.coffee Grant Program — an initiative to support developers, teams, and projects building solutions on top of our infrastructure within the TON ecosystem. 🤑 The program provides financial, technical and promotional support to those who bring value to the platform, improve user experience and expand technical capabilities. The size of each grant will be tailored to

19 Aug 2025, 21:27 UTC403 views2 reactionsread 8 August 2026

⚡️⚡️⚡️ Due to the scheduled @thermos maintenance, website & backend.thermos.gifts will be unavailable from 21:30 UTC to 23:00 UTC. After the maintenance, certain schemas in backend.thermos.gifts will be updated (specifically, the types of all price fields will be changed from integer to string). proxy.thermos.gifts will remain available.

👍2

5 Aug 2025, 19:22 UTC260 views2 reactionsread 8 August 2026

⚡️⚡️⚡️ Due to the @thermos infrastructure update, the proxy.thermos.gifts will be unavailable for up to 10 minutes. There may also be interruptions in availability today from 9 PM to 1 AM UTC. Update: proxy is available again :)

1👍1

4 Aug 2025, 19:09 UTC239 viewsread 8 August 2026
Photo

Introducing Smart Mode 🧠 💪 No more manual settings — forget about adjusting slippage, managing intermediate tokens, or analyzing pool volatility. 💻 Smart Mode handles everything for you. We’ve built an intelligent AI-powered algorithm into the new mode that automatically finds the best conditions for your swap. 🤖 How Smart Mode works: — Selects the most optimal swap route; — Automatically sets slippage for maximum

3 Jul 2025, 19:21 UTC322 views11 reactionsread 8 August 2026

Hello Everyone 👨‍💻 Today, we are excited to announce the launch of Thermos, the best gift aggregator on Telegram! No fees, no hidden charges 🏆 We are open to developers and new projects provide an API for anyone! You can find the API documentation here: https://docs.swap.coffee/technical-guides/thermos/backend-api. Feel free to create your own products with Thermos.

🔥63👏2

5 Jun 2025, 15:20 UTC236 views4 reactionsread 8 August 2026
Forwarded from @swap_coffeePhoto

Meet Coffee DEX 🧩 It is the foundation of a new generation of swap exchanges.Coffee is a powerful, extensible and open protocol designed for both users and developers. 👑 Coffee DEX provides the smoothest possible user experience: smart routing, lowest gas consumption compared to other solutions on the DEX market, support for using liquidity from other protocols. It's a solution where security, efficiency and flexib

4

29 Apr 2025, 20:09 UTC361 views4 reactionsread 8 August 2026
Photo

swap.coffee at the TON Mini Apps Build Contest AMA Session As part of the TON Mini Apps Build Contest, we’ll be sharing how to connect a Mini App with backend services, smart contracts, and blockchain-based notifications in Telegram. Our lead developer Nikita Duginets will cover: • Backend architecture and logic for Mini Apps • Session handling and user verification with TON Proof • Smart contract integration and t

👍211

17 Apr 2025, 16:56 UTC344 views2 reactionsread 8 August 2026
Photo

UI Widget Kit Update 👩‍💻 We’ve just updated the UI Widget Kit — it now includes several important improvements. • New design • MEV Protect support • Limit Orders and DCA support • Token list management • Liquidity provider management • Initial tokens (firstToken, sendToken) • Default amount value configuration • Option to hide Limit/DCA The updated documentation is already available.

👍2

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

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

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“swap.coffee Developers” (@swapcoffee_dev), 159 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/swapcoffee_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.