https://x.com/CertiKCommunity/status/1766212545990299908
👍4❤1

Channel
@swiftotc_announcements
On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
3,586subscribers
-82 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001994183723 |
|---|---|
| Type | Channel |
| Username | @swiftotc_announcements |
| Created | 29 January 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/swiftotc_announcements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 04:38 | 3,586 | -8 |
| 2 Sept 2026, 08:08 | 3,594 | -11 |
| 30 Aug 2026, 07:36 | 3,605 | -6 |
| 27 Aug 2026, 17:02 | 3,611 | -4 |
| 24 Aug 2026, 21:18 | 3,615 | -12 |
| 21 Aug 2026, 02:24 | 3,627 | -9 |
| 17 Aug 2026, 18:37 | 3,636 | -11 |
| 14 Aug 2026, 21:16 | 3,647 | -10 |
| 11 Aug 2026, 04:26 | 3,657 | -11 |
| 7 Aug 2026, 12:33 | 3,668 | no change |
| 7 Aug 2026, 12:19 | 3,668 | first reading |
14 posts held, back to 29 January 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pages 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 14 posts for this entry, the most recent from 9 March 2024. An engagement rate over an empty window would be a number about nothing.
1,332 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 49.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 660 | 49.5% | |
| ❤ | 475 | 35.7% | |
| 👍 | 99 | 7.43% | |
| 👏 | 56 | 4.20% | |
| 🐳 | 22 | 1.65% | |
| 🥰 | 15 | 1.13% | |
| 👎 | 5 | 0.375% |
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 9 of the 14 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,332 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 29 January 2024 to 9 March 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://x.com/CertiKCommunity/status/1766212545990299908
👍4❤1
Swift OTC pinned a photo
🔒 SwiftOTC has proudly passed the CertiK Security Assessment! We're all about elevating your trading experience with top-tier security. Gear up for the revamped platform - it's sleeker, faster, and more secure than ever! 🌐 In the meantime, get a sneak peek at our commitment to excellence. Dive into our audit and code on GitHub: https://github.com/SwiftOTC/contracts/blob/main/SwiftOTC-Certik.pdf 🧐
We have introduced multi-signature authentication and implemented 48-hour time-lock controls for privileged functions in order to uphold transparency in SwiftOTC. 🛡 If you would like to learn more about how we handled the situation, read below: 📖 https://medium.com/@swiftotc/the-majority-of-smart-contracts-contain-special-functions-that-are-exclusively-accessible-to-the-0f18d85670a1
❤1
🚀 Big updates on the way! ✨ While security audits are ongoing, we've completely revamped the UI/UX of SwiftOTC. 💫 Get ready for a sleek new look and improved user experience! 👀 Stay tuned for updates.
🚀 We're thrilled to announce that CertiK is officially kicking off our security audits. We're partnering with the best to ensure unparalleled security for our users.🔒 Stay tuned for updates to see what we're brewing! 🧙♀️ Read more below 👇 https://medium.com/@swiftotc/swiftotc-first-audit-by-certik-2fd7cd8e30be
❤9👍1
🔐 Exciting News, We're leveling up! Our Smart Contracts are gearing up for a top-tier security audit. ✨ Your trust is our treasure, and we're committed to ensuring unparalleled security for our users. 🛡 Stay tuned for updates and get ready for a safer, stronger trading scene! 🌟
❤36🔥25
Swift OTC pinned a photo
🎉 Big news! The SwiftOTC GitHub is now live! Soon, you'll be able to explore all our contracts & source code. Stay tuned for a transparent future with us! 🔍✨ 🔗 https://github.com/orgs/SwiftOTC/
❤84👍13
🚀 You can now discuss with other users about the SwiftOTC Platform on our Telegram Group. ☑️ Simplify Your Trading: A user-friendly platform that transforms the complexity of crypto trades into a seamless experience. https://t.me/swiftotc_discussions
❤193👍12👏4
SwiftOTC is here to support you at every need! ✅ Although the SwiftOTC Platform is automatic and we do not hold any of your funds, the sale being completed once a buyer is found for your offer, if you require any assistance or experience any technical difficulties you can reach us at: [email protected] t.me/swiftotc_official Thank you. 🎉
🔥43👏4
💵Airdrop is live!!! 🏮Welcome to SwiftOTC Community -------------------------------------------------------------------------------------------- Participate in our Airdrop and earn 2 USDT for doing tasks. Join our airdrop bot here: @SwiftOTCAirdropbot SwiftOTC shields DeFi traders from unpredictable market turbulence, ensuring a user-friendly peer-to-peer trading experience. Airdrop rewards will be distributed …
🔥592❤138👍67👏48🐳22🥰13👎5
Showing the 12 most recent of 14 posts we hold for @swiftotc_announcements. 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.
@swiftotc_announcements named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Swift OTC” (@swiftotc_announcements), 3,586 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/swiftotc_announcements.
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.