Cryptohopper: proof scope and population coverage
Paper configuration stays paper: source-specific evidence questions for Cryptohopper, not a completed paid-account test.
Automation tools. A documentation-based note, not a measured performance ranking.
Verification methods and user-led checklists. No provider has been certified by this site; declared coverage counts are not independently checked.
Automation tools
A paper bot record and a real exchange ledger answer different questions. Verify configuration and field scope.
Evidence still needed
Request original bytes, serialization version, proof file, verified attestation, complete signal-ID population, amendments and the separate execution ledger. A hash match is only one part of that request.
Assessment boundary
No paid-account test, complete trade population or independent execution comparison was supplied for this entry. Current terms, regional eligibility and the exact purchased offer require direct confirmation. No rating, rank or consumer-review count is asserted.
Source documents
Documentation establishes the stated mechanism, not tested trading performance. Checked 9 October 2026; a later version can differ.
Paper configuration stays paper
Request the exact configuration, data inputs, test environment and continuous event population. A paper-trading exercise is not a real exchange account. Preserve simulated fill conventions and do not describe them as broker evidence. A hash of configuration can identify that object while leaving future execution, costs and strategy validity unresolved.
From configuration to exchange records
A real automated workflow needs separate connector events, acknowledged orders, fills, outstanding exposure and account accounting. A functioning bot is not proof of profitable strategy performance. Changes to settings deserve new versions and their own effective times. This note has no paid bot test or actual exchange ledger and therefore supplies no measured return, rating or verification badge.
An invented paper-to-live distinction
Prepare fictional configuration BOT3 in a paper environment and an independent live-account label EX9. The paper output has a retained settings file, while EX9 has no order or fill ledger in the example. A digest of BOT3 can establish identity of the authored configuration file, but it cannot bridge the missing exchange record or convert simulated execution into actual fills.
A second configuration BOT3-v2 changes an execution setting. Preserve its parent and effective-time request rather than overwriting the earlier experiment. Paper fill assumptions, connector acknowledgements and real filled quantities remain different records. A functioning connection would show operational behaviour, not independently validated strategy performance. No paid automation or exchange account was used for this fictional case.
Retain environment_label, configuration_version, data_input_identity, event_population, simulation_fill_convention, connector_event_id, order_acknowledgement, actual_fill_source, quantity_source and account_cost_scope. A complete net-return claim would need an authentic economic ledger and declared accounting method. The hash fixtures and membership checker cannot supply that evidence. The bounded finding is inspectable paper configuration with unestablished live execution, not evidence that a bot is profitable or that it fails. Keep the paper/live boundary in the title, visible notes and machine-readable exports so a precise-looking result does not acquire a different empirical meaning.