Two PUMP token buyback burn writeups clash, and the math stays unmerged

PUMP token buyback burn is the subject, and two secondary writeups, neither of them Pump.fun and neither of them the SEC, described a PUMP token buyback burn at the turn of October. CryptoTicker published on 1 Oct 2026. Startup Fortune is timestamped 30 Sep 2026 at 11:58 p.m., with no timezone on that stamp in this pack. Their figures clash, and this recap keeps both sets and does not blend them.

What actually happened

PUMP token buyback burn remains the subject, and start with the sourcing constraint, because it governs every number below. CryptoTicker and Startup Fortune are the two pages in the pack. The pack says flatly that neither page is Pump.fun and neither page is the SEC.

A reader who wants a company dashboard or the staff FAQ text itself will not get it from these two articles. What you get is how two outlets chose to total a buyback-and-burn story, plus one outlet's reading of a staff FAQ.

PUMP token buyback burn is the subject, and this item is filed with 3 confirmations and a hype-gas reading of 74. Three confirmations is a mid score, not a clean sweep. Hype gas at 74 says the story is running hot relative to how settled the math is.

That split is the whole point of reading it slowly. Heat is not the same thing as a single audited table.

PUMP token buyback burn stays the subject, and CryptoTicker, publishing 1 Oct 2026, says CoinGecko showed PUMP at 0.00526 euros on 1 Oct at 01:04, versus 0.00352 euros seven days earlier. CryptoTicker calls that a 49.6% week. It also cites a market cap of about 2.45 billion euros and a rank of 40.

Those price, cap, and rank lines live in CryptoTicker's piece. Startup Fortune does not reprint that euro pair or that rank in the figures this pack records, so they do not get pasted onto Startup Fortune's column.

PUMP token buyback burn remains the subject, and on supply, CryptoTicker says max supply is 1 trillion and total supply is about 830.7 billion, so about 169.3 billion have been burned, which it puts at 16.9%. That "so" is CryptoTicker's arithmetic, reported here as CryptoTicker's, not re-derived and not "corrected." Startup Fortune says 168.89 billion tokens have been burned and calls that "close to 17%."

Close is not identical. 169.3 billion and 168.89 billion disagree, even if a casual glance wants to round them into one number. This piece will not round them.

PUMP token buyback burn is the subject, and the buyback money has the same problem, and it is a worse problem because the gaps are wider. CryptoTicker cites DefiLlama at $371 million sent to holders, and it separately points to 29 Sep reports of more than $466 million in buybacks. Those are two figures inside one article, and CryptoTicker does not, in this pack, present them as the same line item.

Startup Fortune says buybacks topped $466 million. The "more than $466 million" cite and the "topped $466 million" line rhyme. The DefiLlama $371 million figure does not match either of them.

PUMP token buyback burn stays the subject, and do not average $371 million with $466 million. Do not pick the larger one because it sounds tougher.

CryptoTicker also says seven-day flows to holders were $7.3 million, and that Pump group revenue was about $16.1 million in the seven days to 29 Sep. Startup Fortune says weekly revenue was $9.7 million versus $7.5 million the week before, and separately cites $15.16 million in seven-day revenue. Read that again before you screenshot one of them. Startup Fortune's own pack of figures contains two revenue numbers, $9.7 million and $15.16 million, and CryptoTicker has a third, about $16.1 million, plus a flows-to-holders figure of $7.3 million that is not the same sentence as revenue.

PUMP token buyback burn remains the subject, and the pack says those revenue and performance figures conflict. That instruction is not a suggestion to pick a midpoint. A midpoint would be a number nobody printed.

It would look precise and be fiction. The reader-facing version is a clash list, not a compromise list.

Where the two writeups disagree

PUMP token buyback burn is the subject, and take performance first, because it is the line most likely to get cropped into a single percentage. CryptoTicker's week is a euro price move from 0.00352 to 0.00526, labeled 49.6%, tied to a CoinGecko check at 01:04 on 1 Oct. Startup Fortune's week is 38%, with a separate "as much as 20%" over 24 hours.

A 49.6% week and a 38% week cannot both be the same measurement of the same window unless someone is using a different clock, a different currency, or a different print. This pack does not give you the reconciliation. It gives you the disagreement. Stop there.

PUMP token buyback burn stays the subject, and a 20% daily move and a 38% weekly move can coexist inside one outlet's story, because they are different windows. They still do not become CryptoTicker's 49.6% week. If a later post blends the 49.6% week with the 38% week, that post has already averaged, and averaging is the move this recap refuses.

Now the burn tally. 16.9% of a 1 trillion max supply, as CryptoTicker frames its 169.3 billion, is not the same sentence as Startup Fortune's 168.89 billion and "close to 17%." You can notice they live in the same neighborhood.

PUMP token buyback burn remains the subject, and neighborhood is not identity. Quote the outlet you are using, or quote both and say they disagree. Do not weld the two burn totals into one caption as if the sources shook hands.

Startup Fortune's "close to 17%" is that outlet's rounding language. CryptoTicker's 16.9% is a tenth. If you need a figure in a caption, you need a citation next to it, and you need to leave the other figure visible. Deleting the one that fits worse in a headline is how a 3-confirmation story gets dressed up as a 6.

PUMP token buyback burn is the subject, and revenue is where casual merging does the most damage. Here are the revenue-shaped numbers exactly as the pack separates them. CryptoTicker: about $16.1 million of Pump group revenue in the seven days to 29 Sep, and $7.3 million of seven-day flows to holders.

