What we watch
Skein tracks a small set of verified Stock Tokens on Robinhood Chain. An asset is verified only when its contract address matches the official registry, has code onchain, and reports the expected decimals and multiplier. For each one, Skein reads reference prices, Uniswap v3 pool state, executable quotes and swap activity.
How we spot changes
Detectors are deterministic rules with versioned thresholds. A change must persist across several checks, both sources must be inside their freshness limits, and comparisons use baselines from like market sessions. Thresholds are provisional until backtested and are never presented as a precision guarantee.
How we use market data
A verified observation is a value read directly from a source with its block, timestamp and hash. A calculation combines observations with a published formula. A possible explanation is a hypothesis and is always labelled as one. Evidence records are immutable and carry a SHA-256 hash of their inputs.
How updates are tracked
Each activity item stays open while Skein keeps monitoring it, then closes with an outcome. Updates are appended, never rewritten. When a figure is wrong, Skein adds a correction event and keeps both the original reading and the updated value. The History control on each activity page shows only what had been published at each point.
When data is delayed
Each source has a freshness target. When a source falls behind, Skein marks affected data as delayed, keeps the last verified reading visible, and stops publishing new claims that depend on it.
What Skein can't tell you
- Skein does not promise profitable trades or recommend any action.
- Reference prices are not executable prices. Swaps can fill at different prices.
- Source data can be delayed or incomplete, and only the covered pools are measured.
- A link between markets does not show that one caused the other.
