Channel
@stonfidevs
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
218subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002468464663 |
|---|---|
| Type | Channel |
| Username | @stonfidevs |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/stonfidevs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 19:20 | 218 | -6 |
| 14 Aug 2026, 11:47 | 224 | -2 |
| 7 Aug 2026, 23:03 | 226 | no change |
| 7 Aug 2026, 06:01 | 226 | first reading |
20 posts held, back to 6 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 1 page of 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 21 July 2026. An engagement rate over an empty window would be a number about nothing.
8 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 50.0% | |
| 👍 | 2 | 25.0% | |
| 👏 | 2 | 25.0% |
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 4 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 8 reactions 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 6 February 2026 to 21 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.
STON.fi Dev Announcements pinned «🚀 Omniston Cross-Chain Expansion Update Omniston’s cross-chain network continues to grow. If you missed it, we have added support for four new chains, including TRON now officially available today: 🔴 TRON 🔵 Arbitrum 🔺 Avalanche ⚫️ Robinhood Chain With…»
🚀 Omniston Cross-Chain Expansion Update Omniston’s cross-chain network continues to grow. If you missed it, we have added support for four new chains, including TRON now officially available today: 🔴 TRON 🔵 Arbitrum 🔺 Avalanche ⚫️ Robinhood Chain With these additions, developers can now access more cross-chain routes through Omniston’s atomic swap infrastructure. We have also released an updated Omniston SDK …
STON.fi Dev Announcements pinned «📢 Omniston SDK Update: Price Impact Estimation We’ve added a new price_impact_pips field to the Omniston API and SDK. The price_impact_pips field is available for Swap settlement via DEXs only. It estimates the relative difference between the swap execution…»
📢 Omniston SDK Update: Price Impact Estimation We’ve added a new price_impact_pips field to the Omniston API and SDK. The price_impact_pips field is available for Swap settlement via DEXs only. It estimates the relative difference between the swap execution price and the mid-market price immediately before the swap, helping developers identify swaps with significant price impact caused by trade size or limited liqu…
STON.fi Dev Announcements pinned «🚀 Omniston Cross-Chain Expansion Update Cross-chain routing continues to expand. EVM ↔️ EVM routes are now live on production. You can now perform cross-chain swaps between supported EVM networks through Omniston’s atomic swap infrastructure. Supported…»
🚀 Omniston Cross-Chain Expansion Update Cross-chain routing continues to expand. EVM ↔️ EVM routes are now live on production. You can now perform cross-chain swaps between supported EVM networks through Omniston’s atomic swap infrastructure. Supported networks: 💎 TON 🟡 BNB Chain 🔵 Ethereum 🔵 Base 🟣 Polygon Current route coverage: 🌐 EVM ↔️ EVM 🌐 TON ↔️ EVM 💵 Supported cross-chain assets: • USD₮ on TON • USD₮…
👏2
Join us live May 26, 14:00 UTC: Emerging TON Builders Just a few hackathon or grant projects keep going after demo day, and we're working to change that! Next week join us for an online developer session with emerging projects like Dyadnum, @stuntrade_bot and @Toncast_TCAST that already ship on top of http://STON.fi infrastructure and keep building. 📅 May 26 · 14:00 UTC What we’ll discuss: 1️⃣ How these teams int…
STON.fi Dev Announcements pinned «⚠️ Omniston API Support Notice We’re announcing the upcoming end of support for older Omniston API versions: • v1beta6 → support ends on 01 June 2026 • v1beta7 → support ends on 01 September 2026 Developers should migrate to the latest API version below…»
⚠️ Omniston API Support Notice We’re announcing the upcoming end of support for older Omniston API versions: • v1beta6 → support ends on 01 June 2026 • v1beta7 → support ends on 01 September 2026 Developers should migrate to the latest API version below to ensure uninterrupted service and access to our newest improvements: • v1beta8 → https://docs.ston.fi/developer-section/omniston/v1beta8 If you have any questi…
❤1
STON.fi Dev Announcements pinned «🚀 Omniston v1beta8 — Now Live in Production We’ve moved Omniston v1beta8 into production, bringing the latest iteration of STON.fi’s swap aggregation infrastructure a step closer to full cross-chain capability. 🔧 What’s live now: 🌐 v1beta8 API is live in…»
🚀 Omniston v1beta8 — Now Live in Production We’ve moved Omniston v1beta8 into production, bringing the latest iteration of STON.fi’s swap aggregation infrastructure a step closer to full cross-chain capability. 🔧 What’s live now: 🌐 v1beta8 API is live in production 🧩 SDK Release Candidates with v1beta8 support are available * @ston-fi/omniston-sdk → 0.8.0 * @ston-fi/omniston-sdk-react → 0.8.0 🖥 Demo app …
STON.fi Dev Announcements pinned «🔄 Omniston v1beta8 Update Quick clarification on the earlier announcement 👇 At the time of posting, only the proto files and glossary were published to help developers start exploring the new version. Now, we’re ready for the next step: 🧪 Sandbox is live…»
Showing the 12 most recent of 20 posts we hold for @stonfidevs. 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.
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.
Named by 5 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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“STON.fi Dev Announcements” (@stonfidevs), 218 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/stonfidevs.
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.