On-Chain Moves research screen

Как этим пользоваться

1. Open On-Chain Moves and inspect each asset’s direction, evidence time and watch conditions.
2. Compare daily move, saved shared brief and experimental 4-hour direction lens; record unavailable or conflicting evidence as such.
3. If you have a public transaction ID, submit it and open the independent explorer. Admins can load the protected review queue and transcribe only the supported native-asset facts from that explorer; Whale Alert text and alert claims are not retained. After recording ETH or SOL facts, an admin may explicitly look for same-address leads among nearby reviewed transactions. Treat these as review leads only: they do not prove common ownership or intent. BTC address relationships are unavailable because those addresses are not retained.
4. After independently checking related transactions in their explorers, an admin may save a versioned story group with a written rationale. Revisions preserve prior membership and exact evidence links; newer transaction facts mark a group stale until re-reviewed. A group is analyst workflow context only and does not identify an owner, establish net flow, add event labels, or change market direction or probability.
5. Use Check reviewed analysis only after an admin has recorded independent explorer facts; inspect event delay, retrospective context and limitations. An admin can save an exact-evidence analysis draft to the separate transaction-analysis archive. Readers can reopen its historical market cutoff and hashes; admins can append an independently reviewed correction or withdrawal if needed. A signed-in reader can continue a saved draft in ResearchCase; the transaction ID and report hashes stay bound to the account that opened the handoff. These receipts remain unpublished and probability stays unqualified.
6. When an admin checks a mature market snapshot, compare its descriptive market view with the later stored perpetual close. Treat it as retrospective follow-up, never as a forecast score or probability. Load daily edition history to inspect every BTC/ETH/SOL opportunity, including abstentions and missed capture windows, then open a report snapshot to review its saved market context.

Разобранный пример и ожидаемый результат

Teaching case: BTC technical structure points upward while the shared brief conflicts and the 4-hour experimental lens is down; a large transfer reference alone does not resolve that disagreement. A saved draft preserves the exact market cutoff used at that time.

Это фиксированный учебный пример, а не текущая котировка, результат вашего счёта или торговая рекомендация.