Telegram RegisterThe public register of Telegram
Telegram profile photo for Pump Developer Updates

Channel

Pump Developer Updates

@pump_tech_updates

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

6,713subscribers

+120 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002286234018
TypeChannel
Username@pump_tech_updates
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/pump_tech_updates

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 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 why it has no browse page of its own yet.

Growth

6,5936,7136,6537 August 2026 — 6,593 subscribers7 August 2026 — 6,593 subscribers11 August 2026 — 6,605 subscribers14 August 2026 — 6,613 subscribers18 August 2026 — 6,616 subscribers21 August 2026 — 6,626 subscribers25 August 2026 — 6,625 subscribers28 August 2026 — 6,654 subscribers31 August 2026 — 6,663 subscribers3 September 2026 — 6,671 subscribers8 September 2026 — 6,697 subscribers13 September 2026 — 6,713 subscribers7 August 202613 September 2026
12 measurements spanning 37 days, net +120. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 6,575–6,731 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 06:406,713+16
8 Sept 2026, 23:596,697+26
3 Sept 2026, 16:216,671+8
31 Aug 2026, 09:256,663+9
28 Aug 2026, 10:346,654+29
25 Aug 2026, 02:366,625-1
21 Aug 2026, 11:456,626+10
18 Aug 2026, 05:236,616+3
14 Aug 2026, 19:536,613+8
11 Aug 2026, 12:426,605+12
7 Aug 2026, 16:016,593no change
7 Aug 2026, 15:546,593first reading

Engagement

20 posts held, back to 1 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pages 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 20 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 Jul 2026, 13:50 UTC≈4,720 viewsread 20 August 2026

Hi all, The update above of enabling non zero virtual quote reserves will be now at 10am EST on july 21, 2026

15 Jul 2026, 19:26 UTC≈7,220 viewsread 20 August 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

18 May 2026, 20:37 UTC≈12,700 viewsread 20 August 2026

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

7 May 2026, 17:13 UTC≈11,600 viewsread 20 August 2026

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

22 Apr 2026, 21:07 UTC≈10,600 viewsread 20 August 2026

━━━━━━━━━━ 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

24 Mar 2026, 16:20 UTC≈8,480 viewsread 20 August 2026

## 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.

13 Mar 2026, 15:41 UTC≈8,820 viewsread 20 August 2026

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

5 Mar 2026, 19:18 UTC≈8,930 viewsread 20 August 2026

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

26 Feb 2026, 15:22 UTC≈11,500 viewsread 20 August 2026

🚨 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] •

17 Feb 2026, 18:30 UTC≈7,810 viewsread 20 August 2026

Cashback Rewards allows token creators to create coins with "cashback" enabled which redirects the creator fee to the users. Each user would get the creator fee on their swap volume as cashback rather than paying that fee to the coin creator. This is a backwards compatible change, so if you do not update to the latest IDsL/SDKs it will work but cashback will not be enabled. ## Integration You can also use our Type

9 Jan 2026, 18:16 UTC≈9,030 viewsread 20 August 2026

* pump-public-docs has been updated with all the latest IDLs * SDKs updated at: https://www.npmjs.com/package/@pump-fun/pump-sdk and https://www.npmjs.com/package/@pump-fun/pump-swap-sdk

9 Jan 2026, 17:38 UTC≈10,100 viewsread 20 August 2026

# Creator Rewards Sharing - Developer Update ## Overview Creator Rewards Sharing allows token creators to split their creator fees with multiple recipients. Instead of all fees going to a single wallet, creators can configure a list of shareholders with custom percentage splits. ## Dynamic creator_vault Address This update will make some coins' creator_vault point to new addresses. To ensure buy and sell instructi

Showing the 12 most recent of 20 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.

Forward network

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.

Mentions

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.

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 13 September 2026 — this entry's latest reading, not the date you are reading this.

“Pump Developer Updates” (@pump_tech_updates), 6,713 subscribers as measured 13 September 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.