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

Channel
Pump Developer Updates
@pump_tech_updates
On this record: Growth · Engagement · Posts · Citations · Cite this entry
6,613subscribers
+20 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 |
|---|---|
| Type | Channel |
| Username | @pump_tech_updates |
| 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 | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/pump_tech_updates |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:53 | 6,613 | +8 |
| 11 Aug 2026, 12:42 | 6,605 | +12 |
| 7 Aug 2026, 16:01 | 6,593 | no change |
| 7 Aug 2026, 15:54 | 6,593 | first reading |
Engagement
20 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 8 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 64.9%
- avg views ÷ 6,613 subscribers
- Avg views / post
- 4,290
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 20 held
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 20 July 2026 |
|---|---|
| Posts held | 20 (1 September 2025 – 20 July 2026) |
| Views total | 4,290 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 02:59 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.
Recent posts
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] •…
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…
* 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
# 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.
Citation-graph rank
Citation-graph rank — 308,803 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Pump Developer Updates” (@pump_tech_updates), 6,613 subscribers as measured 14 August 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.