Fast answer
Realized-price signal checks prove whether cost-basis context, spot price relation, holder cohort, and timing were visible.
Before accepting a bitcoin realized price signal, record the data provider, realized-price model, holder cohort if used, spot price, distance from realized price, time frame, signal timestamp, trade plan, invalidation, updates, and final result.
If a provider calls realized price support without showing the level, cohort, and original signal time, the claim is not auditable.
Cost-basis checks
What to inspect in bitcoin realized price signal records.
Model source
Realized price, short-term-holder realized price, active investor price, and other cost-basis models should be named clearly.
Spot relationship
The record should show whether BTC was above, below, retesting, or reclaiming the model at signal time.
Cohort scope
All-holder cost basis can say something different from short-term-holder or long-term-holder cost basis.
Trade plan
A reviewable signal includes entry, stop, invalidation, update trail, and final outcome.
Source context
Realized price estimates average on-chain cost basis, not a precise support or resistance guarantee.
Glassnode describes realized price as an early on-chain metric designed to reflect average cost basis by valuing coins at the time they last moved on-chain. Bitcoin Magazine Pro similarly explains realized price as realized value divided by circulating bitcoin. The level can frame context but still needs execution proof.
Review standard
A reviewable realized-price signal ties cost basis to a visible execution rule.
For CSR evidence review, realized-price records should include source, model, holder cohort, spot price, cost-basis level, signal timestamp, entry, invalidation, updates, and final outcome.