on record

Program Stats

mainnet·last 24h·232 programs·42 new · 190 upgrades

Deploys over timei

05010023:0004:0009:0014:0019:00

Frameworksi

anchor4044% → 50%▲ +6pp
native2330% → 27%▼ -3pp
pinocchio2026% → 23%▼ -3pp

Categoriesi

DEX
4
STAKING
3
LAUNCHPAD
3
LENDING
0
PERPS
1
BRIDGE
1
ORACLE
4
NFT
1
GOV
0
AIRDROP
0
TOKEN
0
INFRA
0
DEFI
4
UNKNOWN
62

Integrationsi

SPL Token
49
Token-2022
32
Associated Token
18
Pump.fun
7
Orca Whirlpool
5
Meteora DLMM
5
Jupiter
5
Raydium AMM
4
Raydium CLMM
4
Metaplex Metadata
2

Identityi

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

Lineagei

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

Controli

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

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.
0
untracedCouldn't reach the funding origin.
83

Recycled — byte-clone redeploysi

14.3%of today's 42 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.
6
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
4
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
10
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 24h · updated 2026-09-14 22:49 UTC