https://t.me/PumpFunBundler/281
Signed Chipper🇨🇭

Channel
@SOLDevAnnouncements
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
80subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002076356163 |
|---|---|
| Type | Channel |
| Username | @SOLDevAnnouncements |
| Description | Other channels: @PumpFunBundler Community: @SOLDevCommunity for info and help @chipperg |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/SOLDevAnnouncements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 19:02 | 80 | no change |
| 7 Aug 2026, 12:59 | 80 | first reading |
19 posts held, back to 23 August 2024 — 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 pageof 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 19 posts for this entry, the most recent from 3 February 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
https://t.me/PumpFunBundler/281
Signed Chipper🇨🇭
SOL Developers | Scripts and more pinned a photo
🏎 Delayed v3 just got faster! I have updated my v3 backend and wrote a custom prediction logic to calculate/estimate how much the curve will progress with more buys, this allows for quicker buy cycles. So you will see v3 working much faster overall now 😁 🧪 Experimenting this new logic with more than 24 wallets as well, so stay tuned for that
Signed Chipper🇨🇭
SOL Developers | Scripts and more pinned a photo
🐢 Delayed v2.1 Release You can now configure block 0 buyers (guaranteed before any sniper) in the delayed v2 version to prevent snipers or dump on them. This is disabled by default. The first X buyers are taken and not bought with in the delayed bundle. (need help DM me) Example: https://pump.fun/6hP2zxqbgwuu8HJT8F3LTpnM78r7TXqUnL2fcnZqpump (in this example i set it to 5 buyers in the same block) Also fixed some i…
Signed Chipper🇨🇭
Introducing the Solana Tweet Sniper Snipe tokens on pump.fun & Raydium automatically from a Twitter post. Track influencers, shillers, or any random accounts on Twitter/X, and automatically buy & sell their shilled tokens based on your settings. Features: - Track any account on Twitter/X (unlimited at a time) - Set a custom buy amount to snipe with - Set the amount gained in % to auto sell - Easy to use JS program …
Signed Chipper🇨🇭
Small but amazing update 🔥 - delayed v3 dev sell is now guaranteed :) reworked the backend to make it work - delayed v2 bundle buy is now 1-2 seconds faster on average. with a decent slippage it is pretty much guaranteed to go through. (example: https://pump.fun/96vdbAqkWRdZbDjLJUwy4WaPacBS6TzcdBd8FHEHpump) IMPORTANT to remember with v2 delayed is to wait a few seconds after extending your LUT when generating the …
Signed Chipper🇨🇭
Hearing people getting drained on trading bots like bonkbot and solana trading bot due to a potential telegram mobile exploit. Disconnect telegram mobile from your PC/laptop to be safe, stay safe out here ❤️
Signed Chipper🇨🇭
🌝 Moonshot Sniper is almost ready! Early bird discount ends at time of launch, no exceptions! Some of the features -> Option to only buy when there are no snipers -> Configure the amount of snipers you want to allow (my example i set it to 1) -> Auto-retry txs if they fail due to like slippage up to 3 times -> Track & snipe coins based on name, symbol or dev address Pre-purchase it for 15 SOL at @ChipperAccountBot …
Signed Chipper🇨🇭
The Moonshot Mass Sniper is now in early sale You can pre-order it for 15 SOL instead of 25 SOL! This early discount ends when it releases, might be today 👀 Pre-order via @ChipperAccountBot or DM me @chipperg
Signed Chipper🇨🇭
For those interesting in the upcoming moonshot bundler/sniper please join the announcement channel here https://t.me/MoonshotBundler
Signed Chipper🇨🇭
https://t.me/MoonshotBundler/7 Polling interest for a moonshot sniper
Signed Chipper🇨🇭
Showing the 12 most recent of 19 posts we hold for @SOLDevAnnouncements. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“SOL Developers | Scripts and more” (@SOLDevAnnouncements), 80 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/SOLDevAnnouncements.
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.