Open Data

We publish the raw layer our scanner runs on. Two datasets, JSON and CSV — no signup, no API key, no paywall. Take them, mirror them, ship them inside your own product. You do not need to credit us.

Repository: github.com/scytheradar/scythe-radar-datasets

1. Sanctioned addresses — 492 addresses, 12 chains

Addresses published on the OFAC SDN list, resolved to the chain each one actually lives on. Most public "sanctioned address" lists stop at Bitcoin and USDT. This one keeps the long tail, because a screening stack that only covers ERC-20 is screening a fraction of the surface.

Total: 492. Every entry keeps the source address exactly as published — we resolve the chain, we do not rewrite the address.

2. Rug-pull archive — 86 documented cases

86 tokens on BNB Chain that either went to zero or had their liquidity pool drained to nothing. Each row carries the contract address, so you can open a block explorer and verify every claim yourself. No "trust us" — just addresses.

Each record ships these fields:

• contract_address — the token contract, verifiable on-chain
• chain and status — e.g. "LP drained" or "went to zero"
• peak_tvl and current_pool — peak liquidity versus what remains today
• mechanism — how the drain was executed
• early_warning — the signals that were publicly visible before it happened
• detail_url — link to the full autopsy report on this site

One example of why both numbers are published side by side: $LAX peaked with $45.9M in its pool. At the time of documentation the main pool held $5. That is not a typo — that is the whole point.

Full reports for every case are indexed at Death Files.

3. Two things we deliberately did not put in

Attribution to individuals. Some cases look like a common operator behind them — but "looks like" is not evidence. We publish what the chain shows, not who we suspect.

A single "total lost" figure. Peak TVL, residual liquidity and single cash-outs are different quantities. Merging them into one headline number produces something that is arithmetically wrong. We would rather publish the parts than a number that does not survive checking.

4. What it is for

• Compliance screening — load the sanctions list into your own pipeline, cross-check inbound or outbound transfers.
• Research — study drain mechanisms and the gap between a token's peak and its present state.
• Tooling — build alerts, dashboards or datasets on top of it. CC0 means no attribution requirement and no license friction.

5. Verify it yourself

Nothing here requires trusting us:

• Contract addresses — paste any of them into a block explorer.
• Sanctions entries — compare against the OFAC SDN list published by the U.S. Treasury.
• File integrity — the repository is public and every change is a commit.

6. Get the data

• Repository: github.com/scytheradar/scythe-radar-datasets
• Sanctions list: JSON · CSV
• Rug-pull archive: JSON · CSV

This is the static layer. On top of it we run honeypot detection, same-name impostor checks and multi-hop tracing toward cash-out points — see On-Chain Detective and the B2B API. Data provenance for everything else on this site is documented on Data Sources.