solana-launch-forensics
Read-only forensics for pump.fun style token launches. Standard library only — no
API key, no pip install of crypto SDKs, no wallet connection.
It answers four questions from public chain data alone:
- Which mints did a wallet create?
- How fast, and did any share a transaction?
- How did the SOL leave, and did the payouts repeat one size?
- Which mints belong to the same operator, and what is the evidence?
Every output line is traceable to a signature you can paste into an explorer. The tool never guesses intent.
$ launchforensics scan GtTg74Zp…4W14 --limit 60
wallet GtTg74Zp…4W14
scanned 60 transactions
creations 13
window 9m 11s
created (UTC) batch mint tx
2026-11-16 12:22:27 1 C53a9Fc6…pump ggoZiaudL3jx..6tiw
2026-11-16 12:23:07 1 CqAjDktv…pump 5BHGkpzjtjUU..RLY3
...
Install
git clone https://github.com/tdkrHuang/solana-launch-forensics
cd solana-launch-forensics
python3 -m launchforensics --help
Python 3.9+. Nothing to install.
Optionally, as a command:
pip install -e .
launchforensics --help
Commands
scan <wallet> — mints created by a wallet
launchforensics scan <WALLET> --limit 400 --out wallet.json
| Flag | Meaning |
|---|---|
--limit N |
transactions to inspect (max 1000, newest first) |
--out FILE |
write the full JSON result |
--json |
print JSON to stdout |
Reports creations, the time window between the first and last creation, and any
transaction that created more than one mint.
tx <signature> — one transaction, decoded
launchforensics tx <SIGNATURE>
Resolves which program emitted each Program log: line by walking the
invoke / success stack, so pump.fun operations are counted separately from
token-program noise. Output includes signers, fee, pump instruction counts,
referenced mints, SOL transfers and repeated equal-size outflows.
flows <wallet> — repeated equal-size payouts
launchforensics flows <WALLET> --limit 200 --min-sol 0.01 --across-tx
Groups SOL transfers leaving the wallet by exact lamport amount. Scripted splitters tend to pay one number to many destinations; humans rarely do.
| Flag | Meaning |
|---|---|
--across-tx |
group identical amounts across transactions (default: within one tx) |
--min-count N |
minimum distinct destinations to report |
--min-sol X |
ignore dust below X SOL |
Real output — nine wallets received the identical 486,609,148 lamports:
$ launchforensics flows GtTg74Zp… --limit 150 --min-sol 0.4 --across-tx
0.486609148 SOL x 9 destinations (9 txs)
-> 2c5o9kpr…vJq4
-> 3EyicXms…hPb
-> 6NmwtSZ5…M2N
...
--across-tx is the mode that matters for payout analysis: a splitter usually pays
one destination per transaction, so a within-transaction view finds nothing.
cluster <wallet> — mints that share evidence
launchforensics cluster <WALLET> --limit 400
Builds a graph whose nodes are wallets and mints and whose edges are individual, signed facts:
| Edge | Meaning |
|---|---|
created |
the wallet paid for the transaction that created the mint |
swept |
the wallet collected that mint's creator fee — only the creator can |
funded |
SOL moved from one wallet to another |
Connected components containing at least two mints are printed together, with the signature of every link, so any single claim can be checked on an explorer.
| Flag | Meaning |
|---|---|
--min-mints N |
ignore components below N mints (default 2) |
--max-mints N |
mints printed per cluster (default 25) |
--max-edges N |
evidence lines printed per cluster (default 25) |
--out FILE |
write the full JSON result |
--json |
print JSON to stdout |
Example output (addresses shortened):
wallet GtTg74ZpUb…4W14
scanned 5 transactions
evidence created 3, funded 1, swept 3
clusters 1 (minimum 2 mints)
cluster 1: 3 mints, 2 wallets
links created 3, funded 1, swept 3
window 2025-11-16 04:50:00 -> 2025-11-16 05:16:21 (26m 21s)
wallets
- GtTg74ZpUb…4W14
- 8fJ1XKz6Yb…QwZa
mints
- EGX8MJT8wd…pump
- 2ZZhunwtYT…pump
- 2GoDADTFmh…pump
evidence
created GtTg74ZpUb…4W14 -> EGX8MJT8wd…pump create1
funded 8fJ1XKz6Yb…QwZa -> GtTg74ZpUb…4W14 0.05 SOL fund1
swept GtTg74ZpUb…4W14 -> EGX8MJT8wd…pump sweep1
A control wallet — one that created a single token and collected nothing — prints
No cluster above the threshold. That silence is the point: the command reports
links it can sign, not wallets it finds interesting.
Shared funding is a link, not proof. Exchanges and faucets fund thousands of
unrelated wallets, so read the funded edges with that in mind; created and
swept are the stronger links because both require control of the wallet.
Dataset
datasets/clusters.jsonl collects reproducible cluster records: the seed wallet,
the exact command, the scan bound, the evidence counts and a confidence grade.
The schema is documented in datasets/SCHEMA.md.
python3 tools/build_dataset.py --seeds datasets/seeds.json --limit 200
python3 tools/build_dataset.py --seeds datasets/seeds.json --dry-run
Grading is by the weakest link used to join the mints:
| Grade | Condition |
|---|---|
high |
at least one swept edge — only a creator can collect the fee |
medium |
two or more created edges from one wallet |
low |
joined only by funding transfers (dropped by default) |
Records are keyed by a hash of their mints, so re-running updates instead of duplicating, and a rate-limited run keeps what it already wrote.
What it correctly distinguishes
Two traps that produce wrong conclusions:
1. Program log: lines carry no program id.
A pump.fun CreateV2 fans out into Token-2022, which logs its own
Instruction: InitializeMint2. Naive substring counting reports two creations per
launch. This tool attributes logs through the invoke stack, so create_count
returns 1.
2. Touching a mint is not creating it.
A creator-fee sweep references seven mints and contains zero creations:
$ launchforensics tx zWcwg1pBsstXjKUw…whEq
pump ops SweepCreatorFee x7, CollectCreatorFeeV2
creates 0
mints 7 referenced
That distinction matters: a sweep across seven mints proves one wallet controls the creator-fee accounts of all seven. Calling it "seven launches in one transaction" would be wrong, and a reviewer will check.
Output schema
scan writes:
{
"wallet": "...",
"scanned_transactions": 400,
"creation_count": 27,
"window_seconds": 2350,
"creations": [
{
"mint": "...pump",
"signature": "...",
"slot": 470014561,
"block_time": 1763268569,
"batch_size": 1
}
],
"batch_transactions": []
}
cluster writes:
{
"wallet": "...",
"scanned_transactions": 400,
"edge_counts": {"created": 84, "funded": 12, "swept": 61},
"cluster_count": 2,
"clusters": [
{
"mints": ["...pump", "...pump"],
"wallets": ["..."],
"links": {"created": 84, "funded": 12, "swept": 61},
"first_block_time": 1763268569,
"last_block_time": 1763272285,
"edges": [
{"type": "created", "wallet": "...", "mint": "...pump", "signature": "..."}
]
}
]
}
Limits, stated plainly
-
Public RPC is rate limited. Default pause is 0.35 s and requests retry with backoff.
scanskips individual failed transactions and reportsfailed_transactionsinstead of aborting. If you see many failures, switch endpoint:launchforensics --rpc https://solana-rpc.publicnode.com scan <WALLET> --limit 400
For serious volume, point
--rpc(orSOLANA_RPC_URL) at your own node. -
--limitcaps history.scanreads newest-first; a wallet older than the window will appear to have fewer creations. Results sayscanned_transactionsso the bound is visible. -
pump.fun mints are detected by the
pumpsuffix. Non-pump SPL mints are only found when the RPC returns parsedinitializeMintinstructions. -
No price or PnL data. Deliberately. Prices come from third-party APIs with their own reliability; this tool only reports what the chain itself records.
-
Endpoints disagree. Some public RPCs return an empty signature list for addresses they do not index — including wallets that are active.
scanwill reportno signatures returned. Confirm on a second endpoint before treating a wallet as inactive, and say which endpoint you used. -
Not a verdict. Repeated equal-size payouts and batched creations are patterns, not proof of wrongdoing.
Paid reports
Reading the code is free. If you need this applied to a specific wallet — with the funding chain, payout reconstruction and a PDF you can hand to a community, a lawyer or an exchange — I write those reports with this tool:
- Lite $99 — one wallet, 48h
- Standard $299 — up to 5 wallets, 72h
- Deep $699 — up to 15 wallets, legal appendix, 5 business days
Every claim carries a signature. Sample report (real case, 96 launches): docs/sample-report.md
Tests
python3 -m pytest -q
Fixtures in tests/fixtures.py mirror real responses, including a versioned
transaction without message.header and a Token-2022 InitializeMint2 nested
inside a pump.fun call. tests/test_cluster.py covers the graph rules: a single
mint is never a cluster, shared funding joins two wallets, a sweep joins mints to
the sweeper, and duplicate links collapse without duplicating mints.
License
MIT
Metadata
Release files for solana-launch-forensics 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| solana_launch_forensics-0.2.0.tar.gz | 27.4 kB | Without provenance | Details for solana_launch_forensics-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| solana_launch_forensics-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for solana_launch_forensics-0.2.0-py3-none-any.whl |
Total release size: 49.7 kB
Release files / solana_launch_forensics-0.2.0.tar.gz
| Download URL | solana_launch_forensics-0.2.0.tar.gz |
|---|---|
| Size | 27.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eda78158e1e2002c6a700a52a3ef0e45fac9b2c63a552d66dbbdebbced8f0afe
|
|
BLAKE2b-256 checksum How to use checksums |
108832d24c52b303455c8568cdefd8082a64b8b5f9da7dc8328c10d244953e1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / solana_launch_forensics-0.2.0-py3-none-any.whl
| Download URL | solana_launch_forensics-0.2.0-py3-none-any.whl |
|---|---|
| Size | 22.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7cc1fd9bbabee1b8a29280615f3e1caf7c130d9afc5b6c3b9f5bdf8a553c21a
|
|
BLAKE2b-256 checksum How to use checksums |
54c78fb02514aa4059abf36de242cc3b5c3041908935bdaceeffd44027dc93c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for solana-launch-forensics 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.