on record

Program Stats

mainnet·all·since Jul 9, 2026i·7,807 programs·3,616 new · 4,191 upgrades

Deploys over timei

0500010000archiverecord startsMar '22Mar '23Feb '24Jan '25Dec '25

Frameworksi

anchor392459% → 46%▼ -13pp
native206222% → 30%▲ +8pp
pinocchio156618% → 22%▲ +5pp
unknown1031% → 2%→ +0pp
anchor v2210% → 0%→ +0pp
quasar10% → 0%→ 0pp

IDL, security.txt, verifiedi

IDL
10.5%
security.txt
8.8%
verified build
3.9%
all three
1%

Categoriesi

DEX
480
STAKING
323
LAUNCHPAD
155
LENDING
85
PERPS
85
BRIDGE
115
ORACLE
87
NFT
82
GOV
53
AIRDROP
21
TOKEN
48
INFRA
89
DEFI
477
UNKNOWN
5577

Integrationsi

SPL Token
3938
Token-2022
2585
Associated Token
1262
Pump.fun
645
Meteora DLMM
404
Raydium CLMM
370
Orca Whirlpool
361
Metaplex Metadata
308
Raydium AMM
285
Jupiter
172

Identityi

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

Lineagei

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

Controli

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

Build machinei

MacBuilt with the macOS platform-tools download, or on a Mac home folder.
2106
LinuxBuilt with the Linux download. Includes Docker builds.
2746
no clueNo machine paths left in the binary: stripped or remapped at build time.
2801
not readNo stored bytecode to read yet.
24

Fundingi

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

sBPF versioni

v313210% → 23%▲ +23pp
v2770% → 1%→ +1pp
v1260% → 0%→ +0pp
v029991% → 52%▲ +52pp
not read338499% → 23%▼ -76pp

Recycled — byte-clone redeploysi

7.4%of today's 3,616 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.
267
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
30
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
11900
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 all · updated 2026-11-14 09:29 UTC