PUMP token buyback burn stays the subject, and Startup Fortune: weekly revenue of $9.7 million versus $7.5 million the week before, and a separate cite of $15.16 million in seven-day revenue. Three revenue prints and one flows print are four lines. None of them is an average of the others.

The $7.5 million in Startup Fortune is a prior-week comparison attached to the $9.7 million weekly revenue line. It is not CryptoTicker's $7.3 million of flows to holders. The numbers sit near each other.

PUMP token buyback burn remains the subject, and near is how bad merges start. Different nouns, different outlets, different jobs in the sentence. Keep the nouns.

Buybacks versus "sent to holders" needs the same care. DefiLlama, via CryptoTicker, is cited at $371 million sent to holders. The more-than-$466-million figure is described as separate 29 Sep reports of buybacks.

PUMP token buyback burn is the subject, and Startup Fortune's "topped $466 million" is a buyback line. A holder distribution total and a buyback total are not interchangeable just because both are large and both mention the same ecosystem. This pack does not give a formula that turns one into the other.

Market cap and rank stay in CryptoTicker's column only: about 2.45 billion euros, rank 40, beside the 01:04 CoinGecko price. Max supply of 1 trillion and total supply of about 830.7 billion are also CryptoTicker's supply frame for the 169.3 billion burned figure. Startup Fortune's burned figure does not, in this pack, come with that same total-supply sentence. Do not backfill it.

What the SEC staff text is, and is not

PUMP token buyback burn stays the subject, and CryptoTicker says the SEC text in question is a staff view, not a Commission rule. It also says a central operator may fail the "no central party" condition. The staff FAQs are dated 25 Sep 2026 and were updated 28 Sep.

CryptoTicker describes them as discussing when a buyback is not by itself a securities promise. That is a narrow topic description. It is not a verdict that any specific token passed a test, and it is not a quote of the FAQ in this pack.

PUMP token buyback burn remains the subject, and this recap does not have the FAQ page as a source document. It has CryptoTicker's characterization, and it has Startup Fortune as a second outlet that is also not the SEC. A staff FAQ date and an update date are worth keeping: 25 Sep 2026, updated 28 Sep.

They tell you the text people are gesturing at is a late-September staff document. They do not tell you the Commission voted on a rule. CryptoTicker's own caveat says the opposite of a Commission rule.

PUMP token buyback burn is the subject, and "not by itself a securities promise" is doing a lot of quiet work. Even on CryptoTicker's telling, the staff discussion is about when a buyback, alone, is not that kind of promise. Alone is the word to underline.

A buyback tally, whatever size you refuse to average, does not become a legal all-clear because a staff FAQ exists. CryptoTicker adds a second caution in the same breath: a central operator may fail the "no central party" condition. That is a may, attributed to CryptoTicker, not a court result and not a Commission order.

PUMP token buyback burn stays the subject, and Startup Fortune's page is one of the two tally sources. Its URL framing is louder than CryptoTicker's caveat. This article will not adopt a "path cleared" reading, because the pack does not give that as an SEC action.

It gives you a staff-view warning from the other outlet, and it tells you neither writeup is the Commission. If the loud page and the cautious page disagree in tone, you keep the caution next to the totals. You do not let the tone pick the math.

PUMP token buyback burn remains the subject, and confirmation score 3 is what this clash looks like as a desk number. You have overlapping subject matter, buybacks and burns, and you do not have overlapping arithmetic. Hype gas 74 is what it looks like when percent-up screenshots outrun the footnotes.

The practical response is not to turn the hype down by inventing a calmer number. It is to show the columns.

What to do as a reader

PUMP token buyback burn is the subject, and open both pages and write two columns before you repeat a single percentage. Column one is CryptoTicker, 1 Oct 2026: the euro prices and the 49.6% week, the about-2.45-billion-euro cap, rank 40, the 1 trillion max and about 830.7 billion total, the about 169.3 billion burned at 16.9%, DefiLlama at $371 million sent to holders, the separate more-than-$466-million buyback reports, $7.3 million in seven-day flows to holders, and about $16.1 million in Pump group revenue for the seven days to 29 Sep.

Column two is Startup Fortune, 30 Sep 2026 at 11:58 p.m. with no timezone in this pack: buybacks topped $466 million, 168.89 billion tokens burned, "close to 17%," up as much as 20% in 24 hours and 38% over seven days, weekly revenue $9.7 million versus $7.5 million the week before, and a separate $15.16 million seven-day revenue cite. If a figure is not in that column, do not drag it across to be nice.

PUMP token buyback burn stays the subject, and when you talk about the SEC piece, use CryptoTicker's constraint. Staff view, not a Commission rule. FAQs dated 25 Sep 2026, updated 28 Sep.

The discussion, as CryptoTicker describes it, is about when a buyback is not by itself a securities promise. A central operator may fail the "no central party" condition. That is a reading from an outlet, not a paste of the FAQ, and not a ruling.

PUMP token buyback burn remains the subject, and do not average. Do not split the difference between 49.6 and 38. Do not call 169.3 and 168.89 the same burn.

Do not fold $371 million, $466 million, $16.1 million, $15.16 million, and $9.7 million into "hundreds of millions of revenue." Some of those are buybacks, one is a holder-flow cite, and the rest are revenue lines that already disagree with each other.

PUMP token buyback burn is the subject, and this is not a trade instruction. A hot hype-gas reading and a mid confirmation score are a reason to read the clash, not a reason to do anything with a token. Neither source is the project, and neither source is the regulator. Until a primary page is what you are quoting, the honest sentence is that two outlets disagree, and the disagreement is the story.

Readers who want a sourced recap that is already on the site can read DogeOS public testnet as a separate live post.