on record

Program Stats

mainnet·last 7d·1,132 programs·511 new · 621 upgrades

Deploys over timei

012525011/711/911/1011/1211/13

Frameworksi

native26148% → 31%▼ -17ppanchor21027% → 38%▲ +12pppinocchio15919% → 30%▲ +11pp
unknown256% → 1%▼ -5pp
anchor v200% → 0%→ +0ppquasar00% → 0%→ +0pp

IDL, security.txt, verifiedi

IDL
8%
security.txt
7.4%
verified build
2.4%
all three
1%

Categoriesi

DEX
22STAKING
20LAUNCHPAD
7LENDING
6PERPS
4BRIDGE
18ORACLE
4NFT
3GOV
4AIRDROP
0TOKEN
1INFRA
3DEFI
16
UNKNOWN
547

Integrationsi

SPL Token
244
Token-2022
175
Associated Token
83
Pump.fun
66
Meteora DLMM
39
Raydium CLMM
32
Orca Whirlpool
32
Raydium AMM
26
Metaplex Metadata
19
Jupiter
12

Identityi

namedA project name was recovered from the binary.
212
has repoA source-code repo was found in the binary or a verified build.
6
opaqueNo name, repo, or security.txt — anonymous bytecode.
442

Lineagei

novelNo known code relative on record — genuinely new code.
1variantLoosely similar to a known program, but not a direct copy.
592fork≥60% code match to a known program — a fork or close derivative.
62

Controli

mutableHas an upgrade authority — the deployer can still replace the code (including to rug).
604
frozenUpgrade authority is null — the code can never be changed by anyone.
51verified buildThe on-chain bytecode reproduces from public source code.
6

Build machinei

MacBuilt with the macOS platform-tools download, or on a Mac home folder.
89
LinuxBuilt with the Linux download. Includes Docker builds.
172
no clueNo machine paths left in the binary: stripped or remapped at build time.
394

Fundingi

known entityDeployer was funded from a labeled exchange or bridge.
0
traced funderFunded from a specific wallet we could trace, but not a labeled entity.
1
untracedCouldn't reach the funding origin.
654

sBPF versioni

v340443% → 30%▼ -13pp
v2292% → 3%→ +2pp
v160% → 1%→ +1pp
v069356% → 66%▲ +10pp

Recycled — byte-clone redeploysi

11.4%of today's 511 new deploys are byte-clone redeploys, not new code
redeploysNew deploys that are byte-clones of known code — same program, fresh id. A fact, not a judgment.
58
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
18
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
565
What's a throwaway bot?

A disposable on-chain program a trader deploys to run one strategy — almost always sniping new Pump.fun token launches — then closes minutes later to reclaim its rent, redeploying under a fresh id for the next run.

Why a program at all?

Sniping means "buy the instant the pool exists, atomically, or abort" — you can't do that reliably from a wallet. A tiny custom program bundles the whole attempt (and often multi-venue routing) into a single instruction that either lands complete or reverts.

Why thousands of failed transactions?

That's the race. The bot fires on every launch; most attempts lose the block or the token rugs, so they revert. The failures are the strategy — spray for the few that land.

Why redeploy and close?

The ~0.2 SOL of rent is refundable on close, and a fresh program id sidesteps any blocklist or reputation built against a known address. Cheaper and stealthier to burn identities than to keep one — so one operator can wear dozens of "new program" identities in a day.

How On Record catches it

Exact-bytecode dedup (same sha256 = same bot) collapses the redeploys into one cluster; lifecycle tracking sees the deploy → close; the failed-tx count confirms the intent. No explorer distinguishes "new protocol" from "same bot, 30th identity today" — that's a novelty-definition problem, which is exactly what this radar solves.

last 7d · updated 2026-11-14 09:11 UTC