Protection needs evidence.

Anti-sniper protection #

RESET intends to reduce the advantage of automated buyers at the opening of a launch. The batch-round design is one part of that direction. No anti-sniper enforcement program or production-tested rule set is active yet.

A shared opening window cannot by itself prevent multiple identities, privileged transaction routing, manipulation after settlement or abuse of poorly specified allocation rules.

Connected wallets and bundles #

The planned analysis aims to identify groups of wallets that may be acting together, rather than treating every address as an independent buyer. The data sources, scoring thresholds, timing and enforcement consequences are still to be designed.

Wallet relationships are signals, not proof of common ownership. A future detector can miss connections or flag unrelated users. “Not analyzed” must never be read as “clean.”

Developer holdings and distribution #

The product intends to show creator holdings and token distribution alongside a token. Useful disclosures will need a clearly identified mint, timestamp, definition of the creator wallets and treatment of pools, program accounts and locked allocations.

No wallet risk engine, verified distribution pipeline or insider-free certification is available. A low displayed creator balance would not, by itself, rule out related wallets or later transfers.

What readiness should look like #

Before any protection is described as active, RESET must publish what it checks, when it checks it, what it blocks and what it cannot detect. These docs will need to change with the actual implementation.