Quoted text as recorded“This will now act as support. If we lose that, then you go back down to the 50 EMA.”
Our interpretation
- Source published
- Sep 28, 2026
- Interpreted confidence
- low
- Specificity
- vague
Why this call is unscored
- Status
- Not scored: condition
- Notes
- The claim contains a condition. Its trigger has not been verified, so price alone cannot establish an outcome.
Email me when HYPE calls resolve
When a tracked HYPE call is scored — hit, miss or partial — we’ll email you the result. No account needed.
Used only for these updates. Privacy
Evidence and source
Our summary of the thesis
BullishStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
The host views HYPE's decline as profit taking after a strong run and expects a recovery around the following week. Former resistance and the Bollinger Band midline form the support area he is watching, with a deeper decline possible if it fails.
Key arguments
- The weekly pullback has reached the five-period moving average after price became extended above it.
- He describes the broader trend as still rising.
- Former resistance should now act as support.
- The Bollinger Band midline and nearby support form a contested trading area.
Counter-arguments acknowledged
- The chart shows a large red gap down and considerable selling.
- Losing support would expose the 50 EMA.
- The recovery timing is expressed as a hope.
Hedges and caveats (from the video)
- A confirmed XRP breakdown below the daily 50 EMA would change his assessment and prompt action.
- XRP must break above and hold its weekly 50 EMA to confirm the anticipated advance.
- The XRP advance could begin earlier than his late-October estimate.
- HYPE could decline to its 50 EMA if support fails.
- The promoted algorithm's historical backtesting does not guarantee future performance; the host explicitly says he does not know whether it will outperform.
About this record
Not yet reviewed by a moderatorImported analysis · scheduled AI source. A quote, summary and outcome each need their own context. Moderator review does not certify investment performance.
- Source published
- Sep 28, 2026, 9:04 PM UTC
- First recorded by TubeRank
- Oct 6, 2026, 6:51 AM UTC
- Record last updated
- Oct 6, 2026, 8:49 AM UTC
- Moderator review recorded
- Not recorded
- Transcript provenance
- YouTube captions (manual or automatic)
- Recorded analysis processor/source label
- codex-cli-scheduled
- This can identify a workflow rather than an exact AI model version.
- Submission path version
- manual_v1
- Identifies the precomputed submission path. It does not identify an AI model version or imply human authorship.
- Outcome methodology version
- 2026-10-06.5
- Outcome reason code
- unverified_condition
Recent record changes 2 shown
Oct 6, 2026, 8:49 AM UTC
unverified condition
- Outcome methodology version
BeforeNot recorded
After2026-10-06.5
- Reference price
Before91.68728
AfterNot recorded
- Reference observation time
Before2026-09-27T23:59:59.999+00:00
AfterNot recorded
- Reference price source
Beforeyahoo_daily_crypto
AfterNot recorded
- Recorded outcome date
BeforeNot recorded
After2026-10-06
- Outcome explanation
BeforeNot recorded
AfterThe claim contains a condition. Its trigger has not been verified, so price alone cannot establish an outcome.
- Outcome reason
BeforeNot recorded
AfterUnverified condition
Oct 6, 2026, 6:51 AM UTC
source updated
- Recorded analysis processor/source label
BeforeNot recorded
Aftercodex-cli-scheduled
- Extraction or submission version
BeforeNot recorded
Aftermanual_v1
Showing up to 20 recent changes. The complete feed has 3 recorded events for this call, including its initial entry. Read the full paginated history (JSON); follow nextCursor while hasMore is true.
Stored outcome evidence
- Stored reference price
- Not recorded
- Not recorded · provider not recorded
- Target as extracted
- Not recorded
- Stated deadline as extracted
- None recorded
- Recorded outcome date
- Oct 6, 2026
- Outcome price observation
- Not recorded
- Not recorded · provider not recorded
Stored explanation
The claim contains a condition. Its trigger has not been verified, so price alone cannot establish an outcome.
Missing timestamps, providers and versions are historical gaps. Stored observations can include daily closes; they do not show every intraday touch or prove an executable trade. Read the methodology.
Why we interpreted the confidence this way
The downside forecast is conditional on losing the identified support area. Applying the conditional deduction to the base score yields 3; 'will' describes support rather than an unconditional price decline.
