← Bot directory

Status & evidence record

HyperEVM Sniper Bot

Onboarding withheld

Verification pending; previous listing claims not reverified

Source checked · Scope & primary sources

Not reverified: prior fee, dual-layer, 150 ms latency, and API-only permission claims are suspended pending accessible primary evidence.

What the sources describe

This profile is retained as a status notice. Current fee, architecture, latency, custody, and wallet-permission claims could not be reverified from accessible primary documentation.

Documented ecosystem
HyperEVM
Interface
Not reverified

An exchange integration is not evidence of HyperEVM deployment.

Account & key authority

Prior claims that keys are generated locally and that access is API-only with no withdrawal capability could not be reverified from accessible primary documentation. Key generation, storage, and permissions remain unresolved.

How to check permissions →

Fees & conditions

Provider charges
Not reverified as of 2026-09-28; the previous 1% claim is withdrawn pending primary evidence.
Plans & payment terms
Not reverified; no accessible current primary fee schedule was found in the scoped check.

Provider charges do not establish total cost. Exchange fees, funding, gas and slippage may also apply.

Limitations to understand

Cautions

  • Do not rely on the earlier 1% fee claim
  • Dual-layer and CoreWriter claims are not reverified
  • 150 ms latency claim is not reverified
  • Key custody and withdrawal permissions are not reverified
  • Current service availability was not verified

Permission & security notes

  • No current primary evidence was found for key generation, storage, or permission limits
  • The earlier non-custodial/API-only description is withdrawn pending evidence

This record is retained for status and evidence information. New-user onboarding and endorsements are suspended.

Listing status — September 28, 2026

HypeChain has suspended its verified endorsement of HyperEVM Sniper Bot. The prior profile described a 1% fee, dual-layer/CoreWriter execution, 150 ms latency, and non-custodial API-only permissions. This source check could not reverify those claims from accessible primary documentation, so they are withdrawn from the active recommendation.

The bot’s listed Telegram entry point did not expose documentation we could inspect, and the available source search did not surface a current official fee schedule or technical and wallet-permission specifications. This does not establish whether the service is operating; current availability was not verified.

What remains unverified

  • Current fee rate and whether other charges apply
  • Whether the bot uses CoreWriter or otherwise executes across HyperEVM and HyperCore
  • Any measured execution latency
  • How keys are generated or stored and what trading or withdrawal permissions apply
  • Current service availability and operator identity

Do not rely on the earlier 1%, dual-layer, 150 ms, or API-only claims when comparing bots or deciding whether to connect a wallet. This profile remains as a status notice for readers of the previous review; it is not an active trading recommendation and contains no trading or onboarding link.

To reconsider the listing, HypeChain needs current primary documentation for fees, architecture, and wallet permissions, plus independent checks appropriate to those claims. This update did not inspect code or interact with the bot. Trading tests not run.

For BSC bot coverage, visit BSC.app .

Evidence, scope & sources

Source check: September 28, 2026. Documentation review; independently tested behavior is not established by this check.

Scope: Accessible listed bot entrypoint and official-source search checked for fees, architecture, latency, and wallet permissions; current claims not reverified; trading tests not run.

Sources reviewed (0) & freshness policy

Evaluated October 3, 2026 against the 90-day editorial window. This describes a dated source check, not current service operation. Builds do not renew it.

No accessible primary sources recorded; claims remain unverified.

Features described in sources

  • Not reverified

Incident research scope

  • Not reviewed in the September 28, 2026 scoped source check.

Historical review date: 2026-02-08. Design updates do not renew source checks. Read our methodology.