BitSanMARKET Simulation only
Market cache · refreshed 0m ago

Know what you’re looking at.

Eight observations, their evidence and the limits of what we know.

Token permissions

Can someone create more tokens?

A mint authority can create additional supply. That can dilute existing holders, even when a price chart looks healthy.

Mint authority →
Token permissions

Can token accounts be frozen?

A freeze authority can freeze token accounts. That may prevent a holder from transferring or selling tokens while the account is frozen.

Freeze authority →
Launch & creator

Who bought in the creation slot?

Several wallets buying in the token’s creation slot can reveal a concentrated launch. It is a reason to examine the early distribution, not proof that the wallets share an owner.

Bundled launches →
Launch & creator

Has the creator sold its curve purchases?

BitSan compares the creator’s recorded sales with what that creator bought on the bonding curve. This gives context when attention is focused only on price.

Creator selling →
Launch & creator

What happened to earlier launches?

A token can have a new name while its creator already has a recorded history. BitSan looks at earlier linked launches and their first hour on PumpSwap where that period can be measured.

Creator history →
Ownership & pools

How much supply sits in a few wallets?

A small number of wallets holding a large share of supply can have substantial influence over price. Wallet distribution helps describe that exposure.

Holder concentration →
Ownership & pools

Are trades occurring in the expected pool?

The same token can appear in more than one pool. Looking only at a symbol or token name can hide important differences in market depth and route identity.

Pool identity →
Ownership & pools

Did one wallet take a large share at migration?

The move from a bonding curve to a pool is a useful moment to inspect ownership. A single wallet buying a large share of the pool’s token deposit can leave other traders exposed to its decisions.

Migration sweeps →

Four states. No hidden verdict.

Flag present: the condition was found. Not observed: absent in the available check. Unknown: not established. Not applicable: does not apply in this stage.

THE WORK BEHIND THE INTERFACE

A closer look, with reasons you can inspect.

Selected technical checks use fresh, independent on-chain observations. Deeper creator and relationship research remains incomplete.

CREATOR RESEARCH

Look at the creator’s past.

Recorded launches, observed sales and recurring patterns give a token context beyond its chart.

How BitSan approaches this

The engine can start with BitSan’s recorded launches, then expand into bounded funding and on-chain history research. Every stage carries a coverage status. First seen in our records does not mean first launch ever.

Understand creator history →
WALLET RESEARCH

Look beyond the wallet count.

Holder concentration and evidence of wallet relationships help reveal who may be moving together.

How BitSan approaches this

The engine examines timing, similar buy sizes, funding and transfers. Strong and suspected relationships are kept separate. A cluster is evidence of a relationship, not proof of common ownership or fraud. Partial research stays partial.

Understand holder concentration →
RESEARCH YOU CAN QUESTION

Keep the evidence behind the claim.

A useful result needs its source, its coverage and a clear account of what remains unknown.

How BitSan approaches this

Token assessments record reasons and policy versions. Callout scorecards keep calls observed as they arrived separate from history collected later, with sample size and coverage. These engine capabilities are not connected to live public reports in this preview.

Read the check methods →

The bot adds another layer

Fresh checks before an entry

Supported entry paths read token and market accounts again before a buy. An unavailable safety read returns a refusal.

Existing engine capability

Token features that can change the rules

The mint safety check rejects active mint or freeze authority and unsupported or dangerous Token-2022 extensions.

Existing engine capability

The expected market, with current reserves

Curve and PumpSwap checks verify account identity and read reserves. Selected entry paths then assess depth and price impact.

Existing engine capability

Boundaries around your capital

The trading envelope checks trade size, open positions, exposure, hourly activity and loss conditions before reserving a buy.

Existing engine capability

A pause can be a decision

The envelope includes a consecutive-loss breaker. Separate integrity controls can halt activity when their configured conditions are met.

Existing engine capability

A reason you can inspect

Safety refusals carry codes and details. Entry records retain the safety evidence used by the inspected path.

Existing engine capability
Explore BitSan Auto →