Keith Kitchen

Crypto Dashboard

Casefile for the review surface I used to bring crypto market structure, macro liquidity, and trading context into one repeatable workflow.

Cadence Recurring review surface

Built for weekly and monthly state checks instead of one-off chart snapshots.

Stack Looker Studio plus TradingView

Market-cap dashboards, chart sandboxing, and macro overlays live in one working desk.

Goal Structure over noise

The dashboard exists to separate regime change from local volatility before positioning changes.

Summary

Role

Dashboard builder, signal curator, and market-review operator.

Inputs

BTC history, CRYPTOCAP data, macro series, and custom chart tracking staged into one review loop.

Use

Support market reads, memo updates, and the cycle framework without bouncing between scattered tabs.

Problem

  • Crypto data was easy to access but hard to interpret consistently because context lived across too many disconnected charts.
  • I needed one surface that could hold BTC structure, market-cap rotation, liquidity context, and risk discussion together.
  • The dashboard had to support both live review and later documentation so it could feed the rest of the research system.

Core modules

Bitcoin performance

Price history and structural context built from a staged Bitcoin CSV data source.

Market-cap dashboard

Looker Studio surface for crypto market composition, capital rotation, and capitalization structure.

Chart sandbox

TradingView layer for hypothesis checks using dominance, liquidity, breadth, and macro overlays.

Review output

Dashboard reads fold directly into market notes, watchlist changes, and cycle updates.

Charts I rely on

BTC price history CRYPTOCAP:TOTAL3 FRED:WALCL BLS:UNRATE BTC.D ex stables

Market-state explainer

The core question is simple: is the move structural enough to change positioning, or is it just noise inside the current phase?

Review loop

Monitor Track BTC structure, breadth, dominance, and macro liquidity in one repeatable surface.
Interpret Decide whether the change is regime-level, confirmation-level, or just local volatility.
Document Turn the read into a market note, watchlist change, or risk comment that can be reviewed later.
Reuse Feed the output back into the cycle playbook and the next market memo instead of starting from zero each week.

What it improved

  • Reduced context switching when reviewing crypto markets.
  • Improved consistency in how market-state changes were described.
  • Created a cleaner bridge between live monitoring and written market notes.
  • Provided the working surface that the cycle playbook could rely on.

Connected outputs

Sources

  • Bitcoin price history staged through Google Sheets CSV
  • CRYPTOCAP market-cap data
  • FRED and labor-market data for macro context

Next iteration

  • Add alert thresholds for regime-shift candidates.
  • Add standardized snapshot exports for monthly review logs.