Channel
@SafeFairMoonAnnouncements
On this record: Growth · Engagement · Posts · Cite this entry
8subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001211637224 |
|---|---|
| Type | Channel |
| Username | @SafeFairMoonAnnouncements |
| Created | Between 1 March 2018 and 26 April 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/SafeFairMoonAnnouncements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 01:18 | 8 | -1 |
| 12 Aug 2026, 10:49 | 9 | no change |
| 6 Aug 2026, 23:55 | 9 | first reading |
20 posts held, back to 26 April 2021 — 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 11 July 2021. An engagement rate over an empty window would be a number about nothing.
Several design ideas and many hours of work later, the time has finally come! We are excited to introduce the new #SafeFairMoon logo. 🚀 From now on, we will also communicate more actively with you again. Lots of work has been done silently. We will share it with you very soon.
Channel photo updated
Check out our latest research article on Fairmoon and the WarOnRugs rugpull. We finally got the answer to who Miley really is, by an expelled WarOnRugs team member. https://saferdefi.medium.com/waronrugs-the-wolf-in-sheeps-clothing-ce9537b3de7b
Join our #SaferDeFi Telegram group! The @SaferDeFi group is the home for the SaferDeFi community. It is used to discuss the security of various tokens, security audits, and the SaferDeFi Platform itself. The group @SafeFairMoonOfficial will of course remain and serve as a platform for the discussion about SafeFairMoon.
The big day is here! 🥳 Time to reveal the name of our platform: We are thrilled to announce the immediate availability of SaferDeFi.com! @SaferDeFi performs security checks on #DeFi tokens and gives you the data/tools you need to trade and invest with confidence. https://twitter.com/SafeFairMoon/status/1393835051377328128?s=20
Less than a day until the release of the first basic version of our upcoming security platform. 👀 In this first step, we will reveal the name of the platform and our service offering will get its own home. New features will come gradually and regularly. We are very excited!😱 https://twitter.com/SafeFairMoon/status/1393476981975502850?s=20
We are thrilled to announce the immediate availability of our very own swap app! 🚀 https://buy.SafeFairMoon.com Any #BSC token can be swapped to #SafeFairMoon via the app. Without interfering popups and warning messages. This is an important milestone for our community! 😎 #DeFi https://twitter.com/SafeFairMoon/status/1393468805133737984?s=20
✅ We audited Lily's Ocean (Lily)! Result: NO Severity Issues found Contract: 0x04B399f248FF583eB9400f9B0C2814869cdDed3B Report: https://www.safefairmoon.com/audits/Lilys-Ocean-Audit_2021-05-08.pdf 🟢 From a technical perspective, we have no reason to advise against investing in the token. #LILYSOCEAN #BSC #Audit All infos in this Twitter thread: https://twitter.com/SafeFairMoon/status/1391421829898588168?s=20
✅ We audited Royal Protocol (ROY)! Result: NO Severity Issues found Contract: 0xcbcB497D505469F34463BBd5490CC46aE43f81cA Report: https://www.safefairmoon.com/audits/Royal-Protocol-Audit_2021-05-03.pdf 🟢 From a technical perspective, we have no reason to advise against investing in the token. #RoyalProtocol #BSC #Audit All infos in this Twitter thread: https://twitter.com/SafeFairMoon/status/1389609080856084484?s=…
⚠️ We audited PolySafe (POLYSAFE)! Result: LOW Severity Issues found Contract: 0xB1CB4aC6b1685DcbE691b9246406748805aa6FA8 Report: https://safefairmoon.com/audits/PolySafe-Audit_2021-05-02.pdf 🟡 From a technical perspective, we have reason to advise particular caution when investing in the token. #PolySafe #Matic All infos in this Twitter thread: https://twitter.com/SafeFairMoon/status/1389602460625375239?s=20
⚠️ We audited SafeSex (SEX)! Result: Medium Severity Issues. Contract: 0x6eA05F63DAF6b0Dc6b8bea94342330CC602c5536 Report: https://www.safefairmoon.com/audits/SafeSex-Audit-Report_2021-05-01.pdf 🟠 From a technical perspective, we have reason to advise particular caution when investing in the token. Full info on Twitter: https://twitter.com/SafeFairMoon/status/1388897819843391489?s=20
We've just started a new #Giveaway on Twitter. Go check it out! 😎 https://twitter.com/SafeFairMoon/status/1388713527091744768?s=20
Showing the 12 most recent of 20 posts we hold for @SafeFairMoonAnnouncements. 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.
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.
“SafeFairMoon Announcements” (@SafeFairMoonAnnouncements), 8 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/SafeFairMoonAnnouncements.
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.