Channel
@GMX_Technical_Announcements
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
444subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001958738416 |
|---|---|
| Type | Channel |
| Username | @GMX_Technical_Announcements |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 7 September 2026 |
| On Telegram | t.me/GMX_Technical_Announcements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 03:05 | 444 | +2 |
| 22 Aug 2026, 13:27 | 442 | -3 |
| 14 Aug 2026, 22:58 | 445 | +1 |
| 7 Aug 2026, 23:12 | 444 | -1 |
| 6 Aug 2026, 23:32 | 445 | first reading |
20 posts held, back to 29 October 2025 — 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 23 July 2026. An engagement rate over an empty window would be a number about nothing.
17 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 64.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 11 | 64.7% | |
| ❤ | 5 | 29.4% | |
| 😢 | 1 | 5.88% |
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 7 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 17 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 29 October 2025 to 23 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.
GMX v2.2c Contracts Are Now Live GMX v2.2c contracts are now deployed on Arbitrum, Avalanche, and MegaETH. This release strengthens protocol safeguards and risk controls, while adding new capabilities for wallets, order execution, and integrations. The contracts are live. The interface and supporting integration rollout is being completed in stages. We encourage GMX integrators to review the changes and switch ove…
❤1
GMX will be carrying out another round of maintenance on selected Arbitrum V2 markets to reduce accumulated Price Impact bucket balances. This is a follow-up to the previous August 2025 activity discussed here: https://gov.gmx.io/t/updating-price-impact-buckets/4795 The withdrawal moves excess accumulated Price Impact funds from selected market buckets to the GMX DAO Treasury, while leaving sufficient balances for …
👍3
Funding Rate Configuration Update — Arbitrum GMX is standardizing the max funding rate configuration for all its Arbitrum markets, effective Thursday, 23 April. The update involves the keeper-side logic used to set the max funding ceiling on Arbitrum. This specifically covers the floor, cap, and reference-rate inputs that sit on top of GMX's adaptive funding model: the layer that determines the upper bound for fund…
❤2😢1
GMX Subsquid API — Breaking Change (Effective Today) Follow-up to our announcement on Feb 24 — the changes described below have been implemented on the main endpoint today, ahead of the original March 1 timeline. Main endpoint (updated schema): https://gmx.squids.live/gmx-synthetics-arbitrum:prod/api/graphql Backward-compatible endpoint (available until March 1): https://gmx.squids.live/gmx-synthetics-arbitrum@786…
GMX Subsquid Update: The structure of all entities that have the 'Transaction' relation will be updated in the Subsquid GraphQL API. All instances of the field transaction: Transaction will be renamed to transactionHash: String. This change affects the following entities: TradeActions, ClaimAction, SwapFeesInfo, Order, SwapInfo, PositionFeesEntity, and Distribution. The 'Transaction' entity will be removed at a s…
MegaETH Deployment Notes As the MegaETH deployment is still being tested, the maxCallbackGasLimit on MegaETH has been set to zero The nativeTokenTransferGasLimit and refundExecutionFeeGasLimit have similarly been set to zero This means that: • Callback contracts are not currently supported on MegaETH • Users will receive WETH from GMX V2 contracts only instead of ETH There will be a separate announcement when th…
Price Impact Cap Update GMX is updating the price impact cap configuration across select markets to better align with current liquidity conditions. What's changing: Major markets including BTC, ETH, and SOL will maintain the current 50-basis-point price impact maximum. For several lower-liquidity altcoin markets, caps will be adjusted to reflect the evolved liquidity landscape. Context: These updates account for o…
The updated open interest balance is now live on mainnet on all networks
IMPORTANT UPDATE: Open Interest Balance Calculation On Monday, 22 Dec, the calculation for open interest (OI) balance will be updated. ──────────────────── Current calculation • Based on the sum of the USD value of all positions at the time they were opened New calculation • Based on the sum of the notional value of positions ──────────────────── Example (current calculation) 1. BTC price = $100k User A ope…
All old V2.2 contracts have now been disabled The USE_OPEN_INTEREST_IN_TOKENS_FOR_BALANCE flag would be set to TRUE on 22 Dec 2025, please see the linked message for more details about this flag: https://t.me/GMX_Technical_Announcements/75
👍1
Max Funding Rate caps based on Reference Rates introduced for WIF, SHIB, FARTCOIN, AAVE & DOGE markets To keep funding costs reasonable for traders while maintaining attractive conditions for arbitrage funding farmers, GMX is trialing caps on the maximum funding rate on the paying side for select Arbitrum markets. The cap is determined by applying a 1.5× buffer to the median reference funding rate on exchanges like…
GMX Subgraph Migration Update Our subgraph indexer APIs have migrated from Satsuma to Goldsky. You can find the new URLs here: https://github.com/gmx-io/gmx-interface/blob/master/src/config/indexers.ts Important: Subgraph is GMX's legacy indexer API. We're actively transitioning to Subsquid (SQD), our new indexer, which may introduce some breaking changes. It is recommended to use the latest Subsquid endpoints to …
Showing the 12 most recent of 20 posts we hold for @GMX_Technical_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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“GMX Technical Announcements” (@GMX_Technical_Announcements), 444 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/GMX_Technical_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.