Module 3 · BOLT Verified

A transparency standard for BOT Chain projects

BOLT Verified is a public, automatable verification standard — not a security audit. It declares which transparency primitives a project has wired up so reviewers and counterparties can read it in seconds.

Standard publishedMainnet activation pending

What it does

A project becomes BOLT Verified when its on-chain footprint shows:

  • Launch metadata registered (BoltLaunchFactory).
  • BOT pair seeded via the BOLT router.
  • Liquidity locked in BoltLiquidityLocker with a public unlockTime.
  • Team / advisor vesting disclosed in BoltVestingFactory.
  • Grant registry entry (BoltGrantRegistry) with a metadata URI.
  • Owner / project wallet disclosed and matches all of the above.
  • No obvious rug configuration (locker beneficiary ≠ deployer, vesting cliff > 30 days, etc.).

Why BOT Chain needs it

A grant committee, a market maker, or a wallet's listing team should be able to decide whether to engage with a project from a single badge row — not a 40-tab spreadsheet. Verified is the protocol-level handshake that makes that possible across every BOT Chain launch.

Readiness evidence

The standard is automatable end-to-end: each badge is a deterministic check against on-chain data. No human review of code; no "team trust me" badge.

Verified LaunchVerified Liquidity LockVerified VestingGrant RegisteredPending Review

Once mainnet deployment completes

The verification engine reads on-chain state on a schedule and writes the resulting badge set into the project's BoltGrantRegistry metadata URI. Anyone can rerun the same checks because every input is public.

Commercial value

  • Free for projects that pass the standard.
  • Optional verification-bundle audit add-on (third-party audit shop, BOLT-coordinated).
  • Verified-badge placement on partner wallets and aggregators.
BOLT Verified is a transparency standard, not a security guarantee. Passing it does not imply BOLT or BOT Chain has audited the project's contracts. Always read the code.