We’ve recently add changes to our swapEvents data. If you were parsing it, please use the latest IDL.

Channel
Jupiter Dev Notifications
@jup_dev
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,361subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001706087112 |
|---|---|
| Type | Channel |
| Username | @jup_dev |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/jup_dev |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 11:45 | 2,361 | -2 |
| 12 Nov 2026, 23:10 | 2,363 | -2 |
| 8 Nov 2026, 07:06 | 2,365 | -2 |
| 2 Nov 2026, 04:27 | 2,367 | -3 |
| 30 Oct 2026, 01:28 | 2,370 | -5 |
| 26 Oct 2026, 17:46 | 2,375 | -1 |
| 23 Oct 2026, 07:34 | 2,376 | +1 |
| 20 Oct 2026, 15:59 | 2,375 | +5 |
| 17 Oct 2026, 21:34 | 2,370 | -1 |
| 14 Oct 2026, 17:57 | 2,371 | -3 |
| 11 Oct 2026, 09:38 | 2,374 | +2 |
| 5 Oct 2026, 06:57 | 2,372 | -1 |
| 27 Sept 2026, 03:18 | 2,373 | +11 |
| 15 Sept 2026, 10:58 | 2,362 | +4 |
| 11 Sept 2026, 21:57 | 2,358 | +1 |
| 7 Sept 2026, 01:38 | 2,357 | +3 |
| 2 Sept 2026, 11:04 | 2,354 | -3 |
| 30 Aug 2026, 07:16 | 2,357 | +1 |
| 27 Aug 2026, 02:52 | 2,356 | -1 |
| 24 Aug 2026, 08:42 | 2,357 | first reading |
Engagement
20 posts held, back to 10 March 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Suggested events endpoint deprecation Hi all, heads up for teams using the Prediction Market API suggested events endpoint. We are deprecating the wallet-specific suggested events endpoint on Friday, 10 July 2026: GET https://api.jup.ag/prediction/v1/events/suggested/{walletAddress} For suggested events, use the category-based endpoint instead: GET https://api.jup.ag/prediction/v1/events/suggested Supported que…
Final reminder on the Developer Platform migration (portal.jup.ag → developers.jup.ag) The cutoff is 7th july 9am UTC. if you haven't claimed your legacy org and set up billing on the new platform yet, do it before then or your rate limits drop to free tier (1 RPS). set up here: developers.jup.ag/portal Reach out to @anmoldotsol / @Yankee0x for any questions
Update The Content API deprecation is now in effect. Stated endpoints are no longer publicly accessible and will return a 403 If this broke an existing integration, reach out to @nineyoi and we'll help you sort it out.
JupiterZ integrator fees on Swap API Hi all, quick update for teams using the /order path of the Swap V2 API Integrator fees are now supported on JupiterZ/RFQ routes. You can pass referralAccount + referralFee like any other /order request and still receive JupiterZ/RFQ quotes when it is the best eligible route Relevant docs: - Changelog - Referral fees setup/usage
Content API Deprecation Notice Heads up, we are deprecating the beta Content API on 1 July 2026. - /tokens/v2/content - /content/feed - /content/cooking In the coming months, we will be sharing more about an update to the Tokens API, including a comprehensive replacement for the Content API. If you currently rely on/or were planning to use the Content API, reach out to @9yointern. We'd love to hear your feedback a…
Hi all, quick heads up for teams working with Jupiter's Prediction Markets API. We're shipping the next step of the fractional contracts migration on Thursday, 4 June 2026 at 6:00 AM UTC (2:00 PM SGT, UTC+8). No downtime is expected. What's happening The previous migration on 27 May was step one. On-chain storage moved to micro-contracts and the new *Micro / *Decimal fields became available. This Thursday is step …
Prediction Markets API maintenance complete ✅ The fractional contracts migration is done. Trading, claims, and settlement have all resumed. If you haven’t already, please migrate to the new contractsMicro / contractsDecimal fields within the next week, the legacy whole-contract fields (contracts, filledContracts, totalContracts) will be deprecated after that. If you're facing any issues post maintenance, feel free…
Hi all, quick heads up for teams integrating with Jupiter Prediction Markets API. We’re shipping a coordinated migration to add fractional contracts support, scheduled for Wednesday, 27 May 2026 at 6:00 AM UTC (2:00 PM SGT, UTC+8). Estimated downtime: up to ~4 hours (may complete earlier if everything goes smoothly). What’s changing Contract quantities are migrating from whole-contract units to micro-contract uni…
🛠 Metis V8 is live Focused on closing Quotation–Execution Drift, the gap between the price you're quoted and what actually lands. • Route splits finalized onchain at execution, instead of ~400ms before • Sub-2 slot state freshness on every routing decision (gRPC streaming + own validator shreds) • Landing via Beam, direct to validator leaders, p95 0–1 slots • Rapid Quotation: <100ms quotes that skip marginal optimi…
Hi everyone, we apologize for a brief outage that caused intermittent transaction submission and landing issues across Jupiter Spot products and APIs, including Swap, Limit Order, and DCA. The issue appears related to DNS resolution affecting our transaction landing infrastructure. We deployed a hotfix around ~45 minutes ago, and services appear to have recovered. We’re continuing to monitor and investigate the root…
Hi all, quick heads up for teams using Trigger API V2. We’re shipping a breaking request validation change for price-order deposits on Thursday, May 14, 2026 at 4:00 AM UTC. If your integration calls: POST https://api.jup.ag/trigger/v2/deposit/craft please make sure you send both of these fields in the request body: { "orderType": "price", "orderSubType": "single" } Set orderSubType based on the order: 1.…
Showing the 12 most recent of 20 posts we hold for @jup_dev. 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.
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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“Jupiter Dev Notifications” (@jup_dev), 2,361 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/jup_dev.
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.