Channel
@pump_tech_updates
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
6,890subscribers
+297 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002286234018 |
|---|---|
| Type | Channel |
| Username | @pump_tech_updates |
| Description | Updates regarding all technical related changes that may affect integrations |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 2 times, most recently 1 November 2026 |
| On Telegram | t.me/pump_tech_updates |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Oct 2026, 21:36 | 6,890 | +8 |
| 26 Oct 2026, 10:58 | 6,882 | +11 |
| 23 Oct 2026, 08:54 | 6,871 | +12 |
| 20 Oct 2026, 18:46 | 6,859 | +14 |
| 17 Oct 2026, 07:56 | 6,845 | +11 |
| 14 Oct 2026, 15:20 | 6,834 | +28 |
| 11 Oct 2026, 04:37 | 6,806 | +46 |
| 5 Oct 2026, 01:35 | 6,760 | +37 |
| 17 Sept 2026, 04:41 | 6,723 | +10 |
| 13 Sept 2026, 06:40 | 6,713 | +16 |
| 8 Sept 2026, 23:59 | 6,697 | +26 |
| 3 Sept 2026, 16:21 | 6,671 | +8 |
| 31 Aug 2026, 09:25 | 6,663 | +9 |
| 28 Aug 2026, 10:34 | 6,654 | +29 |
| 25 Aug 2026, 02:36 | 6,625 | -1 |
| 21 Aug 2026, 11:45 | 6,626 | +10 |
| 18 Aug 2026, 05:23 | 6,616 | +3 |
| 14 Aug 2026, 19:53 | 6,613 | +8 |
| 11 Aug 2026, 12:42 | 6,605 | +12 |
| 7 Aug 2026, 16:01 | 6,593 | first reading |
23 posts held, back to 1 September 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 10 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 13 October 2026 |
|---|---|
| Posts held | 23 (1 September 2025 – 13 October 2026) |
| Views total | 10,670 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 14:07 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 3 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Hey everyone. We're going to be enabling creation of tokens to one more depth in the next few hours. Any token paired with SOL, USDC or one of the whitelisted mints from quote-control PDA are considered depth 0. Last week we enabled the creation of depth 1 coins which meant new creations were allowed paired with any Pump token with depth 0. Today we will be enabling the creation of depth 2 tokens which can be pair…
Hello everyone. Tomorrow we will be releasing new instructions and features on the pump and pump swap programs. All changes are non breaking if you had adapted to the virtual quote reserves being negative in the previous announcement. What is new? - New Pump coins can be paired with any previously created Pump coins that are paired with SOL, USDC or one of the mints in the quote control PDA. - New v3 instructions i…
Hi all, starting tomorrow, the virtual quote reserves in pump swap which is marked as i128, can be negative also. This is a heads up to make sure quoting logic handles it already from your side. More details on how to handle when its negative: https://github.com/pump-fun/pump-public-docs/blob/main/docs/NEGATIVE_VIRTUAL_QUOTE_RESERVES.md
Hi all, The update above of enabling non zero virtual quote reserves will be now at 10am EST on july 21, 2026
Hello everyone We're changing how PumpSwap (pump-amm) pool quotes must be computed. This is a breaking change: everyone who prices, quotes, or indexes PumpSwap pools will need to update their integration. We're rolling it out in two phases so you have time to adapt before it takes effect. What's changing? The Pool account now carries an additional field, virtual_quote_reserves. Quotes should be computed against th…
Hello everyone, On Thursday, May 21, 2026, we will be enabling USDC mint as a quote mint for creating and trading pump coins. * Please note that USDC-paired coins can only be traded using the new V2 instructions announced earlier. * SOL paired coins will continue to be traded in native SOL even though the quote mint needs to be passed as the wrapped SOL mint. * All legacy instructions will continue to work for SOL …
Hello everyone. We just upgraded the Bonding curve contract for a new non breaking feature. Happy to announce support of USDC as a quote mint for creating and trading Pump meme coins. As part of this upgrade, we have rolled out 3 new instructions, buy_v2, sell_v2 and buy_exact_quote_in_v2. These new instructions are meant to unify the trading interface so the same instruction can be used to trade USDC and SOL paired…
━━━━━━━━━━ PROGRAM UPGRADE ━━━━━━━━━━ Hi. We will be doing a breaking program upgrade on April 28th, 16:00 UTC, to both the pump bonding curve program and the pump swap amm program. In order to make sure your integrations do not break please see the instructions below: ━━━━━━━━━━ 8 NEW FEE RECIPIENTS ( common for both programs ) ━━━━━━━━━━ 5YxQFdt3Tr9zJLvkFccqXVUwhdTWJQc1fFg2YPbxvxeD 9M4giFFMxmFGXtc3feFzRai56W…
## One-Time Creator Reward Distribution Policy This update only affects fee-sharing configuration. Trading instructions are unchanged and do not require an upgrade. TLDR: After the first configuration, reward distribution is locked and cannot be changed. What changed: - Reward distribution can be configured only once. - You can configure it using either updateFeeShares or updateSharingConfigWithSocialRecipients. …
Hi devs — we've shipped Tokenized Agents. Tokenized Agents allow agents to collect revenue and use a portion of it for buybacks. This does not alter the trade flow — both buy and sell behavior remain the same. This is an entirely new smart contract that works on top of our Pump bonding curve and Pump AMM smart contracts. To create a tokenized agent, please use the NPM package: @pump-fun/agent-payments-sdk. After c…
Hi devs — we’ve shipped Creator Fee V2 integration guidance (docs + SDK helpers). This is not an on-chain update, but you may need to adjust your integration to correctly support all creator-fee configurations. - SDK update: @pump-fun/[email protected] (new helper functions) https://www.npmjs.com/package/@pump-fun/pump-sdk/v/1.30.0 - Docs / requirements: GitHub recipient + social fee PDA requirements https://githu…
🚨 PROGRAM UPGRADE: NEW REQUIRED ACCOUNTS 🚨 We pushed a program upgrade that requires 1 extra account for an upcoming feature on BOTH: • Bonding Curve program • Pump Swap AMM program ✅ These additions are REQUIRED for BOTH cashback + non-cashback coins. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🆕 NEW PDAs TO DERIVE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1) Bonding Curve v2 PDA • Seeds: ["bonding-curve-v2", mint] •…
Showing the 12 most recent of 23 posts we hold for @pump_tech_updates. 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.
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 2 registered channels — 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 29 October 2026 — this entry's latest reading, not the date you are reading this.
“Pump Developer Updates” (@pump_tech_updates), 6,890 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/pump_tech_updates.
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.