BDS / Intraday usability
Cryptohopper: Intraday Workflow and Evidence
Bot and third-party seller. Source-linked desk research, not a verified subscriber-performance ranking.
Continuous markets do not imply a same-session mandate
The marketplace lists third-party signals with exchange and free/paid filters. Evaluate a named seller and the configured bot, not a platform-wide intraday return. A crypto venue may trade continuously while the seller holds positions for days; those are different clocks. Define your session boundary and the intended handling of open positions before starting a trial.
Configuration can dominate the subscriber outcome
Save the seller, pair list, permitted exchange and local order rules. A hypothetical signal can arrive when the bot has no available balance or already holds the maximum permitted exposure. Track that event as rejected or skipped. A summary that keeps only filled winners cannot describe the full automation workflow.
Test both the close and the accounting
Attach exchange order identifiers to any alert that produces an order, and retain partial fills, fees and open positions at the chosen cutoff. A sell instruction that remains unfilled can leave overnight exposure despite a seller marking its idea closed. This assessment did not run a paid bot or authenticate a marketplace seller's full history.
Purchase rationale
Shortlist if your goal is a deliberately configured crypto execution environment and you can review the seller separately. Avoid treating marketplace convenience as audited same-session performance. Confirm current plan, venue and custody assumptions without assuming that a historical screenshot applies to your account.
Intraday Evidence Packet
| Question | Required record |
|---|---|
| What is purchased? | Bot and third-party seller |
| What remains to inspect? | Seller timing and configured execution chain |
| Which test was not done? | Paid access, routing latency and funded subscriber execution. |
Check the selected product, actual instrument mapping and original session policy. A platform mechanism can be documented while a private plan or source account remains untested. Do not fill those gaps from a brand reputation.
Keep the session evidence record / Product compatibility questions
Primary References
The sources support documented mechanisms and source definitions. Our procedure and teaching examples are not completed paid-feed, latency or account tests.