Skip to content

VeriLaunch

Token Verification

VerifyDiscoverLink Telegram

BOT Chain mainnet · chain ID 677

Know what a token proves before you trust it.

VeriLaunch reads live BOT Chain facts and shows where each one came from. No scam verdicts, no trust score, and no wallet required to check.

Verify a token See the evidence model
Read-only checksLive sourcesUnknowns shownNo account

Try it now — live on BOT Chain

Queries the BOT Chain RPC and the Blockscout explorer — a read-only check; nothing is signed here.

Read-only check · No account · No wallet · No gas — just data

A live report begins with one contract address

The evidence model

Four questions. Source attached.

The report separates confirmed facts, known negatives, unknowns, and request errors. Color supports the words; it never replaces them.

01

What does the contract return?

Name, symbol, decimals, and total supply are read from the token contract.

Source · BOT Chain RPC

02

Is source code published?

The report distinguishes published source from source not published on the explorer.

Source · Blockscout

03

What does holder data show?

Top 1 and top 5 shares are calculated from real balances, with the page cap disclosed.

Source · Blockscout holder balances

04

Can a liquidity lock be verified?

The BDEX V2 Locker stays unable to verify while its deployed address is unpublished.

Source · BOT Chain configuration

Provenance

A report is only as honest as its caveats.

Token basics are read from the contract. Blockscout supplies source publication and holder balances. The report keeps the timestamp, source, and best-effort limits beside the fact.

A confirmed fact is shown as confirmed, with its source named.

A known negative, like unpublished source, is not converted into a verdict.

An unavailable integration stays “unable to verify.” The BDEX V2 Locker is intentionally unconfigured at launch.

Registry boundary

A submission is a flag, not an endorsement.

Any connected wallet can submit a valid contract to the community registry; the submission is recorded on-chain as a signed transaction. Other people can then open its live report. The registry does not vet, approve, rank, or declare a token safe.

Browse the registry

Telegram support

Bring the same evidence into chat.

The Telegram bot uses the same verification boundaries: live facts, visible unknowns, and no score in place of the report.

Bot commands

Open bot
/verify 0x…Get a token evidence report
/discoverBrowse registry submissions
/link CODELink a wallet to Telegram
/submit 0x…Flag a contract for others to check

Wallet context

Only connect when you need to act.

Wallet connection is reserved for registry submissions (recorded on-chain as a signed transaction), Telegram linking, and the weekly-quota AI interpretation. A normal verification check remains open to everyone.

Link Telegram

FAQ

Questions, answered plainly

Do I need a wallet to check a token?
No. Verification is read-only and requires no account or wallet. A wallet is only needed for Telegram linking, the optional AI interpretation, or a registry submission — and a submission signs a small on-chain transaction on BOT Chain mainnet (or testnet).
What does a registry submission mean?
It means someone flagged a valid contract for others to check. The registry is unmoderated: submission is not endorsement, approval, ranking, vetting, or a safety signal. Trust comes from each token's live report.
What does “unable to verify” mean?
It means the relevant source or configuration did not let VeriLaunch confirm the fact. For example, the BDEX V2 Locker address is not published in official BOT Chain documentation, so the lock check remains unknown rather than guessed.
Is the AI interpretation a score or recommendation?
No. It is a plain-language explanation of the facts above. It is generated only after server-side re-verification, is identity-quota limited, and never replaces the raw evidence or gives financial advice.
Where does the data come from?
Token basics come from the BOT Chain mainnet RPC (chain ID 677). Source verification and holder balances come from Blockscout. The interface labels source, caveat, and snapshot context for each evidence area.

Start with the address, not the assumption.

Run a read-only BOT Chain check, then decide what the evidence means for you.

Verify a token

Not financial advice. Always double-check the facts yourself.

VeriLaunch

Token Verification

Verification reads are read-only — nothing is fabricated, and when a fact can't be verified we say so. Registry submissions are recorded on-chain as signed transactions.

Verify TokenDiscoverLink Telegram@VeriLaunchBot

Verified data only · BOT Chain

Green — a confirmed factAmber — unable to verifyGray — not verified (a fact)