What NagBot reads. How to use it, and what it runs on.

NagBot helps you investigate a token. It reads public chain data, applies written rules to it, and shows each finding with its source, its timestamps and its limits. It never certifies a token as safe, never decides who owns a wallet, and never asks you to connect one.

Read-only

No wallet connection, no signature, no seed phrase, no token approval. There is nothing to sign in to.

Evidence first

Every finding opens to its evidence: what was asked, of which source, at which slot or block, and what the reading cannot show.

Honest about gaps

A section that could not be read says so. Missing data is never shown as zero, and never as “no risks detected”.

Yours alone

Watchlists, snapshots, attributed wallets, claims and alert rules live in your browser. There is no account and no server copy.

Token Scanner

Paste a token address. A Solana address opens the full report; a 0x address is looked up on every EVM network NagBot reads and opens the core report on the one where it is a token. The first reading takes a second or two. The early-activity scan is longer and starts when you ask for it.

Wallet Map

Drawn from a Solana token’s first transactions: funding sources, early buyers, recipients. Observed links are solid, inferred links are dashed and labeled. Filter by link type or time, select a node or a link to read what it rests on.

KOL Watch

A registry you fill in yourself: a wallet a public account disclosed, the source of the attribution, two readings of its holdings and the posts you add by hand. Nothing ships in it.

Watchlist

Tokens and addresses you watch, the latest difference between two saved scans of each token, and the controls for exporting, importing and deleting your data.

Alerts

Five rule types: a decoded sell by a wallet, a group’s holdings falling below a level, pooled reserves moving, a token control changing, and a new funding connection. Checks run while this app is open.

Address profile

Any address in a report opens its profile: what kind of thing it is and how that was decided, its balances, and its recent transactions.

A token report has eleven sections: Overview, Token Controls, Holders, Early Buyers, Wallet Connections, Supply Exits, Deployer History, Liquidity, Claims, Activity and Changes. The section is part of the address, so a link opens the same view.

NagBot runs with no configuration at all, on key-free public sources. Each value below lifts one limit. They are read on the server only: no provider credential is ever sent to the browser, and none is written to a log.

Copy .env.example to .env.local and fill in what you have. With a configured Solana endpoint the early window grows from 60 to 200 transactions, funding is read for 30 buyers instead of 12, and history is paged back 40,000 signatures instead of 12,000.

The watchlist, saved snapshots, attributed wallets, claims and alert rules are stored in this browser’s local storage, validated every time they are read, and never sent to the server. Clearing the site’s data removes them.

Export

The Watchlist page writes everything to one JSON file. Keep it private: it holds your labels and notes.

Import

A file is checked entry by entry against the same rules as local data. You choose to merge it or to replace what is here. A file from someone else carries their labels and claims, not verified facts.

Delete

One control on the Watchlist page removes everything NagBot stored in this browser.

Bounds

Up to 100 tokens, 200 addresses, 20 snapshots per token, 200 attributed wallets, 40 alert rules and 200 alert events.

What the server sees

The addresses you scan, as any website sees the pages you open. It keeps no list of them and has no place to store one.

Bundles

No bundle provider is integrated. A visible Jito tip is reported; bundle membership is never stated.

Social posts

No social data provider is integrated. Posts are added by hand and labeled as manually supplied.

Alert delivery

In the app only. No email, Telegram or webhook delivery is built, and nothing is checked after the tab closes.

Busy tokens

Without oldest-first history, a token with more transactions than the page budget reports “earliest history not reached”, and early buyers are not listed.

Large holder sets

On the public Solana endpoint a full census works for tokens with a moderate number of holders. Larger ones report “unavailable” rather than a partial count.

EVM depth

Core checks only. Holders and creation need an indexer and are unavailable where no key-free one exists.

Request limits

Per visitor: 90 reads and 6 decoding scans a minute. Provider quotas remain the real bound.

NagBot is a Next.js application. It needs Node.js 22.12 or newer and pnpm.

pnpm install
pnpm dev          # http://localhost:28900

Checks and a production build:

pnpm check        # types, lint, tests
pnpm build
pnpm start        # http://localhost:28910

The same pipeline runs from the command line, which is the quickest way to see what an endpoint can serve:

pnpm scan <mint> [--early] [--wallet] [--json]
pnpm scan:evm <ethereum|bsc|robinhood|elysium> <address>

The app holds no database and no secrets of its users, so it can run on one Node server or on a serverless host. The per-visitor request limit is kept in process memory: on a serverless host each instance counts separately, so treat it as a courtesy limit.