Galt Adds 30 Days of Deployer History to Larpcheck

Galt, the developer posting as @0xgalt on X, said Larpcheck had added 30 days of past token launches to its deployer page and fixed trading for Pumpfun coins paired with another Pumpfun coin. The November 1 update combines more launch history with support for a pairing type that can trip up third-party trading interfaces.

For a trader researching a fresh token, the history change is the more useful starting point: it provides earlier launches to inspect alongside the current coin. A deployer's previous projects can raise questions that a single price chart cannot answer, although launch history alone does not establish who controls every related wallet.

backfilled "deployers" page with 30 days of launches

— Galt (@0xgalt) November 1, 2026

Why the pairing fix matters

Pumpfun coins do not all trade directly against SOL or USDC. The platform's pairing documentation allows an eligible coin launched against a supported asset to become the pair asset for another coin.

Its example is straightforward: a coin launched against SOL may become the quote asset for a second coin. The second coin cannot automatically become the basis for another layer of pairings. Those rules give external tools more cases to handle than a simple token-to-SOL trade.

Galt said Larpcheck previously could not trade coins in that secondary-pair setup. His announcement describes a fix in Larpcheck, rather than a change to Pumpfun's own contracts.

More context before the trade

The same update lists more consistent market-cap displays, direct trading links from bots and faster chart availability for new coins. These are the developer's reported changes; BTC PEERS did not execute a trade to test the routing fix.

The public terminal, checked on November 2, displays Pumpfun launches alongside separate assessments of their narrative and holder distribution, with timestamps showing when checks were made. That separates what a token claims to represent from how its supply is distributed.

The backfilled history adds another layer to that workflow: checking what a deployer launched before, rather than treating every new ticker as a clean slate.