live · solana devnet

The deployed thing.

Soothsayer's router and Chainlink Streams relay programs are deployed on Solana devnet. This page reads their on-chain state directly from the deployed PDAs every 30 seconds — no cached snapshots, no off-chain compositing. Honest scoping: the end-to-end publish→read-back loop is not yet wired (the account-initialize runner is still a TODO — see docs/devnet-quickstart.md), so the PDAs below read as not-found until a publisher populates them. On-chain serving runs the M5 reference path; enabling the deployed off-chain forecaster on-chain (M6 LWC + σ̂ EWMA HL=8) is pending the next publisher release.

connecting… cluster: devnet

Router snapshot — SOL

program: AZE8…xNU · snapshot pda:
$ — — — band [—, —]
regime
quality
aggregate method
quorum (size / required)
methodology
soothsayer-router · unified_feed_receipt.v1
publish_ts: — slot: —

Streams relay — SPY (synthetic feed)

program: DiLq…yMFG · relay pda:
$ — — — bid/ask [—, —]
market status
signature verified
schema decoded from
underlier symbol
feed_id
chainlink_observations_ts: — relay_post_ts: —

How to read this page

Router snapshot is what consumers integrate against. The regime tells you which calibration methodology backed this read — open means Layer 0's multi-upstream aggregator, closed means soothsayer's empirically-calibrated band primitive. The quality_flag is a required disclosure when the underlying conditions are degraded (low quorum, all upstreams stale, ambiguous regime).

Streams relay is the soothsayer-controlled relay for Chainlink Data Streams (Option C, methodology entry 2026-04-29 afternoon). The signature_verified field is load-bearing: 1 means the underlying signed Chainlink report was validated on-chain by the Chainlink Verifier program via CPI before this PDA was written; 0 means dev-mode (off-chain validation only). Production relays always run with CPI required.

Both PDAs auto-refresh every 30 seconds. Click any address to open it in a Solana explorer.