14 Nov 2022, 19:51 UTC766 viewsread 10 August 2026
Latest changelog for 88mph: https://twitter.com/88mphapp/status/1592242186044997632
Channel
88mph announcements
@join88mphAnn
On this record: Growth · Engagement · Posts · Citations · Cite this entry
37subscribers
-1 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 | -1001313884054 |
|---|---|
| Type | Channel |
| Username | @join88mphAnn |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/join88mphAnn |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 01:48 | 37 | -1 |
| 10 Aug 2026, 20:45 | 38 | no change |
| 6 Aug 2026, 23:31 | 38 | first reading |
Engagement
20 posts held, back to 26 April 2022 — 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 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 20 posts for this entry, the most recent from 14 November 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
9 Nov 2022, 15:29 UTC694 viewsread 10 August 2026
88mph vesting contract bug disclosure 1. On September 24, 2022, Szeth, 88mph contributor, submitted a bug report regarding the accounting logic of the MPH reward vesting contract, which resulted in depositors getting significantly more rewards than they should. 2. Approximately ~3572 MPH were fraudulently claimed. 3. Since then, 88mph's core contributors have executed several contract upgrades via the governance mul…
31 Aug 2022, 20:40 UTC564 viewsread 10 August 2026
Hey everyone, 3h left to vote https://twitter.com/88mphapp/status/1565076492903661569
2 Aug 2022, 15:19 UTC491 viewsread 10 August 2026
Hey everyone! 8IP#11 - Rotate multisig signers This proposal seeks to replace the inactive multisig signers with Alan Stivelman and Amadeo Brands 🗳 Vote now on Snapshot https://vote.88mph.app/#/proposal/0x61481cb91f8061aa71f3bbafd116b126996dfc857c7b7043deb9307e425be6ff
26 Jul 2022, 11:10 UTC462 viewsread 10 August 2026
Looking to rotate 2-3 multisig signers https://twitter.com/88mphapp/status/1551887378511499264
22 Jul 2022, 14:57 UTC390 viewsread 10 August 2026
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99% LOADING $veMPH https://etherscan.io/address/0x0f17c89ae8edf5f8ad78d4af5518dc238bb62624 More coming ...
13 Jul 2022, 21:25 UTC353 viewsread 10 August 2026
80MPH-20WETH Balancer pool token has been selected as the locked asset for the upcoming veMPH by the 88mph's governance https://twitter.com/88mphapp/status/1547330486204350464
12 Jul 2022, 10:34 UTC300 viewsread 10 August 2026
Hi everyone! One day left to vote on the last 8IP before moving forward with 88mph v4 $veMPH. Balancer LP token or MPH as the locked asset for v4? Choose wisely ⚡️ https://vote.88mph.app/#/proposal/0x83842c17f0bb039871a67daee32b74da903cad9ee96689648df26ec7f281fc48
10 Jul 2022, 19:12 UTC223 viewsread 10 August 2026
Calling all $xMPH holders! We have created an 8IP 🦧 to move forward with 88mph v4 $veMPH. Read more and discuss your thoughts on our Discord before voting for this snapshot 🗳⚡️ https://vote.88mph.app/#/proposal/0x83842c17f0bb039871a67daee32b74da903cad9ee96689648df26ec7f281fc48
5 Jul 2022, 22:49 UTC249 viewsread 10 August 2026
https://discord.gg/GXJfxbKP
5 Jul 2022, 22:49 UTC228 viewsread 10 August 2026
8RC#10 - Replace bnMPH with an 80MPH-20WETH pool on Balancer or MPH as the locked asset for veMPH. Please read and post your comment directly on the 💬 chat here or on our Discord https://hackmd.io/@guilaumepalayer/r1wMZF-s9 This proposal will be available on Snapshot for voting between July 10 and July 12, 2022 3:00 PM CET. Only xMPH holders are allowed to vote.
20 Jun 2022, 22:44 UTC310 viewsread 10 August 2026
Meanwhile we don't stop shipping new innovative products for the true DeFi believers like you guys, please check our announcement https://twitter.com/Timeless_Fi/status/1538997539529142273
Showing the 12 most recent of 20 posts we hold for @join88mphAnn. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“88mph announcements” (@join88mphAnn), 37 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/join88mphAnn.
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.