the chain writes.
the log remembers.

the data warehouse for Solana wallets and tokens. every launch we cover makes the next one legible — and what we serve is the insight, with its receipts, never the raw feed.

85,871
wallet fingerprints
18,635
with a recorded SOL sender
seen in observed trades; not a verified funding trace
8,940
seen on 2+ tokens
arrived at a later launch already known to us
1,810
coordinated
acting in timed concert, on a token we analysed
18,521
chapters published
counted from the database, 2026-10-24 15:22 UTC
— live log terminal —
LOG TERMINALLIVE
STATUSVERIFIED
CHAPTER 4147
The same address (EGva…Hs23) sold again — 90,930 $Human for 0.716 SOL, about seven hours after its first exit. Two sells, no buys on record, and the second cart is lighter than the first. The log has watched this wallet twice now and still hasn't seen it arrive.
tx: 3Hp8…RLuV
case file / 00

what is this, actually?

LOG remembers wallets and tokens. It reads the chain, records what each wallet did — bought, bundled, sniped, quietly left — and keeps it. So a wallet showing up on a token nobody has looked at yet already has a history, and what we serve is the insight, never the raw feed. Nothing is invented: every chapter links to the transaction that caused it.

what LOG is

a data warehouse for wallets and tokens

Raw transactions go in once. What comes out is a checkable record of what each wallet and each token did, and the insights built on it. Every row keeps the transactions it was computed from, so you can recompute any number yourself.

SOLANArawtransactionsand accountsINGESToperator coverageliveon request (paid)roadmapLEDGERtradestransferscomplete from launchpartly liveDERIVEDpositions · cost basiswallet profilesfunding evidencecohorts · clusterspartly liveINSIGHTSfeed · bot · evidencelivetoken reportroadmapAPI, SQL (derived)roadmapreadsstoresderivesservesraw feednot soldevery row keeps the signatures behind it: receipts
Raw transactions are read once and turned into a ledger, then into derived tables, then into insights. Only the insights leave. The receipts bar is the rule that makes the warehouse checkable: no derived number without the transactions it came from.
Insights, not raw data. We don't sell the feed and we don't resell a node. We serve what the chain means, with the receipts to prove it.
two directions, one register

ask a question, or help the record grow

ASKroadmapPaste a contractin the LOG botEstimate in creditsyou confirm firstBackfillcurve or poolAnalyseledger to insightsDeliverbot · PDF · linkTHE REGISTER · wallets and tokensevery row with its receiptswrites wallets and tokenswrites wallets and tokensACCUMULATEOperator addsa tokenBackfillfrom launchAnalyseledger to insightsIngestionapproach (beta)AutomaticcoveragePredictionsshadow, then betaliveroadmaplivebetanextroadmap
Both lanes write the same wallets and tokens into the same register. A paid request and a token added by the operator leave the same trace, each row with its receipts, so the record gets more complete every time either lane is used.

Ask

Paste a token contract, see what the report will cost before anything runs, and get who is making money, who is selling and how much has been taken out, with the wallets and transactions behind each line. Next on the path.

Accumulate

Coverage widens stage by stage, curated first and automatic after, on a data-ingestion approach that is currently in beta. It builds the record that later stages, up to predictions graded in public, stand on.

what it actually does

wallet intelligence, then token intelligence

case file / 01

Wallet intelligence

The asset. Every wallet we see acting inside a launch is fingerprinted and kept: what it did, how fast, what it paid, what it took out.

Keyed on wallets, not tokens, so the same address is known on the next launch whatever venue it is on, and the record only grows.

live
case file / 02

Token intelligence

What the record renders. Who bundled, who sniped, who the deployer paid, how concentrated it is now.

Every percentage ships with the wallets behind it. What we couldn't establish says so — never a clean zero. Next: a token report on request, with top-100 leaderboards in SOL of who is making money, who is selling and what has been taken out, each wallet shown with the number of screened launches it has been seen on.

live · report next
case file / 03

The Feed & the free read

Where you read it. Chapters, each linked to the transaction that caused it.

Or paste a contract address and get the read back. No account, no charge, no limit.

free
where the record goes

stage by stage, gated by data

  1. liveCurated coverageTokens chosen one at a time, the ledger built from launch. The token report is the first paid depth.
  2. nextAutomatic coverageNew launches brought under coverage as they appear, so the record is continuous.
  3. thenShadow predictionsBuilt from facts the warehouse holds, locked when made, graded, and not published.
  4. thenPublic betaPredictions shown with their evidence and a public record of hits and misses.
  5. futureOpen insightsDerived insights other builders can query. Never the raw feed.
  6. futureMore venuesBonk and the other launchpads, then the DEXs, into the same register.
recent entries

the feed, entry by entry. every one opens on its transaction.

CH.4147
The same address (EGva…Hs23) sold again — 90,930 $Human for 0.716 SOL, about seven hours after its first exit. Two sells, no buys on record, and the second cart is lighter than the first. The log has watched this wallet twice now and still hasn't seen it arrive.
on-chain
CH.4146
Same wallet, fifth buy on $Human: 126,745.837112 tokens for 1.037846925 SOL. It has bought four times before this and sold once, and the last time the log wrote about it, the cart was heavier than the one before. This one is lighter than that one by a hair, which is the kind of thing only a wallet with a habit would notice.
on-chain
CH.4145
Oof. A wallet bought $Human once, at 12:42, and sold the whole 1,420,189 tokens nine hours later at 60.6% below what it paid. That entry price covers only part of the position — the rest of its history on this token isn't on the record. One buy, one sell, and the log has both.
on-chain
the public record

Every token we screen stays screened, in public.

permanent
THE FORENSIC LAYER · NO ACCOUNT
The forensic layer of every tracked token is permanent and public

The verdict, the block it was derived from and the wallets behind every number — so anyone can check it without an account and without trusting us. Every token added makes that record longer.

The stories and chapters on your watchlist are yours — the ongoing narration on the tokens you chose.

Every token we cover writes into the same record. Past a certain size it stops being a feature of one product and becomes insight others can query: derived insights with their receipts, never the raw feed.

where we haven't looked it says so — never a clean zero
no exceptions
policy

the three rules that don't bend

  1. Nothing gets written that didn't happen. No fake wallets, no manufactured drama, no paid volume dressed up as a chapter. The premise dies the moment the input's fake.
  2. Name the wallet, and prove the claim. A wallet trades under the name its own owner chose on pump.fun, so that name is the subject of the sentence — with the address beside it. Anyone can call themselves anything; the address is the part you can check.
  3. An accusation rests on a relationship, never on a timestamp. Being early, being late, or being large proves nothing. Naming a wallet as part of a launch cohort takes something provable about how it is connected — a transfer from the deployer, a shared funding source, a token they ran together before.

the wallets are already on record.

Paste any Solana contract into the bot and read who is in it — holders, concentration, who is coordinated, what the contract still permits. Free, no account, no limit.

The safety question stays free, permanently. The forensic layer of every tracked token is permanent and public — a record of who did what on Solana, that nobody has to trust us to read.

$LOG token · CA: coming at launch