Skip to crypto research
Crypto Trading Strategy GuideVenue / Contract / Settlement

Cryptohopper assessment

An automation route to investigate, not an independently tested crypto strategy.

Original desk review: 8 October 2026. Examples are fictional scenarios; no live crypto strategy or paid account was tested. Expanded edition: 14 October 2026.

Bot and signal marketplace

Mechanism

The official marketplace presents signals and trading automation products. Distinguish the bot software, a selected signal seller and the exchange account. The economic outcome depends on that exact combination, not the marketplace label.

Unresolved Checks

Confirm supported venue, regional access, order sizing, fee treatment and key permissions for the intended configuration. Ask how it reconciles timeouts and partial fills. This publication has not connected API keys or reproduced a seller's ledger; no return or reliability score is awarded.

Primary Sources

Compare categories and evidence limits

Paper automation has a declared environment

Cryptohopper's official paper-trading page describes a simulation role. A genuine evaluation must preserve environment, chosen venue/product support, configuration, inputs and permitted actions. Paper output is not an actual exchange execution stream or independently validated live return. This desk did not activate a paid bot, obtain private settings or reproduce a continuous result population. The settlement worksheet contains manually chosen values rather than vendor trades. Its linear/inverse labels do not grant a particular bot contract or prove that the actual selected environment implements the same formula, funding or quantity rules.

A simulated balance still needs its producing assumptions

An invented learner saves a paper balance but lacks causal data history, effective configuration and real fill evidence. The completed finding is simulation context with absent economic sources, not a statement that any real vendor misreported results. Ask for fee model, execution assumptions, missing data, funding calendar and complete eligible decisions. Partial quantities and unknown request states may have different meanings in paper and actual environments. No paid customer, bot result, market observation or calibrated failure probability is invented to close those questions. The original data workbench preserves them as evidence requests.

Account authority is not a feature label

A bot description does not itself establish current account permissions, custody arrangement or withdrawal protection. Verify the exact selected venue, product and chosen rights from effective sources. Keep view, trade and administration scope separate. Current pricing, renewal, cancellation and trial terms are not measured by this profile. The public teaching packets request no key and grant no subscription, proprietary code or historical-data licence. Adjacent chart or copying tools remain different routes, not financial competitors with a tested return ranking. No platform suitability or safe funded-account allocation is inferred.

The next evidence request stays specific

A real comparison would join authentic original configuration, eligible history, unique executions, fee assets, final funding cash and the account valuation policy. A current public feature page supplies only its stated mechanism context. Actual strategy research and operational deployment need their own independent evidence; code presence or a simulation label cannot substitute for a complete master or deployed subscriber route. The static website creates no live exchange connection or personal-computer production dependency. It can document what is missing without promoting a paper example into an independent account audit.

Primary references and scope

Source review: 14 October 2026. Official mechanism descriptions are not this desk's paid-account test, independently captured fills or vendor-return audit.